HP Integrity Virtual Machines 4.2.5: Release Notes

1. In the guest, execute rmsf for the lun path ( lunpath Class in ioscan display).
2. In the VM Host, delete the lun entry from the guest's configuration using the hpvmmodify
command.
3. In the VM Host, add the lun entry back to the guest's configuration using the hpvmmodify
command.
4. In the guest ioscan, the lun (which was deleted and added back) does not appear.
Perform the following workaround:
1. In the guest, rmsf the target path (tgtpath Class in ioscan display) corresponding to the lun
path.
2. In the guest, perform an ioscan.
8.2.22 Storage for Deactivated Volume Groups not Protected by Integrity VM Storage
Management
When an LVM volume group is deactivated, the storage (physical volumes) used by that storage
is designated as unused by HP-UX system administration tools such as System Management
Homepage (SMH). This is also true for Integrity VM storage management. As a result, these physical
volumes are not automatically protected from use by virtual machines as virtual disks.
You can resolve this problem in one of two ways:
• If the volume group is to remain deactivated, the VM Host administrator can manually add
the physical volume as a restricted device with the hpvmdevmgmt command.
• Or, after activating the volume group, execute the hpvmhostrdev command, so that the VM
Host storage management database is updated accordingly.
An HP-UX system administrator can deactivate a volume group using the vgchange command. It
can also be deactivated, if it is a shared LVM (SLVM) volume group, whenever the associated
Serviceguard cluster is reconfigured, or the VM Host system is rebooted. Take care to check that
all SLVM volume groups are activated after a VM Host reboot or Serviceguard cluster
reconfiguration.
8.2 Known Issues and Information 87