HP Integrity Virtual Machines Release Notes

8.8 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.9 Extending a Logical Volume Backing Store Corrupts the Guest
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.
In this case, the guest root device has been corrupted. You must reinstall the guest operating
system.
For a 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.10 Management Limitations of Virtual SCSI Devices
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.11 Installing Integrity VM Clears SecurePath 3.0F SP1 Settings
If you are using SecurePath for a storage array configured as active-active, update to SecurePath
3.0F SP2 before installing Integrity VM. With earlier versions of Securepath, you must manually
restore your SecurePath configuration after installing Integrity VM.
48 Storage Information