HP IO Accelerator Driver 3.1.1 Release Notes

Errata 18
kdump crashkernel requires additional memory for the IO
Accelerator
With the IO Accelerator driver installed, kdump might fail to generate a complete dump due to a lack of
reserved memory. To ensure that you have enough memory, increase the memory allocated to the
crashkernel.
The amount of memory required varies, depending on your kernel version and the formatted sector sizes
(more RAM is required for 512B sector sizes than for 4K sectors). You can format the device sector size, using
the fio-format command. As a best practice, increase the crashkernel reserve by approximately 50
to 250 MB of RAM, depending on your configuration.
VMware-specific issues
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.