HP BL860c HP Integrity Virtual Machines Release Notes - Page 34
Actual Running Entitlement May Differ from Con d Entitlement
View all HP BL860c manuals
Add to My Manuals
Save this manual to your list of manuals |
Page 34 highlights
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. 5.7 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. 5.8 Maintain Minimum Entitlement The hpvmcreate and hpvmmodify commands do not allow the minimum CPU entitlement to be set below 5%. If you force the entitlements below 5%, boot time and potential runtime failures occur. Set entitlement percentages in integers, not fractions. Fractions are ignored. 5.9 Guest Memory Must Be a Multiple of 64 MB When you specify the guest memory, use a multiple of 64 MB. When a guest is created, Integrity VM rounds the guest memory up to the nearest multiple of 64 MB. However, if you specify a value that is not a multiple of 64 MB, the actual value can be rounded down, which may prevent the guest from booting. 5.10 Actual Running Entitlement May Differ from Configured Entitlement Displayed and reported guest entitlement settings can differ from values that are specified. This occurs when entitlement settings have a granularity of one percent of the VM Host CPU capacity. An entitlement specified in cycles can be rounded to an integral percentage of VM Host cycles. For example, if you specify the guest entitlement as -E 100 on a 900 MHz host system, it is rounded to 108 MHz (12%). 5.11 Duplicate Messages when Modifying Running Guests Using the hpvmmodify command to add zero-length files to file-backed virtual disks can result in duplicate warning messages. For example: # hpvmmodify -P test_duperr -a disk:scsi::file:/tmp/zero.size.1 \ -a disk:scsi::file:/tmp/zero.size.2 hpvmmodify: WARNING (test_duperr): File size of: 0 (bytes) for disk backing file: /tmp/zero.size.1 must be equal to or greater than: 512 (bytes), or the device may not show up in the guest when booted. hpvmmodify: WARNING (test_duperr): File size of: 0 (bytes) for disk backing file: /tmp/zero.size.2 must be equal to or greater than: 512 (bytes), or the device may not show up in the guest when booted. hpvmmodify: WARNING (test_duperr): File size of: 0 (bytes) for disk backing file: /tmp/zero.size.1 must be equal to or greater than: 512 (bytes), or the device may not show up in the guest when booted. hpvmmodify: WARNING (test_duperr): File size of: 0 (bytes) for disk backing file: /tmp/zero.size.2 must be equal to or greater than: 512 (bytes), or the device may not show up in the guest when booted. Remove the failing device from the guest configuration using the hpvmmodify command. 5.12 Manpages Display on Linux Guests The hpvmcollect and hpvminfo commands are available on Linux guests after installing the Linux guest management software kit, as described in the HP Integrity Virtual Machines Installation, Configuration, and Administration manual. To view the command displays properly, enter the following commands on the Linux guest: # export LANG=en_US.iso88591 # export TERM=vt200 34 Using Integrity VM Commands