HP XP RAID Manager Software - Manual (Page 15)

The following commands cannot be used because there is no PORT information:
•
raidscan -pd <device>, raidar -pd <device>, raidvchkscan -pd <device>
•
raidscan -find [conf] , mkconf
Requirements and restrictions for VM
Restrictions for VMware ESX Server
Whether RAID Manager (RM) runs or not depends on the support of guest OS by VMware. In
addition, the guest OS depends on VMware support of virtual H/W (HBA). Therefore, the following
guest OS and restrictions must be followed when using RAID Manager on VMware.
Figure 2 RAID Manager configuration on guest OS/VMware
The restrictions for using RAID Manager with VMware are:
1.
Guest OS. RAID Manager needs to use guest OS that is supported by RAID Manager, and
also VMware supported guest OS (for example, Windows Server 2008, Red Hat Linux, SUSE
Linux). See
“Supported guest OS for VM” (page 12) .
2. Command device. RAID Manager uses SCSI path-through driver to access the command device.
Therefore, the command device must be mapped as Raw Device Mapping using Physical
Compatibility Mode. At least one command device must be assigned for each guest OS.
3. RAID Manager (RM) instance numbers among different guest OS must be different, even if
the command is assigned for each guest OS, because the command device cannot distinguish
a difference among guest OS due to the same WWN as VMHBA.
4. About invisible Lun. Assigned Lun for the guest OS must be visible from SCSI Inquiry when
VMware (host OS) is started. For example, the S-VOL on VSS is used as Read Only and
Hidden, and this S-VOL is hidden from SCSI Inquiry. If VMware (host OS) is started on this
volume state, the host OS will hang.
5. Lun sharing between Guest and Host OS. It is not supported to share a command device or a
normal Lun between guest OS and host OS.
Requirements and restrictions for VM 15