HP: Integrity Virtual Machines:ΒΆ

Title:HP: Integrity Virtual Machines:
Author:Douglas O’Leary <dkoleary@olearycomputers.com>
Description:HP: Integrity Virtual Machines:
Date created:02/04/2011
Date updated:02/04/2011
Disclaimer:Standard: Use the information that follows at your own risk. If you screw up a system, don’t blame it on me...

I have to manipulate the HP IVM farm so infrequently, that, every time I do, I have to relearn the commands. This cheat sheet should provide command syntax

hpvmstatus
Displays summary status of the virtual machines running on the host
hpvmstatus -P ${ivm}
Displays detailed status of the virtual machine. Includes number of CPUs, memory, “disk” layout, network layout, and console
hpvmconsole -P ${ivm}
Connects to the virtual console for ${ivm}
hpvmdevmgmt
Displays the devices assigned/associated with the integrity virtual machines. A bit unreadable in this format
hpvmdevmgmt -a gdev:/dev/vgvmdata/rvgAS1ci_d2
Add the LV as a backin store to the IVM device database
hpvmdevmgmt -m gdev:/dev/vgvmdata/rvgAS1ci_d2:attr:SHARE=YES
Modifies the entry added previously to be shared. Please note the caps; they’re mandatory.
hpvmmodify -P r3db21v2 -a disk:avio_stor::lv:/dev/vgvmdata/rvgAS1ci_d2
Add the LV as a logical store to the virtual machine. Automatically updates the device management database. The few times I’ve done this, the devices have shown up automagically in the guest systems. Your mileage may vary.

If you’re adding disks to a pair of virtuals on the same host for clustering purposes, I’ve found this process to work best:

  1. Add the disks to the host
  2. Create the LV backstores
  3. Add the lvs to the dev mgmt tree (hpdevmgmt)
  4. Add the disks to one of the virtuals
  5. Update the dev mgmt tree to enable shared devices
  6. Add the disks to the second virtual.

Otherwise, I end up having to reboot one or the other virtual. Not sure what’s up with that, but there you go.