HP Integrity Virtual Machines Version 4.2 Release Notes

8.2.11 The hpvmmodify Command Fails to Change a DVD
The hpvmmodify command might fail to change a Virtual FileDVD if the device has already
been modified by the virtual console. The hpvmstatus command displays the current status of
the Virtual FileDVD, which might not be in its original resource state. To see the original resource
statement, which is required by the hpvmmodify command to change a Virtual FileDVD, use
the hpvmstatus —D command.
8.2.12 Virtual FileDVD Reverts to Original Resource Statement
A Virtual FileDVD reverts to its original resource statement when the guest shuts down or
reboots. Therefore, after you install a guest from multiple CDs or DVDs, you must reload the
Virtual FileDVD when the guest reboots to complete the installation. Stop the automatic EFI
reboot and insert the CD/DVD using the appropriate IN and EJ commands. When the media is
loaded, proceed with the installation.
8.2.13 Physical Device null Assigned to Nonexistent Path
Devices with physical storage type null might be given device path specifiers that do not exist.
This problem does not prevent guests from starting. In previous versions of Integrity VM, the
guest does not start if the device path for a null physical storage type device does not exist as a
real device, file, or directory.
8.2.14 Using sam on Guest Cannot Initialize Disk
When you create a file system using the sam command on an HP-UX guest, do not initialize the
disk. This option returns an error and the file system is not created.
8.2.15 Extending SCSI Whole Disk Backing Stores
On the VM Host, do not extend a logical volume (LVM or VxVM) used as a backing store for a
guest root disk. If you do this, the guest panics on its next reboot with the following error:
System panic: all VFS_MOUNTROOTs failed: Need DRIVERS.
The guest should be able to boot if the logical volume is reverted (using lvreduce in case of LVM)
to its original size. If this fails, the guest root device has been corrupted, and the guest operating
system must be reinstalled.
An AVIO logical volume backing store not used as a root disk can be extended while the guest
is online. For HP-UX 11i v3 guests using AVIO, the guest is notified of the increased size of the
backing store for logical volumes as well as raw disks, and the guest can take the appropriate
actions to use the larger size.
For a SCSI logical volume used as a backing store for a guest data disk, you can extend the volume
after removing it from the guest using the hpvmmodify command. After extending the volume,
use the hpvmmodify command to add the volume to the guest. Do not modify a logical volume
used as a backing store without first removing it from the guest.
After you extend the logical volume, use operating system commands on the guest to extend its
file system.
8.2.16 Virtual SCSI (VIO) Device Limitations
Although SCSI devices appear to a guest as Ultra320 SCSI controllers claimed by the MPT driver,
this is an emulation. There are several differences from using a real device. Specifically:
• You cannot upload or download firmware for emulated devices.
• Although HP-UX commands such as mptutil(1M) and mptconfig(1M) do not fail when run
in a guest, they do not always return the same information as they would when referencing
a physical device.
• The EFI drvcfg command does not fail when run in a guest, but it returns no useful data.
8.2 Known Issues and Information 79