HP Integrity Virtual Machines Release Notes Version A.03.50

# hpvmstop -P winguest
# hpvmconsole -P winguest -c "pc -off"
These commands do not stop the Windows operating system gracefully. To shut down a Windows
guest, use the standard Windows operating system commands.
4.1.11 Do Not Delete EFI Shell Boot Option
Do not delete the EFI Shell [Built-in] EFI Boot Manager option. Deleting this option
might interfere with the subsequent installation of the guest operating system. To recover if there
are no options present on the EFI Boot Manager menu screen:
1. Enter the Boot option maintenance menu.
2. Select Add a Boot Option.
3. Select Load File [EFI Shell [Built-in]].
4. Save the setting to NVRAM.
4.1.12 Bug Check 0xA: IRQL_NOT_LESS_OR_EQUAL — 1
If the footprint on the guest console looks like the following text, then this is a known problem
with the Microsoft Windows 2003 Server SPx code base.
*** STOP: 0x0000000A
(0x00000000000003E8, 0x000000000000000C, 0x0000000000000000, 0xXXXXXXXXXXXXX)
We are investigating possible workarounds for this problem. If this bug check continues to occur,
try reducing or adding virtual CPUs or changing another configuration parameter temporarily.
4.1.13 Bug Check 0xA: IRQL_NOT_LESS_OR_EQUAL — 12
If the footprint on the guest console looks like the following text, then this is a known problem
with the Microsoft Windows 2003 Server SPx code base.
*** STOP: 0x0000000A
(0x0000000000000010, 0x0000000000000002, 0x0000000000000000, 0xXXXXXXXXXXXXX)
There is a patch available from Microsoft (4.6 QFE) to resolve this issue.
4.1.14 Restoring the NVRAM for Windows Guests
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:
1. From the Boot Maintenance options, select the boot device and enter the following command:
fs0> ls \EFI\Microsoft\WINNT50
Look for the Bootxxxx filename.
2. Change to the MSUtil directory. For example:
fs0> cd \MSUtil
3. Enter the following command:
fs0:> nvrboot
4. Enter the I command to import the Windows boot entry. Then enter the correct location of
the boot entry. For example:
4.1 Windows Guests 37