HP Integrity Virtual Machines Version 4.2 Release Notes

• Red Hat Enterprise Linux 4 Installation Guide for x86, Itanium, AMD64
• Intel Extended Memory 64 Technology (Intel EM64T)
• Red Hat Linux Customization Guide
For information about the SUSE Linux operating system for HP Integrity servers, see http://
docs.hp.com/en/linuxsuse.html
The guest parameter settings for Linux guests are listed in the HP Integrity Virtual Machines 4.2:
Installation, Configuration, and Administration manual.
For information about installing Linux guests, see the HP Integrity Virtual Machines 4.2: Installation,
Configuration, and Administration manual.
4.3.2.2 SUSE Linux Cloned Guests Boot-Disk Boot Problems
SUSE Linux (SLES) cloned guests have issues with the cloned guest boot disk. The first issue
occurs when a SLES Linux guest is cloned using a new boot device using the hpvmclone -b
option, the cloned guest requires updates in the elilo config file (elilo.conf) and the fstab
file with the new boot device's SCSI WWID before it can be booted to the multi-user mode. The
cloned guest's OS image on the new boot device still contains the orignal guest boot device's
SCSI WWID in these config files. Therefore, the cloned guest with the new boot device fails the
boot when it tries to access the original guest's boot device.
In SLES Linux, the boot config file /boot/efi/SuSE/elilo.conf and /etc/fstab file both
contain the guest boot disk's SCSI WWID. To correct this cloned boot disk boot problem, boot
the cloned guest to the "Rescue System" mode, then mount the cloned guest's boot-disk, root-file
system (where /etc/fstab resides) and boot file system (where elilo.conf resides), update
these config files with the cloned boot disk's SCSI WWID, and then reboot the guest.
The second issue involves the use of the hpvmmigrate command with the offline migration
and backing store copy. The offline-migrated guest encounters this boot failure when the backing
store copy completes and the migrated guest on the target host attempts to boot. This occurs
because the migrated guest's boot disk has been changed to the copied disk, which has a different
WWID.
To correct the cloned-guest, boot-disk boot problems, follow these steps:
1. Boot the guest to the Rescue System mode from the SLES Linux CD 1:
a. Configure the SLES Linux CD onto the guest for boot to the Rescue System mode:
# hpvmmodify -P cl_suse -a dvd:scsi:file:/iso/linux/SLES-10-SP2/SLES-10-SP2-DVD-ia64-RC5-DVD1.iso
b. Boot the guest:
# hpvmconsole -P cl_sue -fi -c "pc -on"
c. Interrupt the guest boot from the auto boot, then boot from the Linux CD:
1) Select the “Boot option maintenance menu” in the EFI menu.
2) Select the “Boot from a File” option.
3) Select the “Removable Media Boot” item. (This boots from the SLES Linux CD to
the Installation menu.
d. At the SLES Linux installation menu, select the item “Rescue System”.
e. At the Boot: text field, enter console=ttyS0 and press Return. This action boots the
guest to the Rescue login.
f. To log in, enter the user name, root, at the Rescue Login: prompt and press Return:
Rescue login: root
Rescue:~ #
2. Mount the guest's root file system /dev/sda3 and boot file system /dev/sda1:
Rescue:~ # mount /dev/sda3 /mnt
Rescue:~ # mount /dev/sda1 /boot
4.3 Linux Guests 47