HP Integrity Virtual Machines 4.2.5: Release Notes

5 Using Integrity VM Commands
This chapter contains notes about the Integrity VM commands.
5.1 Changes and Issues in This Release
The following sections describe changes, issues, and new information pertaining to this release.
5.1.1 Integrity VM Command Changes
The Integrity VM commands have changed in the following ways:
• The following new commands have been added:
◦ hpvmresume command
◦ hpvmsuspend command
◦ hpvmmove_suspend
NOTE: These commands are not supported with VMs as Serviceguard Nodes and VMs as
Serviceguard Packages.
5.1.2 Information Missing from hpvmmigrate -Y and -y Option Manpage
Descriptions
The hpvmmigrate -Y and -y options have the following effect:
• -Y skips encryption.
• -y forces encryption.
5.1.3 hpvmsuspend Manpage Missing -q Option
The -q option is missing from the hpvmsuspend manpage. This option sets the quiet flag, which
slightly reduces the messages.
5.2 Known Issues and Information
The following sections describe known issues and information from previous releases that still apply
to V4.2.5.
5.2.1 Boot-Problem Messages Now Found In Log File
Boot-problem messages generated by either the hpvmcreate, hpvmmodify, or hpvmstart
command and displayed on your screen are now also saved to your log file, /var/opt/hpvm/
common/command.log.
5.2.2 Display Output from Some Integrity VM Tools Might Change in Form and
Content
Specific display output from some Integrity VM tools, such as the hpvmstatus command, is
subject to occasional changes of form and content. Program scripts should always use
machine-readable output options (for example, hpvmstatus -M) whenever available to avoid
future script maintenance.
5.2.3 Enabling or Disabling Virtual CPUs Online
Starting with HP Integrity VM V4.2, it is possible to change the number of enabled CPUs in HP-UX
guests, using the hpvmmgmt –c num command. This command sets the number of enabled virtual
5.1 Changes and Issues in This Release 55