HP Integrity VM Accelerated Virtual I/O Overview

Migrating from SCSI or LAN to AVIO
Migrating from SCSI HBAs to AVIO_STOR
This section covers migrating existing SCSI HBAs to avio_stor. Note that the first release of the AVIO
storage driver does not have support for all of the physical backing stores or guest device types
supported by the virtual SCSI adapter.
The following physical backing stores are not supported by the AVIO storage driver:
• Attach
• Disk Partitions
The AVIO storage driver does not support tape, DVD burner and media changer guest devices. Also,
Integrity VM 3.5 does not support AVIO File Backing store (this feature is only supported with AVIO in
Integrity VM 4.0).
Support for Logical Volume (lv) backing store is available starting with the B.11.23.0712.01 revision
of HostAVIOStor bundle. This version is available at www.software.hp.com. Search for the
HostAVIOStor bundle name.
To migrate a SCSI HBA to avio_stor, it must contain only devices supported by AVIO. If there are
unsupported devices, these devices must be moved to a different SCSI HBA (or deleted) prior to
migration. Use hpvmmodify(1M) command to migrate scsi HBA to avio_stor.
The migration should happen after the host has been upgraded to Integrity VM 3.5 or 4.0 and all the
guests have been verified for correct operation. Below is a suggested sequence of steps. It is
suggested that the guest be offline for the entire sequence.
1. Check if there are attached devices by examining the output of
hpvmstatus –P <guest name> -d
2. If a HBA has both virtual and attached devices, delete the attached devices using
hpvmmodify –P <guest name> -d <tape|burner|changer>:scsi:<pci bus, pci device,
target>
3. Migrate the scsi adapters to avio_stor:
Integrity VMmodify –P <guest name> -m hba:avio_stor:<pci bus, pci device>
e.g. Integrity VMmodify –P vm01 –m hba:avio_stor:0,1
4. Add the attached devices deleted in step 3 above to the guest:
hpvmmodify –P <guest name> -a <tape|burner|changer>:scsi::attach:<device
name>
WARNING: Please note that moving unsupported devices to the new SCSI HBA will cause the device
special file name and the hardware path to change. Applications sensitive to device special file name
or hardware path, e.g. : LVM disks, need to be updated to work correctly.
Migrating from LAN NICs to AVIO_LAN
This section covers migrating existing lan networking NICs to avio_lan.
The current release of the AVIO networking driver does not have support for all of the physical
backing networking interfaces supported by the virtual LAN adapter.
The following physical backing interfaces are not supported by the AVIO driver:
• All 100Mbps network interface cards