NAME
vparboot — boot a virtual partition
SYNOPSIS
vparboot
-p vp_name
[-b
kernel_path]
[-o
boot_opts]
[-B
boot_addr]
vparboot
-p
vp_name
-I
ignite_kernel
DESCRIPTION
The
vparboot
command causes the virtual partition monitor to boot the specified
virtual partition. The monitor must be running. The virtual partition
must exist in the monitor configuration and be in the
Down
state. For this reason, it is not possible to
boot the local partition using this command.
The partition in which the command is executing is called the local
partition.
On hard-partitionable systems such as Superdome, if there is a pending
reboot for reconfiguration, the specified virtual partition will not be
booted until all the virtual partitions on that hard partition are shut
down and the virtual partition monitor is rebooted.
Refer to "Performing a Reboot for Reconfig for an nPartition"
in the
HP Systems Partitions Guide, Administration for nPartitions
for more information.
Only a superuser can execute the
vparboot
command. In a secure virtual partition environment only a
Primary-Admin
vPar can boot a virtual partition.
Options
vparboot
recognizes the following command line options and arguments:
- -p vp_name
Specifies the unique name of the virtual partition which
is to be booted. The virtual partition must exist in the monitor's
database, must be in the Down state, and must have a configured
boot device. Required.
- -b kernel_path
Specifies the absolute path to a bootable kernel for the virtual partition.
For example, if a non-partitioned system start string at the ISL prompt
is:
ISL> hpux -iS /stand/vmunix
the
kernel-path
is the
/stand/vmunix
portion of this string.
If this option is omitted, the value is taken from any
-b kernel_path
specified during virtual partition creation or its most recent modification,
or
/stand/vmunix
if
-b kernel_path
has never been specified.
- -o boot_opts
Specifies the command-line options applied when the
virtual partition is booted. For example, if a non-partitioned
system start string at the ISL prompt is:
ISL> hpux -iS /stand/vmunix
the
boot_opts
string in this case will be
-iS.
Note that if there is a space included in the string, the string must
be quoted.
Refer to the virtual partitions administration guide
Installing and Managing HP-UX Virtual Partitions,
and the chapter titled "Monitor and Shell Commands" for a full list of
supported boot option strings.
If the
-o
option is omitted, the value is taken from any
-o boot_opts
specified during virtual partition creation or its most recent
modification, or the empty string if
-o boot_opts
has never been specified.
- -B boot_addr
Specifies the device from which the virtual partition kernel image is
read. It must be one of the following three forms:
- bo[ot] | pri[mary] (case-insensitive)
This is the default if the
-B
option is omitted.
vparboot
attempts to boot
vp_name
from the device previously configured with the
BOOT
attribute. It is an error if no device has been so configured.
- alt[ernate|boot] (case-insensitive)
vparboot
attempts to boot
vp_name
from the device previously configured with the
ALTBOOT
attribute. It is an error if no device has been so configured.
- tape (case-insensitive)
vparboot
attempts to boot
vp_name
from a device previously configured with the
TAPE
attribute. It is an error if no device has been so configured.
This will restore the contents archived using
make_tape_recovery
from
tape.
All the contents on the target disk will be lost.
- Boot From Hardware Path:
Any other string is assumed to be the hardware path (for example,
10/6.0) to the desired boot device.
vparboot
does not check any part of
such a specification. If it is not a proper path, the path does not
exist, the virtual partition does not own the device at that path, or
there is no bootable device at that path, the command either fails with
an error, or the boot attempt fails with no error indication.
- Boot actions:
If the boot from primary path fails then the combination of
autoboot
and
autosearch
attributes decides the boot action to be taken. Refer to
vparcreate(1M) or vparmodify(1M) for details.
- -I ignite_kernel
Specifies a path to a cold-install kernel such as
/opt/ignite/boot/WINSTALL.
This form of the command is used to cold-install an instance of HP-UX on
a virtual partition. Most often, this is done on a newly-created
virtual partition, one that has a completely unwritten disk. However,
it can be used to cold-install HP-UX over an existing instance.
ignite_kernel
can reside either on the current virtual partition (the one on which
vparboot
is run) or on any other networked system or virtual partition accessible from
that partition. The syntax for
ignite_kernel
is:
[server-name-or-IP-addr,]cold-install-kernel
If
cold-install-kernel
begins with a slash,
(/),
you are specifying an absolute path and
vparboot
looks for it at that location. With Ignite-UX revisions prior
to C.6.0, if
cold-install-kernel
does not begin with
/,
the default path
/opt/ignite/boot/
is prepended to
cold-install-kernel.
With Ignite-UX revision C.6.0 or later, the
cold-install-kernel
is not present under default path
/opt/ignite/boot.
Hence it is required to specify an absolute path, such as
/opt/ignite/boot/Rel_B.11.11/WINSTALL.
If
server-name-or-IP-addr,
is not specified,
vparboot
loads the cold-install kernel from the file space of the current
virtual partition. Otherwise the command loads it from the file space of
the specified server. The comma is a required part of the server name
syntax.
RETURN VALUE
The
vparboot
command exits with one of the following values:
- 0
Successful completion.
- 1
One or more error conditions occurred.
EXAMPLES
Boot the virtual partition called
Oslo:
Boot the virtual partition
Bergen
specifying an alternate kernel:
vparboot -p Bergen -b /stand/vmunix_debug
Cold-install the virtual partition
Trondheim
from a file on a remote server:
vparboot -p Trondheim -I mysys.myserver.mydomain.com,/mypath/myinst
Cold-install the virtual partition
Sandefjord
from a file at the default path
/opt/ignite/boot
on the current virtual partition:
vparboot -p Sandefjord -I WINSTALL
DIAGNOSTICS
vparboot
displays error messages on standard error for any of the following conditions:
vp_name
does not exist in the monitor.
vp_name
is in some state other than
Down,
and so cannot be booted. Use the
vparreset
command instead.
An error occurs while trying to access an Ignite server or cold-install file.
You have specified the
BOOT,
TAPE,
or
ALTBOOT
device, but the corresponding device has not been configured in
vp_name.
Note:
If the boot device has not been configured properly the
vparboot
command will complete without error, but the virtual partition will not
boot.
Possible reasons for this could be:
- —
The
BOOT
or
ALTBOOT
attribute was assigned to a device other than a disc or tape.
- —
The
TAPE
attribute was assigned to a device other than tape.
- —
The file at the default or configured kernel path does not exist or is not
a bootable image.
The
vparboot
command and the virtual partition monitor are at different revision
levels. This message is only a warning. The command continues.
AUTHOR
vparboot
was developed by the Hewlett-Packard Company.
Printable version
