Integrity Virtual Machine - EVA4000

[Fernando Jose P de Souz]

Hi,

I have a RX6600 server, HP-UX 11.23.
HP Integrity Virtual Machine installed.
I created 4 VMs.

but how can i present the fiber channel card to the VM?

or i apresent the vdisk for the VM server and the VM server create the Volume Group and present to the VM Host.

VM host: Output of ioscan -fn
don't appear fiber channel card.

qec-/# ioscan -fn
Class I H/W Path Driver S/W State H/W Type Description
============================================================================
root 0 root CLAIMED BUS_NEXUS
ioa 0 0 cec_gen CLAIMED BUS_NEXUS
ba 0 0/0 gh2p CLAIMED BUS_NEXUS Local Bus Adapter
lan 0 0/0/0/0 iether CLAIMED INTERFACE HP PCI/PCI-X 1000Base-T
ext_bus 0 0/0/1/0 mpt CLAIMED INTERFACE SCSI Ultra320
/dev/mpt0
target 0 0/0/1/0.0 tgt CLAIMED DEVICE
disk 0 0/0/1/0.0.0 sdisk CLAIMED DEVICE HP Virtual LvDisk
/dev/dsk/c0t0d0 /dev/dsk/c0t0d0s2 /dev/rdsk/c0t0d0 /dev/rdsk/c0t0d0s2
/dev/dsk/c0t0d0s1 /dev/dsk/c0t0d0s3 /dev/rdsk/c0t0d0s1 /dev/rdsk/c0t0d0s3
target 1 0/0/1/0.1 tgt CLAIMED DEVICE
disk 1 0/0/1/0.1.0 sdisk CLAIMED DEVICE HP Virtual LvDisk
/dev/dsk/c0t1d0 /dev/rdsk/c0t1d0
target 2 0/0/1/0.15 tgt CLAIMED DEVICE
ctl 0 0/0/1/0.15.0 sctl CLAIMED DEVICE Initiator
/dev/rscsi/c0t15d0
ba 1 0/0/3/0 legacyio CLAIMED BUS_NEXUS Legacy IO Core I/O Adapter (IFB)
tty 0 0/0/3/0/1 asio0 CLAIMED INTERFACE Built-in RS-232C
/dev/diag/mux0 /dev/mux0 /dev/tty0p0
ba 2 0/1 gh2p CLAIMED BUS_NEXUS Local Bus Adapter
ba 3 0/2 gh2p CLAIMED BUS_NEXUS Local Bus Adapter
ba 4 0/3 gh2p CLAIMED BUS_NEXUS Local Bus Adapter
ba 5 0/4 gh2p CLAIMED BUS_NEXUS Local Bus Adapter
ba 6 0/5 gh2p CLAIMED BUS_NEXUS Local Bus Adapter
ba 7 0/6 gh2p CLAIMED BUS_NEXUS Local Bus Adapter
ba 8 0/7 gh2p CLAIMED BUS_NEXUS Local Bus Adapter
processor 0 120 processor CLAIMED PROCESSOR Processor
processor 1 121 processor CLAIMED PROCESSOR Processor
ba 9 250 pdh CLAIMED BUS_NEXUS Core I/O Adapter
ipmi 0 250/0 ipmi CLAIMED INTERFACE IPMI Controller
/dev/ipmi
acpi_node 0 250/1 acpi_node CLAIMED INTERFACE Acpi Hardware
qec-/#

[Torsten.]

Hi,

the HPVM has (virtual) *ONLY* SCSI disks.
If you are using a FC disk (from an EVA) as backing storage, the HPVM will see this as a scsi disk - no problem.

The ioscan is from the HPVM, NOT from the host - right???


I see "HP Virtual LvDisk" devices, so you mapped LVOLs from the host to the HPVM.

Just do the same for the EVAs vdisk.

As mentioned, the HPVM will see them as scsi disks.

[Fernando Jose P de Souz]

This ioscan is the host:

qec-/# ioscan -fn
Class I H/W Path Driver S/W State H/W Type Description
============================================================================
root 0 root CLAIMED BUS_NEXUS
ioa 0 0 cec_gen CLAIMED BUS_NEXUS
ba 0 0/0 gh2p CLAIMED BUS_NEXUS Local Bus Adapter
lan 0 0/0/0/0 iether CLAIMED INTERFACE HP PCI/PCI-X 1000Base-T
ext_bus 0 0/0/1/0 mpt CLAIMED INTERFACE SCSI Ultra320
/dev/mpt0
target 0 0/0/1/0.0 tgt CLAIMED DEVICE
disk 0 0/0/1/0.0.0 sdisk CLAIMED DEVICE HP Virtual LvDisk
/dev/dsk/c0t0d0 /dev/dsk/c0t0d0s2 /dev/rdsk/c0t0d0 /dev/rdsk/c0t0d0s2
/dev/dsk/c0t0d0s1 /dev/dsk/c0t0d0s3 /dev/rdsk/c0t0d0s1 /dev/rdsk/c0t0d0s3
target 1 0/0/1/0.1 tgt CLAIMED DEVICE
disk 1 0/0/1/0.1.0 sdisk CLAIMED DEVICE HP Virtual LvDisk
/dev/dsk/c0t1d0 /dev/rdsk/c0t1d0
target 2 0/0/1/0.15 tgt CLAIMED DEVICE
ctl 0 0/0/1/0.15.0 sctl CLAIMED DEVICE Initiator
/dev/rscsi/c0t15d0
ba 1 0/0/3/0 legacyio CLAIMED BUS_NEXUS Legacy IO Core I/O Adapter (IFB)
tty 0 0/0/3/0/1 asio0 CLAIMED INTERFACE Built-in RS-232C
/dev/diag/mux0 /dev/mux0 /dev/tty0p0
ba 2 0/1 gh2p CLAIMED BUS_NEXUS Local Bus Adapter
ba 3 0/2 gh2p CLAIMED BUS_NEXUS Local Bus Adapter
ba 4 0/3 gh2p CLAIMED BUS_NEXUS Local Bus Adapter
ba 5 0/4 gh2p CLAIMED BUS_NEXUS Local Bus Adapter
ba 6 0/5 gh2p CLAIMED BUS_NEXUS Local Bus Adapter
ba 7 0/6 gh2p CLAIMED BUS_NEXUS Local Bus Adapter
ba 8 0/7 gh2p CLAIMED BUS_NEXUS Local Bus Adapter
processor 0 120 processor CLAIMED PROCESSOR Processor
processor 1 121 processor CLAIMED PROCESSOR Processor
ba 9 250 pdh CLAIMED BUS_NEXUS Core I/O Adapter
ipmi 0 250/0 ipmi CLAIMED INTERFACE IPMI Controller
/dev/ipmi
acpi_node 0 250/1 acpi_node CLAIMED INTERFACE Acpi Hardware
qec-/#

output of hpvmstatus the VM Server:

svt-/# hpvmstatus
[Virtual Machines]
Virtual Machine Name VM # OS Type State #VCPUs #Devs #Nets Memory Runsysid
==================== ===== ======= ========= ====== ===== ===== ======= ========
QEC 3 HPUX On (OS) 2 2 1 3 GB 0

[Torsten. · Accepted solution]

No it is the guest:

qec-/# ioscan -fn
...


svt-/# hpvmstatus
[Virtual Machines]
Virtual Machine Name VM # OS Type State #VCPUs #Devs #Nets Memory Runsysid
==================== ===== ======= ========= ====== ===== ===== ======= ========
QEC 3 HPUX On (OS) 2 2 1 3 GB 0

The guest is called "qec".




Anyway, from the host create a VG on the EVA, create a LVOL and assign it to the guest.

[Tim Medford]

Fernando - You cannot present the EVA disk directly to the VMs. You would present them to the VM Host, which would in turn use hpvm commands to present those EVA disks to the virtual hosts.

There is a lot of science behind this process and a number of performance factors to consider. For instance, you can present those EVA luns directly for maximum performance, but then you must have SecurePath in order to have path redundancy. You can use LVM on the host and PVLinks for path redundancy, but there is some performance penalty. It's also possible to present files to the VMs, which is the slowest alternative of all, but is best in terms of portability (if you want to vmmigrate the machines later).

Here are some command examples of presenting the disks to the VM:

Presenting a LVM logical volume:
hpvmmodify -P vmname -a disk:scsi::lv:/dev/vg01/rlvolBlah

Presenting a disk/EVA lun directly (after a pvcreate on the vm host)
hpvmmodify -P vmname -a disk:scsi::disk:/dev/rdsk/c6t0d4

Creating a file and presenting it:
hpvmdevmgmt -S 24G /vmhostfs/disk1
hpvmmodify -P vmname -a disk:scsi::file:/vmhostfs/disk1

Once these are complete, you can then run ioscan and insf -e on the VM and you will see the disks.

See these documents for more information:

http://docs.hp.com/en/T2767-90024/index.html
http://docs.hp.com/en/9983/BestPractices2.2.pdf
http://docs.hp.com/en/9985/TopTenTips2.5.pdf