HP XP P9500 Storage User Manual
Page 17
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.
3.
Lun sharing between guest OS and console OS. It is not possible to share a command device
as well as a normal Lun between a guest OS and a console OS.
4.
Running RAID Manager on Console OS. The console OS (management OS) is a limited
Windows, like Windows 2008 Server Core, and the Windows standard driver is used. Also
the console OS provides an execution environment to monitor and administer the entire Hyper-V
host.
Therefore, you can run RAID Manager by installing “RAID Manager for Windows NT” on the
console OS. In that case, the RAID Manager (RM) instance number between the console OS
and the guest OS must be a different instance number, even if the command is assigned for
each console and guest OS.
Requirements and restrictions for VM
17