HP IO Accelerator Driver and Management Software Version 3.2.3 Release Notes

Errata 26
Using VMDirectPathIO with multiple-device products
Some products contain multiple IO Accelerator devices on one PCI adapter, such as the IO Accelerator Duo
device. The IO Accelerator VSL does not support splitting the two IO Accelerator devices between two
functions or virtual machines. The following scenarios are supported:
• Both IO Accelerator devices are used as a VMFS datastore in ESX or ESXi.
• Both IO Accelerator devices are passed through (using VMDirectPathIO) to the same virtual machine.
ESXi 5.0 injected installer allows installation on an IO Accelerator
device
Do not install the host OS on an IO Accelerator device. IO Accelerator devices are not designed to be
bootable. The ESXi injected installer permits you to install the OS on an IO Accelerator device, but the
installation will fail on reboot.
IO Accelerator devices are only labeled as a VMware Block Device in the installer screen. Make sure to
select a bootable device during the installation.
The IO Accelerator driver cannot be installed as part of an ESXi
4.1 installation
The IO Accelerator driver must be installed on an existing ESXi host system.
vCenter cannot manage extents on IO Accelerator devices
You cannot use vSphere vCenter to manage extents on IO Accelerator devices, including growing or
spanning extents.
However, you can connect directly to the host using the vSphere client and manage extents on IO Accelerator
devices.
Solaris-specific issues
Provide adequate RAM
The IO Accelerator VSL might use a large amount of system RAM. If enough RAM is not available, the system
will crash. For RAM requirements, see "Hardware requirements (on page 7)."
As the system runs out of RAM, it might generate the following message:
verify: bad magic header 0, wanted acca at file /dev/rdsk/c6d0p0 offset
212606976, length 0