HP vPars and Integrity Virtual Machines V6.1 Release Notes

• Cannot dynamically add, delete, modify DIO functions online (that is, virtual OLRAD); such
hpvmmodify operations have to be done when the vPar/VM is down.
• Removing hpvmdio-owned devices while the VSP is down might result in broken VM
configurations that must be fixed manually.
• Cannot dynamically add, remove vPar/VM memory with DIO functions assigned.
• No Online VM Migration support.
• No suspend and resume support for vPars/VMs configured with DIO. These operations fail if
the vPar/VM has a DIO device.
• No firmware upgrades to DIO devices inside the vPar/VM.
• No more than 16 DIO functions can be assigned to a single vPar/VM
• No support for HP Auto Port Aggregation (APA).
3.1.8 No warnings when attempting to change memory size of a running vPar
It is not possible to change the memory size of a running vPar. However; the hpvmmodify command
and the vparmodify command do not print any warnings or errors if this is attempted.
3.1.9 The hpvmmodify command might fail when it should succeed
The hpvmodify command invoked on a running VM might fail when it should succeed. When
failing, the following error message is displayed:
resource intent failed 'Can't get the resource maxima.'
vPar/VM vm_name configuration problems:
Error 1: Internal error -1 when attempting to use the ragent 'intent' interface
hpvmmodify: Unable to modify the vPar or VM.
This failure might happen only when the same processor is used by several VMs.
3.1.10 The hpvmmodify command might succeed when it should fail
When the hpvmmodify command is invoked on a running VM to increase its minimum entitlement
( -e option), it might succeed when it should fail. In this case, the hpvmmodify command displays
the following warning message:
# hpvmmodify -P vm_name -e minimum entitlement
vPar/VM vm_name configuration problems:
Warning 1: vPar/VM CPUs (n) greater than available limit (0).
These problems may prevent the vPar or VM vm_name from starting.
hpvmmodify: The modification process is continuing.
hpvmmodify: The modification process is continuing.
As a consequence, a reserved VM might not be able to start, because not enough CPU is available.
Another consequence is that the VSP resources might become overcommitted:
# hpvmstatus -S
[HPVM Server System Resources]
*** VSP resources are over-committed ***
vPar/VM types supported by this VSP = vPar, Shared
Processor speed = 1595 Mhz
.
.
To work around this overcommitted condition, reduce the minimum entitlement of the VM whose
entitlement increase created the condition.
3.1.11 Converting VMs to vPars causes LAN IDs to shift
The I/O hardware paths on VMs do not have a cell number in the path. For vPars, I/O resources
are shown under a cell, and because of that, I/O hardware paths have an additional "0/" prefix.
3.1 Changes and Issues in this Release 15