Restrictions on windows 2008/2012 hyper-v – HP XP RAID Manager Software User Manual
Page 17
hdisk2 -> NOT supported INQ. [AIX ] [VDASD ]
:
:
hdisk19 -> NOT supported INQ. [AIX ] [VDASD ]
The following commands discover the volumes by issuing SCSI inquiry. These commands
cannot be used, because there is no port/LDEV for RAID information.
raidscan -pd
raidscan -find [conf] , mkconf.sh, inqraid
pairxxx -d[g]
\\.\CMD-Serial#-LDEV#-Port#:/dev/rhdisk on horcm.conf
Therefore, you need to know the volume mapping information (/dev/rhdisk) on the VIO Client
by referring to the physical volume mapping through the VIO Server.
4.
About running on VIO Server. The volume mapping ( /dev/rhdisk) on a VIO Server is a
physical connection without converting SCSI Inquiry, so RAID Manager will perform as if
running on AIX 5.3. However, IBM does not allow running applications in the VIO server.
Since commands or scripts would have to be run outside the restricted shell, it may be necessary
to get IBM approval to run in the VIO server. So you would have to change your scripts to
run on a VIO server to issue the oem_setup_env command to access the nonrestricted shell.
Restrictions on Windows 2008/2012 Hyper-V
Whether RAID Manager can perform or not depends on the support of the guest OS by Windows
Hyper-V, and then the guest OS depends on how Hyper-V supports front-end SCSI interfaces.
Figure 4 RAID Manager configuration on Hyper-V
The restrictions for using RAID Manager on Hyper-V are as follows:
1.
Guest OS. RAID Manager needs to use the guest OS that is supported by RAID Manager and
also the Hyper-V supported guest OS (for example, Windows Server 2003/2008, SUSE
Linux). See
for details.
2.
Command device. RAID Manager uses the SCSI path-through driver to access the command
device. Therefore the command device must be mapped as RAW device of the path-through
disk. At least one command device must be assigned for each guest OS (Child Partition).
The RM instance number among different guest OSs must be used as a different instance
number even if the command is assigned for each guest OS. This is because the command
device cannot distinguish a difference among the guest OSs because the same WWN via
Fscsi is used.
Requirements and restrictions for VM
17