HP Integrity Virtual Server Manager 6.2 User Guide

NOTE: The list of possible backing devices for the storage device you want to add can
include file and directory backing devices that have not been associated with a particular VM
or vPar, or that were associated with VMs or vPars that have been removed or from which
the associated virtual devices have been removed.
You can create a file as a backing storage device for a virtual disk. You can add DVD burners,
tape devices, and changers if they are emulated SCSI adapters; they are added as attached
devices. You cannot use Integrity Virtual Server Manager to add an attached AVIO device;
to add such a device to a VM or vPar, use the hpvmdevmgmt command at the VSP. For more
information, see the Modify→Add Storage Device ... help topic.
NOTE: If you use Integrity Virtual Server Manager to manage a VSP running Integrity VM
Version 3.5 or earlier, Integrity Virtual Server Manager does not fully support virtual device
special files located in /hpap (introduced in HP StorageWorks Secure Path software Version
3.0F SP2) as backing devices for virtual storage. When you use Integrity Virtual Server Manager
to add a storage device on a VM, Integrity Virtual Server Manager does not display device
files in /hpap as possible backing devices to choose from. If a virtual storage device using
an /hpap device special file already exists on a VM managed by Integrity Virtual Server
Manager, Integrity Virtual Server Manager displays it on the VSP Storage and VM Properties
Storage tabs as an unknown device (using the question mark icon, ). Integrity Virtual Server
Manager displays the correct device special file name (for example, /hpap/rdsk/hpap1)
but the box representing this device is not connected to the boxes that represent the physical
storage devices associated with that virtual device special file. In general, Integrity Virtual
Server Manager correctly displays only those device special files located in /dev.
To add a virtual storage device that uses a virtual device special file in /hpap to an existing
VM on a VSP running Integrity VM Version 3.5 or earlier, use the Integrity VM hpvmmodify
command. For more information about these commands, see the HP-UX vPars and Integrity
VM Administrator Guide manual.
• Add Network Device to add network devices and vswitches for VMs.
NOTE: Any network or storage devices that you add are not functional on the VM until the VM
or vPar is started or restarted. When you add an I/O device to a started VM, it might not appear
on the Network or Storage tab until the VM is stopped or restarted. For a started vPar, network or
storage cannot be modified. If you add an I/O device to a stopped VM or vPar, the tab displays
the device immediately.
NOTE: If the VM being modified is an HP Serviceguard package, you must make the same
modifications to the VM on the other VSPs in the cluster.
Starting VMs
Starting a VM starts the virtual hardware for the VM. The VM enters an On state (powered on).
The Start and Restart functions are similar except the Start function does not stop and restart a VM
that is already started (it leaves the started machine as is), while the Restart function does. Use
Restart instead of Start when you have several VMs that you want newly started, some which are
already started and some currently stopped. The Restart function takes care of all the VMs (in
contrast, the Start function does not restart the already started machines). If you do not want the
already started machines stopped and restarted (you just want the stopped machines started), use
the Start function instead. For information about restarting VMs, see “Restarting VMs” (page 93).
NOTE: You cannot start a VM that is currently migrating online. You must wait until migration
completes. If the selected VM has migrated to another VSP (the target), the VM (on the source VSP)
is in the Not Runnable state: you cannot start a VM in this state.
To start one or more selected VMs, perform the following steps.
90 Working with VMs or vPars