Troubleshooting Guest Creation Problems

When the guest boots, the VM Host performs a dynamic resource calculation to make sure there are enough resources to run the guest. If problems occur, one or more of the following messages is displayed:

HPVM guest badguest configuration problems:
    Warning 1: Guest's vcpus exceeds server's physical cpus.
    Warning 2: Guest's vcpus exceeds the supported maximum, 4 vcpus.
    Warning 3: Insufficient free memory for guest.
    Warning 4: Insufficient swap resource for guest.
    Warning 5: Insufficient cpu resource for guest.
    Warning 6 on item /dev/rdsk/c2t1d0: Device file '/dev/rdsk/c2t1d0' in
use by another guest.
    Warning 7 on item /dev/vg00/rhostswap: Device file '/dev/vg00/rhostswap'
in use by server.
    Warning 8 on item /dev/rdsk/foo: '/dev/rdsk/foo' backing device does not
exist.
    Warning 9 on item hostnet: Guest MAC address for switch hostnet is in
use.
    Warning 10 on item offnet: Vswitch offnet is not active.
    Warning 11 on item badnet: Vswitch badnet does not exist.
These problems may prevent HPVM guest badguest from booting.
hpvmstart: Unable to continue.

These warnings allow the guest to be created, but not booted.

The following error messages prevent the guest from being created or booted:

hpvmcreate: ERROR (badguest): Duplicate backing device  '/dev/rdsk/c2t1d0'.
hpvmcreate: ERROR (badguest): Illegal blk device '/dev/dsk/c2t1d0s5' as
backing device

You can modify the guest configuration by using the hpvmmodify command, as described in “Changing Guest Configurations.”

Review the commands you used to create the virtual switches and guests, comparing your input with the messages and the hpvmstatus display to determine whether errors were made in the process of creating virtual switches and guests.

To view the commands that have been entered on the VM Host, look at the following file:

/var/opt/hpvm/common/command.log

You can ignore the following messages in the guest log file/var/opt/hpvm/guests/guestname:

LockInit: redundant call for living lock! 

Returning QUEUE_FULL to dev = …

Problem:

If a guest appears to hang (that is, there is no response to the ping command, or the hpvmconsole freezes), enter ^B (Ctrl/B) in the hpvmconsole session. This action returns you to the virtual machine console. Enter the CM command, then the TC command to send an INIT command to the guest OS. Do not reboot the guest.

On the VM Host, enter the hpvmcollect without the -c option. This command collects VM Host and Integrity VM information that is useful in analyzing the problem. Refer to “Reporting Problems with Integrity VM” in Appendix B for more information.

Problem:

The guest hangs in the EFI shell when you are starting it, and you get the following message:

Shell> \efi\hpux\hpux
'\efi\hpux\hpux' not found
Exit status code: Invalid Parameter

Solution:

The EFI boot parameters were probably not set up correctly during guest OS installation. Choose the correct EFI partition to boot. For example:

Shell> fs3:
fs3:\> hpux

Problem:

The hpvmconsole command hangs when you are starting a guest.

Solution:

Check the guest log file in /var/opt/hpvm/guests/guestname/log. If there is a user configuration problem, make changes to the guest configuration and restart. Otherwise, enter the hpvmcollect command, and report the problem through your support channel.