HP Integrity Virtual Machines 4.3: Installation, Configuration, Administration
This node is the Server.
Volume group "/dev/vgsharedA" has been successfully changed.
#
b. Check the VG Status line of the vgdisplay —v /dev/vgname output to make sure
that it is shared:
# vgdisplay -v /dev/vgsharedA | grep "VG Status"
VG Status available, shared, client
If the VG is not listed as shared, deactivate it and reactivate it with vgdisplay —v
/dev/vgname.
5. Install HostAVIOStor bundle.
If you plan to migrate VMs using logical volumes with avio_stor adapter, install a new
HostAVIOStor bundle on all VM Hosts. You do not need to install this bundle if your VMs
use the legacy VIO scsi adapters.
# swinstall -s depot-location HostAVIOStor
6. Troubleshooting
The following problems might occur:
• The hpvmmigrate fails with a message “Online migration requires only disk or null
backing stores.”
This is most likely caused by not having the latest patch installed on VM Host systems.
• If you receive the following response from the hpvmmigrate command:
hpvmmigrate:ERROR vmname: Source AVIO SCSI failure, status 252
The system does not have the right HostAVIOStor bundle installed to support migration
of VMs with logical volume backing stores. Make sure that the HP-UX 0910 version of
the HostAVIOStor bundle is installed on all VM Hosts among which you plan to migrate
your VMs.
7. Limitations
Online migration of VMs with logical volume backing stores is not supported for the
following configurations:
• Logical volume backing stores contained in volume groups defined on disk partitions
• VxVM logical volume backing stores
• Logical volumes that are not shared across VM Host systems.
• Logical volumes with different pathnames. That is, the pathname for the shared LVM
logical volume must be identical across all VM Hosts.
10.5.1 Creating and Configuring VMs as Serviceguard Nodes Having SLVM Backing
Storage
When creating and configuring virtual machines as Serviceguard nodes having SLVM backing
storage, the following limitations apply:
• SLVM backing stores can be used only as non-shared disks (system storage) in VMs as
Serviceguard Nodes configurations.
• SLVM backing stores cannot be used as shared disks (package storage) in VMs as
Serviceguard Nodes configurations.
• No special configuration other than what is described in Section 10.3, is required for these
configurations.
• Online migration of VMs is not supported in VMs as Serviceguard Nodes configurations.
10.5 Migrating VMs That are Using Logical Volume Backing Stores 219