Modifying Virtual Machines

Virtual Machine vCPU Entitlement to modify the processor entitlement of a selected virtual machine. If supported by the version of Integrity VM running on the VM Host, you can modify the entitlement cap. An entitlement cap is the maximum amount of computing power allotted to a virtual machine for each vCPU.

	NOTE: If the virtual machine is being managed by gWLM, you cannot modify the vCPU entitlement. When you access the Virtual Machine vCPU Entitlement page, the following error message is displayed, where virtual-machine-name is the name of the virtual machine: The processor entitlement for VM virtual-machine-name cannot be modified because it is being managed by gWLM. To adjust the processor entitlement for this VM, use gWLM to change the policy associated with this VM. To create or modify the gWLM policy for this virtual machine, use the Policy menu (available when using VM Manager with VSE Management Software).

Virtual Machine Memory to modify the amount of memory for a selected virtual machine. If the VM Host has Integrity VM 3.0 or later installed and the OS type for the VM supports dynamic memory, the dynamic memory parameters are shown, and you can modify them. Changes to memory take effect when the virtual machine is restarted.

Virtual Machine vCPU Count to modify the number of virtual CPUs for a selected virtual machine. If supported by the version of Integrity VM running on the VM Host, you can modify the minimum and maximum number of vCPUs to be allotted to the virtual machine. Changes take effect when the virtual machine is restarted.

Virtual Machine VLAN Settings to modify the VLAN associated with the virtual machine.

Virtual Machine Hardware Auto Start to specify whether the virtual machine should start automatically when Integrity VM is started or whether the virtual machine will be started manually.

WBEM Credentials to set and change WBEM credentials for virtual machines.

Add Storage Devices to Virtual Machine to add storage devices for virtual machines.

	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 virtual machine, or that were associated with virtual machines that have been removed or from which the associated virtual devices have been removed. For more information, see the ModifyAdd Storage Device to Virtual Machine... help topic.If you use VM Manager to manage a VM Host running Integrity VM version 3.5 or earlier, VM 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 VM Manager to add a storage device on a virtual machine, VM 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 virtual machine managed by VM Manager, VM Manager displays it on the VM Host Storage and VM Properties Storage tabs as an unknown device (using the question mark icon, ). VM 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, VM 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 virtual machine on a VM Host running Integrity VM version 3.5 or earlier, use the Integrity VM hpvmmodify command. For more information about these commands, see the HP Integrity Virtual Machines Installation, Configuration, and Administration manual.

Add Network Device to Virtual Machine to add network devices and vswitches for virtual machines.