This section lists release notes associated with starting and stopping
guests.
Do not enter Ctrl/B after starting guest with virtual console |
 |
When you use the pc -on command inside the Integrity
VM virtual console to start the guest, do not enter Ctrl/B;
this will interrupt the guest boot process. Wait for the guest boot to complete
and the virtual console prompt to return before entering Ctrl/B.
Restoring the NVRAM |
 |
When a guest has been terminated unexpectedly due to a panic or another
critical condition, the guest's boot settings (which are stored in a per-guest
NVRAM file on the VM Host) can become corrupted. This can cause problems with
subsequent reboots of that guest. To correct the problem, copy the file /opt/hpvm/guest-images/common/nvram to /var/opt/hpvm/guests/vm_name/nvram on the VM Host system. This procedure
restores the copy of the NVRAM that was used when the guest was created. Then
you can used the EFI Boot Manager to recreate the guest's boot path and other
data. (The installed guest's operating system should be intact and unaffected
by the corruption.)
To build the EFI Boot Menu Entry for Windows Enterprise:
From the Boot Maintenance options, select the boot device
and enter the following command:
fs0> ls \EFI\Microsoft\WINNT50
|
Note the Bootxxxx filename.
Change to the MSUtil directory. For example:
Enter the following command:
Enter I to import the Windows boot entry.
Then enter the correct location of the boot entry. For example:
\EFI\Microsoft\WINNT50\Bootxxxx
|
Guest LAN devices require an operational virtual network switch |
 |
If you experience a long delay in booting and HP-UX guest, specifically
while the guest is configuring the mail server, a LAN device may be misconfigured.
For instance, the vswitch name is misspelled or the vswitch is not active.
To display information about vswitches, enter the hpvmnet command.
How to stop guests |
 |
To stop a guest, HP recommends that you perform and operating system
shutdown from a privileged account on the guest. If the guest is not responding,
use the hpvmstop -g command on the VM Host. Do not stop
a guest by killing the hpvmapp process.
How to recover from a guest hang |
 |
If a guest hangs, use the virtual console's tc command
to reset the guest. The guest will capture a memory dump of the machine state,
which can be used later for offline diagnosis. Do not kill the guest from
the VM Host or use the virtual console to power down a hung guest. Doing so
can corrupt the guest file system.