HP BL680c HP integrated Citrix XenServer 5.0 Release Notes - Page 5

created using XenCenter on Fibre Channel or iSCSI

Page 5 highlights

• If you are using the scripting (XML) interface, issue a new INSERT_VIRTUAL_MEDIA command without sending EJECT_VIRTUAL_MEDIA first. The scripting interface causes multiple insert commands to be media changes and signals the appropriate event to the OS. If you are using virtual media through the integrated remote console, virtual media does not provide you with the level of control that is needed. The alternative to using virtual media in this manner is to use the java virtual media control in iLO. You can, however, use the integrated remote console to view the remote console and still access virtual media through the Java applet or scripting interface. PVC does not recognize for use a storage repository created using XenCenter on Fibre Channel or iSCSI storage If you use XenCenter to create a new storage repository(SR) on FibreChannel or iSCSI storage using the lvmohba SR type, it is unavailable for use for virtual machine storage in ProLiant Virtual Console. XenCenter does allow lvmohba SR to be used for virtual machine storage. When the SR is created by XenCenter the content_type is set to a bland entry. The ProLiant Virtual Console uses the content field (for virtual machine storage it looks for a content_type of user) to determine valid SRs that might be used to store virtual machines. Because of the way the SR is created the SR is not useable. A work-around is to use the xe command within Dom0 to create the SR instead and set a content_type of user on creation. For iSCSI array: xe sr-create host-uuid= name-label= shared= type=lvmoiscsi content_type=user deviceconfig:target= device-config:targetIQN= device-config:SCSIid= For a Fibre Channel array: xe sr-create host-uuid= name-label= shared= type=lvmohba content_type=user deviceconfig:device=/dev/mapper/ For more information see the Citrix XenServer 5.0 Admin Guide for additional details. Creating a shared SR using PVC on a Fibre Channel LUN can fail Creating a shared SR on a Fibre Channel exposed storage might fail if you use the PVC New Storage wizard to create the storage using the Local Storage option. PVC does not support creation of shared virtual disk storage. To accomplish this task, use XenCenter or the xe CLI tool in Dom0 to provision storage on a shared Fibre Channel LUN. To use PVC to create virtual machines using this storage, see PVC does not recognize SR created using XenCenter on FibreChannel or ISCSI storage. ("PVC does not recognize for use a storage repository created using XenCenter on Fibre Channel or iSCSI storage" on page 5) Important notes and recommendations 5

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11

Important notes and recommendations
5
If you are using the scripting (XML) interface, issue a new
INSERT_VIRTUAL_MEDIA
command
without sending
EJECT_VIRTUAL_MEDIA
first. The scripting interface causes multiple insert
commands to be media changes and signals the appropriate event to the OS.
If you are using virtual media through the integrated remote console, virtual media does not provide you
with the level of control that is needed. The alternative to using virtual media in this manner is to use the
java virtual media control in iLO. You can, however, use the integrated remote console to view the remote
console and still access virtual media through the Java applet or scripting interface.
PVC does not recognize for use a storage repository
created using XenCenter on Fibre Channel or iSCSI
storage
If you use XenCenter to create a new storage repository(SR) on FibreChannel or iSCSI storage using the
lvmohba SR type, it is unavailable for use for virtual machine storage in ProLiant Virtual Console.
XenCenter does allow lvmohba SR to be used for virtual machine storage. When the SR is created by
XenCenter the content_type is set to a bland entry. The ProLiant Virtual Console uses the content field (for
virtual machine storage it looks for a content_type of user) to determine valid SRs that might be used to
store virtual machines. Because of the way the SR is created the SR is not useable.
A work-around is to use the
xe
command within
Dom0
to create the SR instead and set a content_type of
user on creation.
For iSCSI array:
xe
sr-create
host-uuid=<UUID of host>
name-label=<Name of SR>
shared=<true/false>
type=lvmoiscsi
content_type=user device-
config:target=<target ip address>
device-config:targetIQN=<target IQN
name>
device-config:SCSIid=<device SCSI id>
For a Fibre Channel array:
xe
sr-create
host-uuid=<UUID of host>
name-label=<Name of SR>
shared=<true/false>
type=lvmohba
content_type=user device-
config:device=/dev/mapper/<device SCSI id>
For more information see the Citrix XenServer 5.0 Admin Guide for additional details.
Creating a shared SR using PVC on a Fibre Channel
LUN can fail
Creating a shared SR on a Fibre Channel exposed storage might fail if you use the PVC New Storage
wizard to create the storage using the Local Storage option. PVC does not support creation of shared
virtual disk storage. To accomplish this task, use XenCenter or the
xe
CLI tool in Dom0 to provision
storage on a shared Fibre Channel LUN.
To use PVC to create virtual machines using this storage, see PVC does not recognize SR created using
XenCenter on FibreChannel or ISCSI storage. ("
PVC does not recognize for use a storage repository
created using XenCenter on Fibre Channel or iSCSI storage
" on page
5
)