HP Integrity Virtual Machines Version 4.2 Release Notes

6 Guest Administration
This chapter contains information about managing Integrity VM guests.
6.1 Changes and Issues in this Release
There are no new guest administration issues in the V4.2 release.
6.2 Known Issues and Information
The following sections describe known issues and information from previous releases that still
apply to V4.2.
6.2.1 Specifying Maximum Entitlements
Under some conditions, when setting a guest's maximum entitlements to less than the default
(100%), the guest can be erroneously restricted to a fraction of the specified maximum entitlement.
When this happens, the guest receives fewer CPU cycles than it should, even when it appears
there is still unused CPU capacity on the VM Host. This patch kit corrects an issue with maximum
entitlements specified with the hpvmmodify -E min:max command and the hpvmmodify
-e min:max command. Entitlements achieved can be checked with the hpvmstatus -r
command.
6.2.2 gWLM and Integrity VM Incompatibility
There are apparent incompatibilities between gWLM and Integrity VM V4.0 and V4.1. HP
recommends not using gWLM to manage VM environments until these incompatibilities are
resolved. HP is working to correct this problem and intends to make a patch available as soon
as possible through the HP IT Resource Center (ITRC) website: http://www.itrc.hp.com.
6.3 Creating Virtual Machine Administrator and Operator Accounts
In versions of Integrity VM prior to A.03.00, only Admin console access is available, and only
one such account per guest is allowed. The administrator account name must match the guest
name. The new version of Integrity VM provides proper access controls and individual
accountability for these accounts. For more information, see Section 6.6 (page 62).
6.4 Administrator Account Names
Integrity VM Version 4.0 and later lifts the restriction that the virtual console administrator
account names must be the same as the guest name. As a result, the virtual console administrator
name can be any valid HP-UX login name. To continue accessing the virtual console, existing
guest console accounts must be added to the authorization list for the associated guest with the
usermod command. This allows multiple accounts to map to the guest, and requires the account
names to be valid HP-UX login strings.
Authorization of access to the virtual console is determined by the guest configuration file (set
using the -u and -g options to the hpvmcreate, hpvmmodify, and hpvmclone commands).
This controlled access allows you to temporarily block access by using the hpvmmodify command
to change the virtual console administrator account name.
6.5 Guest User Accounts
The configuration for captive hpvmconsole guest user accounts has changed in Integrity VM
Version 4.0 and later to support additional access controls and configurations. This change
requires that the guest user accounts have the correct home directory. It is also necessary to list
the console access account in the guest configuration file.
6.1 Changes and Issues in this Release 61