Jump to content United States-English
HP.com Home Products and Services Support and Drivers Solutions How to Buy
» Contact HP
More options
HP.com home
HP Integrity Virtual Machines Version 4.0 Installation, Configuration, and Administration > Chapter 7 Creating Virtual Storage Devices

Using Integrity VM Storage

» 

Technical documentation

Complete book in PDF
» Feedback
Content starts here

 » Table of Contents

 » Glossary

 » Index

The following sections describe the roles of individuals accessing virtual storage, the commands they use, and some examples of using Integrity VM storage.

Integrity VM Storage Roles

This section describes the roles that individuals play in working with Integrity VM storage. Each role has different responsibilities in using Integrity VM storage. The roles might be played by one or more individuals depending on security requirements and skill sets. The three roles are:

VM Host Administrator

The VM Host administrator role is an individual responsible for the proper configuration and maintenance of the VM Host for running virtual machines. As such, this person needs complete access to the VM Host to install hardware and software. This person also needs to understand how to do HP-UX system maintenance, how to configure hardware properly, and how to set up and use various software applications and tools.

The VM Host administrator uses the following commands to manage virtual machine storage devices:

Management FunctionIntegrity VM Command
Add, delete, manage, and modify virtual machine storage devices.hpvmmodify (see Section )
Display information about the storage devices for a virtual machine.hpvmstatus (see Section )

Once a resource is added or attached to a virtual machine and the virtual machine is powered on, the storage resource is owned by the guest administrator. That is, the guest OS may access that storage resource at any time. A deletion, detachment or modification fails if any guest I/O is active on the resource. Dynamic storage changes on an active virtual machine must be approved by the guest administrator.

Guest Administrator

The VM Guest Administrator is responsible for the proper maintenance of a guest OS. As such, this person needs access to the virtual console by the VM Host administrator to control the virtual machine. The guest administrator must understand how to maintain the guest OS, install patches and applications, and set up security for the guest users of the guest OS. Additionally, Integrity VM storage requires you to:

  • Install any specific guest OS patches required by Integrity VM for proper OS operation on the virtual platform.

  • Review and understand any Integrity VM storage release notes that are specific to the guest OS.

  • Work with the VM Host administrator to complete virtual storage changes, including managing attached VM Host devices.

The guest administrator uses the virtual console to modify virtual storage. The virtual console is used to change discs of a virtual DVD device type. All modifications are bounded by what the VM Host administrator configures for the virtual machine.

The virtual console commands are available from the vMP Main Menu, using the hpvmconsole command or by pressing Ctrl/B if you are already connected . The virtual console commands eject (ej) and insert (in) allow you to control the DVD device. Both commands provide submenus for displaying devices that are removable. Selecting options through the submenus completes the ejection/insertion process.

Management FunctionIntegrity VM Command
Eject a virtual DVD.vMP> ej
Insert a virtual DVDvMP> in

Guest User

The guest user runs applications on a guest OS. Access is provided and limited by the guest administrator. There are no Integrity VM storage requirements for application users of the guest OS.

There are no Integrity VM storage commands for application users in the guest OS. The guest users use Integrity VM storage on the guest OS the same way as they normally use storage on an HP Integrity server. Any required Integrity VM storage changes must be directed to the guest administrator or VM Host administrator.

Integrity VM Storage Use Cases

This subsection describes ways to use the Integrity VM storage commands.

Adding Virtual Storage Devices

A VM Host administrator adds or attaches Integrity VM storage using the hpvmstatus and hpvmmodify commands. Virtual storage devices can be added or attached while the virtual machine is powered on or off. A new virtual storage adapter can be added only when the virtual machine is off. The virtual storage adapter can have up to 30 VIO storage devices or up to 128 AVIO devices total (the number of virtual and attached devices.)

The process to add or attach a virtual storage device to a guest is as follows:

  1. Based on the all Integrity VM storage considerations, choose a storage device to add.

  2. Based on the device type, set up and configure the VM Host to form a valid resource statement. This includes accounting VM Host resources to avoid future storage conflicts.

  3. Use the valid resource statement with the hpvmmodify command to add or attach the Integrity VM storage device.

The resource statement for adding an Integrity VM storage device does not require virtual hardware addressing. If the PCI bus, slot and SCSI target numbers are not specified, Integrity VM automatically chooses the first position available for the device. For example:

# hpvmmodify -P myvmm -a disk:scsi::disk:/dev/rdisk/disk7 # hpvmstatus -P myvmm .. [Storage Interface Details] ... disk scsi 0 1 0 0 0 disk /dev/rdisk/disk5 disk scsi 0 1 0 1 0 disk /dev/rdisk/disk7

To add an AVIO storage device with whole disk as the backing store, specify the following:

host# hpvmmodify -P guest1 -a hba:avio_stor:0,5,0:disk:/dev/rdisk/disk7
NOTE: You can achieve higher guests performance for HP-UX 11i v3 guests by configuring as many AVIO storage adapters as the number of virtual CPUs in the guest. The pcibus, pcislog, and scistgt portions need to be explicitly specified for each device. For example, a resource statement for a 4–vCPU guest takes the following form:
-a disk:avio_stor:1,0,0:disk:/dev/rdisk/disk1 -a disk:avio_stor:1,1,0:disk:/dev/rdisk/disk2 -a disk:avio_stor:1,2,0:disk:/dev/rdisk/disk3 -a disk:avio_stor:1,4,0:disk:/dev/rdisk/disk4

Deleting VM Storage Devices

A VM Host administrator deletes or detaches Integrity VM storage using the hpvmstatus and hpvmmodify commands. Integrity VM storage devices can be deleted or detached while the virtual machine is powered on or off. An Integrity VM storage adapter can only be removed when the virtual machine is off. The Integrity VM storage adapter is automatically removed when the last Integrity VM storage device connected to the adapter is removed.

The process to delete or detach a virtual storage device from a virtual machine is as follows:

  1. Use the hpvmstatus command to locate the resource to verify whether the virtual machine is powered on. If the virtual machine is on, consult with the guest administrator to obtain permission to remove the resource before proceeding.

  2. Use the hpvmmodify command to delete or detach the resource.

  3. Verify that the VM Host resource is no longer being used by the virtual machine.

The resource statement for deleting an Integrity VM storage device does not require virtual hardware addressing. For example:

# hpvmstatus -P myvmm ... [Storage Interface Details] ... disk scsi 0 1 0 0 0 disk /dev/rdisk/disk5 disk scsi 0 1 0 1 0 disk /dev/rdisk/disk7 disk scsi 0 1 0 2 0 disk /dev/rdisk/disk9 # hpvmmodify -P myvmm -d disk:scsi::disk:/dev/rdisk/disk7 # hpvmstatus -P myvmm ... [Storage Interface Details] disk scsi 0 1 0 0 0 disk /dev/rdisk/disk7 disk scsi 0 1 0 2 0 disk /dev/rdsk/disk9

To delete an AVIO storage device, specify the following:

host# hpvmmodify -P guest1 -d hba:avio_stor:0,5,0

Modifying VM Storage Devices

The VM Host administrator or the guest administrator can modify an Integrity VM storage device. The VM Host administrator can use the hpvmstatus and hpvmmodify commands to change the virtual media of virtual devices. The guest administrator uses the virtual console to change the virtual media of virtual DVDs. All attached devices are modified using physical VM Host access.

When the VM Host administrator uses the hpvmstatus and hpvmmodify commands to modify the virtual media of a virtual device, the operation is seen by the guest OS as a whole-disk replacement or a DVD removable media event, depending on the device type.

The process for modifying the virtual media of a virtual device is as follows:

  1. Use the hpvmstatus command to locate the virtual device resource to modify and to see if the virtual machine is powered on. If the virtual machine is on, consult with the guest administrator to before proceeding to replace the virtual media.

  2. Based on the Integrity VM storage considerations, choose a new virtual media type to add.

  3. Based on the virtual media type, set up and configure the VM Host to form a valid VM Host storage specification. Take into account the other demands on VM Host resources to avoid virtual machine storage conflicts.

  4. Use the VM Host storage specification with the hpvmmodify command to modify the virtual device resource.

  5. Verify that the old VM Host resource is no longer in use by a virtual machine.

  6. When run on an active virtual machine and with a storage device managed by avio_stor HBA, the VM guest needs to run the gvsdmgr command prior to using the modified backing store. For information about the gvsdmgr utility, see the HP-UX gvsdmgr(1M) manpage.

The resource statement for modifying a virtual device requires virtual hardware addressing (see Section ). For example:

# hpvmstatus -P myvmm ... [Storage Interface Details] ... disk scsi 0 1 0 0 0 disk /dev/rdisk/disk5 disk scsi 0 1 0 1 0 disk /dev/rdisk/disk7 disk scsi 0 1 0 2 0 disk /dev/rdisk/disk9 # hpvmmodify -P myvmm -m disk:scsi::0,1,1:lv:/dev/rdisk/disk2 # hpvmstatus -P myvmm ... [Storage Interface Details] ... disk scsi 0 1 0 0 0 disk /dev/rdisk/disk7 disk scsi 0 1 0 1 0 lv /dev/rdisk/disk2 disk scsi 0 1 0 2 0 disk /dev/rdisk/disk9

To complete a DVD ejection and insertion, follow the virtual console menus. However, new media selections might require the help of the VM Host administrator. Changes through the virtual console are not saved across guest OS reboots

If the VM Host administrator sets up a Virtual DVD for the virtual machine, the virtual console eject and insert command unlock and lock the physical VM Host CD/DVD drive. The eject command changes the Virtual DVD into a Virtual NullDVD in the VM, unlocking the VM Host CD/DVD drive in the process. The physical media in the VM Host CD/DVD drive can then be changed by the VM Host administrator or the guest administrator if access is permitted. Once the media has been changed, the insert command can be used to change the Virtual NullDVD back into a Virtual DVD, locking the VM Host CD/DVD drive and making the newly loaded media now accessible by the virtual machine. For example:

# diskinfo /dev/rdisk/disk7 SCSI describe of /dev/rdisk/disk7: vendor: HP product id: Virtual DVD type: CD-ROM size: 665600 Kbytes bytes per sector: 2048 vMP> ej Ejectable Guest Devices Num Hw-path (Bus,Slot,Tgt) Gdev Pstore Path ------------------------------------------------------------------------- [1] 0/0/1/0.7.0 (0,1,7) dvd disk /dev/rdisk/disk7 Enter menu item number or [Q] to Quit: 1 Confirm eject action G - Go F - Force Enter menu item or [Q] to Quit: G vMP> co # diskinfo /dev/rdisk/disk7 SCSI describe of /dev/rdisk/disk7: vendor: HP product id: Virtual NullDVD type: CD-ROM size: 0 Kbytes bytes per sector: 0 vMP>

After inserting a new disk on the VM Host CD/DVD drive, enter the following:

vMP> in Insertable Guest Devices Num Hw-path (Bus,Slot,Tgt) Gdev -------------------------------------------- [1] 0/0/1/0.7.0 (0,1,7) dvd Enter menu item number or [Q] to Quit: 1 Insertable File Backing Stores Num File --------------------- [1] /dev/rdisk/disk7 Enter menu item number or [Q] to Quit: 1 Confirm insertion action G - Go F - Force Enter menu item or [Q] to Quit: G vMP> co # diskinfo /dev/rdisk/disk7 SCSI describe of /dev/rdisk/disk7: vendor: HP product id: Virtual DVD type: CD-ROM size: 4300800 Kbytes bytes per sector: 2048

To modify an existing AVIO storage backing store, specify the following:

host# hpvmmodify -P guest1 -m hba:avio_stor:0,5,0:disk/dev/rdisk/disk7

In this command, avio_stor indicates the “from” adapter and the “bus,dev” specification indicates the bus and device list of storage targets to convert.

To modify an existing SCSI storage device to be an AVIO storage device, specify the following:

host# hpvmmodify -P guest1 -m hba:avio_stor:0,5
NOTE: Only HP-UX guests can use AVIO, and the backing store can be only file, disk or volume. There is no attached AVIO device support, and guests can be only disk or DVD.

This command string modifies an existing SCSI device adapter with some number of device targets to use the AVIO device adapter. The command has the following restrictions:

  • Each of the backing store devices under the SCSI HBA must be supported AVIO devices and adhere to storage type limitations.

  • All targets to be converted must list the same device adapter type.

  • The command can be executed only on a guest that is stopped.

  • Multiple adapter entries can be placed on the same command line. For example:

    hpvmmodify -P guest1 -m hba:avio_stor:0,5 -m hba:avio_stor:0,6

    The modification can also be reversed to the original SCSI adapter:

    hpvmmodify -P guest1 -m hba:scsi::0,5

    The following example shows how to convert scsi to avio_stor:

    # hpvmstatus  -P guest1 -d
    ...
    [Virtual Machine Devices]
    
    [Storage Interface Details]
    disk:scsi::0,5,0:disk:/dev/rdisk/disk0
    disk:scsi::0,5,1:disk:/dev/rdisk/disk1
    disk:scsi::0,5,2:disk:/dev/rdisk/disk2
    disk:scsi::0,5,3:disk:/dev/rdisk/disk3
    disk:scsi::0,5,4:disk:/dev/rdisk/disk4
    ...
    
    # hpvmmodify -P guest1 -m hba:avio_stor:0,5
    # hpvmstatus -P guest1 -d 
    ...
    [Virtual Machine Devices]
    
    [Storage Interface Details]
    hba:avio_stor:0,5,0:disk:/dev/rdisk/disk0
    hba:avio_stor:0,5,1:disk:/dev/rdisk/disk1
    hba:avio_stor:0,5,2:disk:/dev/rdisk/disk2
    hba:avio_stor:0,5,3:disk:/dev/rdisk/disk3
    hba:avio_stor:0,5,4:disk:/dev/rdisk/disk4
    ...
    

Prior to running the hpvmmodify command shown previously, devices unsupported by AVIO need to be moved to a new HBA, using the hpvmmodify delete and add operations.

NOTE: Guest operating systems, applications, or configuration files sensitive to device names or hardware paths need to be repaired after the move. Because HP-UX 11i v3 supports the agile device naming model, 11i v3 guest applications using agile device names are not affected as long as they are configured with disk backing stores.

HP recommends the use of agile device names for guest configurations to avoid problems when VM Hosts are reconfigured.

If the VM Host administrator sets up a Virtual FileDVD for the virtual machine, the virtual console options to eject and insert are used to select among the ISO files provided in the file directory for the Virtual FileDVD. The eject command changes the Virtual FileDVD into a Virtual NullDVD device. ISO files can be added to or removed from the file system directory for the Virtual FileDVD by the VM Host administrator. Once this ISO file directory is updated, use an insert command to view all the newly available ISO files in the directory and to choose one to be used for a new Virtual FileDVD. It is not necessary to change the file directory between each eject and insert operation. The guest administrator can change the ISO files provided in the file directory without any VM Host administrator interaction. For example:

# diskinfo /dev/rdisk/disk0 SCSI describe of /dev/rdisk/disk0: vendor: HP product id: Virtual FileDVD type: CD-ROM size: 665600 Kbytes bytes per sector: 2048 vMP> ej Ejectable Guest Devices Num Hw-path (Bus,Slot,Tgt) Gdev Pstore Path ------------------------------------------------------------------------- [1] 0/0/1/0.7.0 (0,1,7) dvd file /var/opt/hpvm/ISO-images/hpux/IOTdisc Enter menu item number or [Q] to Quit: 1 Confirm eject action G - Go F - Force Enter menu item or [Q] to Quit: G vMP> co vm # diskinfo /dev/rdisk/disk0 SCSI describe of /dev/rdisk/disk0: vendor: HP product id: Virtual NullDVD type: CD-ROM size: 0 Kbytes bytes per sector: 0 vMP> in Insertable Guest Devices Num Hw-path (Bus,Slot,Tgt) Gdev -------------------------------------------- [1] 0/0/1/0.7.0 (0,1,7) dvd Enter menu item number or [Q] to Quit: 1 Insertable File Backing Stores Num File --------------------- [1] 0505-FOE.iso [2] 0512-FOE.iso [3] 0603-FOE-D1.iso [4] 0603-FOE-D2.iso [5] IOTdisc Enter menu item number or [Q] to Quit: 1 Confirm insertion action G - Go F - Force Enter menu item or [Q] to Quit: G vMP> co # diskinfo /dev/rdisk/disk0 SCSI describe of /dev/rdisk/disk0: vendor: HP product id: Virtual FileDVD type: CD-ROM size: 3686144 Kbytes bytes per sector: 2048

For attached devices, modifications are made physically on the device. The guest OS supplies commands for loading and unloading tapes using media changers. But loading new media into the media changer, changing tapes in standalone drives, and changing discs with CD/DVD burners are accomplished manually. This process requires cooperation between the VM Host administrator and the guest administrator.

Printable version
Privacy statement Using this site means you accept its terms Feedback to webmaster
© 2008 Hewlett-Packard Development Company, L.P.