Integrity VM Commands

Using hpvmmodify -N -s options together causes guest to be inaccessable

Using the hpvmmodify -N and -s options together can cause the guest to disappear from the hpvmstatus output and become inaccessable. The guest directory name is erroneously changed, but the guest_name in the guest configuration files still have the original guest names.

To correct this problem, change that guest name back to the original guest name using the following command:

# mv /var/opt/hpvm/guest/guest_new_name to /var/opt/hpvm/guest/guest_original_name

The hpvmmodify command reevaluates guest configurations

When you use the hpvmmodify command to modify a guest, the entire guest configuration is reevaluated. Any problems that might prevent the guest from starting are reported. For example, if a guest has a reference to a host device that no longer exists, and you enter an hpvmmodify command that modifies the guest but does not fix the bad reference, a warning message is generated.

The hpvmdevmgmt command truncates file sizes

When you use the -S option on the hpvmdevmgmt command to specify a file size, anything after the initial whole integer is ignored. For instance, both the hpvmdevmgmt -S 1G command and the hpvmdevmgmt -S 1.5G command create a 1 GB file.

Setting devices to sharable can lead to device conflicts

Integrity VM allows Virtual FileDVDs to be shared by guests. With HP Serviceguard, you can share Virtual Disks. Other types of storage devices are not supported for sharing and cannot be allocated to multiple guests. Be careful when you set a virtual device to sharable using the hpvmdevmgmt command. Incorrectly marking a virtual device as sharable can lead to device conflicts and data corruption if multiple guests access it concurrently. In particular, attached devices (tape, burner, or changer) should not made sharable.

Errors on displaying guest or vswitch information while that information is being modified

The hpvmstatus, hpvmmodify, hpvmcreate, hpvmclone, and hpvmremove commands might return the following error when another command accesses the same guest's configuration files at the same time:

hpvm_guest_get_state:103:No Guest by that name or number

If you receive this error when you try to display a guest or vswitch configuration, enter the command again.

Do not attempt to remove busy virtual devices

Before removing virtual devices with the hpvmmodify command, make sure that the guest operating system is no longer directing I/O to the device. Unmount the device if it is mounted. If you attempt to remove a device that has I/O in progress, the hpvmmodify command incorrectly removes the device from the guest configuration file. The hpvmstatus command no longer displays the device, and the hpvmmodify command does not retry the device removal, but the guest operating system sees the device as available. To remove the device, restart the guest.

Missing uuid or .vmid files

If you use Integrity VM commands while guests are being removed, you may receive errors about missing uuid or .vmid files. Enter the command after the guest removal has completed.

Maintain minimum entitlement

The hpvmcreate and hpvmmodify commands do not allow the minimum CPU entitlement to be set below 5%. Forcing entitlements below 5% causes errors at boot time and potential runtime failures. Set entitlement percentages in integers, not fractions. Fractions are ignored.