HP Insight Control for Linux 6.0 Release Notes

The following items are missing from Section 23.26, Troubleshooting virtual machine
installation and setup problems:
Corrective actionsCause/Symptom
Follow this procedure:
1. Verify that virtual machine management has started:
# /etc/init.d/hpvmm status
2. Restart virtual machine management if necessary:
# /etc/init.d/hpvmm start
Virtual machine management might fail to start on
the CMS
In some cases, particularly for the RHEL 4.n release
stream, HP Insight Control virtual machine
management does not start properly after a reboot.
Renumber the Ethernet devices so that the device used
to PXE boot is eth0 (or at least a low number such as
1 or 2). On a RHEL OS, the procedure is:
1. Locate the ifcfg file for the external
interface/bridge (for example, eth6) and a lower
numbered external interface/bridge (for example,
eth0):
/etc/sysconfig/network-scripts/ifcfg-eth0
/etc/sysconfig/network-scripts/ifcfg-eth6
2. Change the numbering of these two interfaces by
swapping their file names:
# cd /etc/sysconfig/network-scripts
# mv ifcfg-eth0 ifcfg-hold
# mv ifcfg-eth6 ifcfg-eth0
# mv ifcfg-hold ifcfg-eth6
3. Change the DEVICE attribute in both files so that
each matches its new file name. For example, in the
new ifcfg-eth0 file, do the following
DEVICE=eth0 <-- this had been set to eth6
before the file was renamed
BOOTPROTO=dhcp
HWADDR=00:0E:7F:B0:9B:13
ONBOOT=yes
4. Make the same change to the ifcfg-eth6 file.
Xen bridge fails to start if an Ethernet device is
numbered too high
On a server with multiple NICs, the Xen bridge does
not start when the main device number is too high (for
example, eth6).
3.3.11 Correction to Chapter 23, Troubleshooting
Substitute the following for the table entry describing “ESX 3.5 Kickstart installation hangs
prompting for disk information” in section 23.26:
Corrective actionCause/Symptom
When VMware ESX 3.x is installed, it may not be able to
determine the state of the partition table on the target
disk, resulting in a prompt on the console to acknowledge
the creation of a new partition table.
Acknowledging the request allows the installation to
proceed.
A complete erasure of the disk (writing zeroes to the disk)
also prevents this situation, however, it may be
time-consuming, depending on the size of the disk.
Use the following command to write zeroes to the disk:
# dd if=/dev/zero of=path-to-disk
Disk error or hang prompting for disk information
occurs during ESX 3.x Kickstart installation
34 Documentation notes