HP Integrity Virtual Machines 4.2: Installation, Configuration, and Administration

/dev/rtape/tape6_BESTn:CONFIG=gdev,EXIST=YES,SHARE=NO,DEVTYPE=ATTACH,SHARE_LUNPATHS=YES:
lunpath3,lunpath6,lunpath5,lunpath4:0x01.0x00.0x03.0x500104f0004732d8
7.1.3.3.1 Sharing Conflicts
You cannot share a device when a mixture of VIO and AVIO usage is specified; however, you
can configure two guests with one guest using a device with VIO access and the other guest
using a device with AVIO access.:
# hpvmmodify -P guest1 -a tape:scsi::attach:/dev/pt/pt_tape6
# hpvmmodify -P guest2 -a tape:avio_stor::attach_path:0/4/1/0.0x500104f0004732d9.0x0
Any attempt to boot both guests at the same time results in the second guest being blocked from
booting. Setting the value of either SHARE or SHARE_LUNPATHS attributes to YES has no effect
on this restriction:
# hpvmstatus
[Virtual Machines]
Virtual Machine Name VM # OS Type State #VCPUs #Devs #Nets Memory Runsysid
==================== ===== ======= ========= ====== ===== ===== ======= ========
guest1 2 UNKNOWN On (EFI) 1 1 0 100 MB 0
guest2 3 UNKNOWN Off 1 1 0 100 MB 0
# hpvmstart -P guest2
hpvmstart: ERROR (host): Device: '/dev/rtape/tape6_BESTn' is in use by another guest. Lunpath cannot be used
at the same time that the device special file is in use by a guest.
HPVM guest guest2 configuration problems:
Warning 1 on item 0/4/1/0.0x500104f0004732d9.0x0: Device file '0/4/1/0.0x500104f0004732d9.0x0' in use by
another guest.
These problems may prevent HPVM guest guest2 from starting.
hpvmstart: Unable to continue.
The following example shows that two guests are configured with the same tape device, each
using a different hardware path, where both hardware paths use the same initiator:
# hpvmstatus -d -P guest1 | grep tape
tape:avio_stor:0,0,0:attach_path:0/4/1/0.0x500104f0004732d9.0x0
# hpvmstatus -d -P guest2 | grep tape
tape:avio_stor:0,0,0:attach_path:0/4/1/0.0x500104f0004732da.0x0
List devices configured using tape 6 (Note that SHARE_LUNPATHS=YES.):
# hpvmdevmgmt -l all | grep lunpath | grep tape6
/dev/rtape/tape6_BESTn,/dev/pt/pt_tape6:CONFIG=gdev,EXIST=YES,SHARE=NO,DEVTYPE=ATTACH,SHARE_LUNPATHS=YES:
lunpath6,lunpath5:0x01.0x00.0x03.0x500104f0004732d8
0/4/1/0.0x500104f0004732d9.0x0,lunpath3:CONFIG=gdev,EXIST=YES,SHARE=NO,DEVTYPE=ATTACHPATHLUN,AGILE_DSF=
/dev/rtape/tape6_BESTn:guest1:0x01.0x00.0x03.0x500104f0004732d8_lunpath3
0/4/1/0.0x500104f0004732da.0x0,lunpath5:CONFIG=gdev,EXIST=YES,SHARE=NO,DEVTYPE=ATTACHPATHLUN,AGILE_DSF=
/dev/rtape/tape6_BESTn:guest2:0x01.0x00.0x03.0x500104f0004732d8_lunpath5
The following example shows that one guest is running:
# hpvmstatus | grep guest
guest1 2 UNKNOWN On (EFI) 1 1 0 100 MB 0
guest2 3 UNKNOWN Off 1 1 0 100 MB 0
#
The following example shows that the second guest cannot be started:
# hpvmstart -P guest2
hpvmstart: ERROR (host): Device: '0/4/1/0.0x500104f0004732da.0x0' associated with guest: 'guest2' conflicts
with device:
'0/4/1/0.0x500104f0004732d9.0x0' associated with guest: 'guest1'. Both guests cannot be booted at the same
time because both
devices use the same initiator, even though SHARE_LUNPATHS is set to YES.
HPVM guest guest2 configuration problems:
Warning 1 on item 0/4/1/0.0x500104f0004732da.0x0: Device file '0/4/1/0.0x500104f0004732da.0x0' in use by
another guest.
These problems may prevent HPVM guest guest2 from starting.
hpvmstart: Unable to continue.
98 Creating Virtual Storage Devices