Jump to content United States-English
HP.com Home Products and Services Support and Drivers Solutions How to Buy
» Contact HP
More options
HP.com home
 HP Integrity Virtual Machines Version 4.0 Release Notes > Chapter 1 Introduction

SUSE Linux Cloned Guests Boot-Disk Boot Problems
» 

Technical documentation

Complete book in PDF
» Feedback
Content starts here

 » Table of Contents

 » Index

spacerspacerspacer
spacer
spacer
  		 
 

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:

    1. 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-SP1/SLES-10-SP1-DVD-ia64-RC5-DVD1.iso

    2. Boot the guest:

      # hpvmconsole -P cl_sue -fi -c "pc -on"

    3. 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.

    4. At the SLES Linux installation menu, select the item “Rescue System”.

    5. At the Boot: text field, enter console=ttyS0 and press Return. This action boots the guest to the Rescue login.

    6. 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

  3. Edit the elilo configuration file, /boot/efi/SuSE/elilo.conf, and the fstab file, /mnt/etc/fstab, to update all entries of the guest boot disk SCSI WWID with the cloned guest boot disk's SCSI WWID.

    NOTE: The cloned guest's boot disk SCSI WWID can be copied from the /dev/disk/by-id/ device names. For example, the cloned guest boot disk device names are as follows:
    Rescue:~ # ls -l /dev/disk/by-id total 0 lrwxrwxrwx 1 root root 9 Dec 5 17:08 scsi-0HP_Virtual_FileDVD_isoLinuxSLES10-SP1SLES-10-SP1- DVD-i -> ../../sr0 lrwxrwxrwx 1 root root 9 Dec 5 17:08 scsi-3600508b4001049440001200002f20000 -> ../../sda lrwxrwxrwx 1 root root 10 Dec 5 17:08 scsi-3600508b4001049440001200002f20000-part1 -> ../../sda1 lrwxrwxrwx 1 root root 10 Dec 5 17:08 scsi-3600508b4001049440001200002f20000-part2 -> ../../sda2 lrwxrwxrwx 1 root root 10 Dec 5 17:08 scsi-3600508b4001049440001200002f20000-part3 -> ../../sda3

  4. In /boot/efi/SuSE/elilo.conf, there are two root device entries with the original quest's boot disk SCSI WWID:

    root = /dev/disk/by-id/scsi-3600508b4001049440000d000026c0000-part3 root = /dev/disk/by-id/scsi-3600508b4001049440000d000026c0000-part3

    Replace these entries with the cloned boot disk's SCSI WWID:

    root = /dev/disk/by-id/scsi-3600508b4001049440001200002f20000-part3 root = /dev/disk/by-id/scsi-3600508b4001049440001200002f20000-part3

  5. In /mnt/etc/fstab, there are three entries (for /, /boot/efi, and swap devices) with the original guest's boot disk SCSI WWID:

    /dev/disk/by-id/scsi-3600508b4001049440000d000026c0000-part3 / reiserfs acl,user_xattr 1 1 /dev/disk/by-id/scsi-3600508b4001049440000d000026c0000-part1 /boot/efi vfat defaults 0 0 /dev/disk/by-id/scsi-3600508b4001049440000d000026c0000-part2 swap defaults 0 0

    Replace these entries with the cloned boot disk's SCSI WWID:

    /dev/disk/by-id/scsi-3600508b4001049440001200002f20000-part3 / reiserfs acl,user_xattr 1 1 /dev/disk/by-id/scsi-3600508b4001049440001200002f20000-part1 /boot/efi vfat defaults 0 0 /dev/disk/by-id/scsi-3600508b4001049440001200002f20000-part2 swap swap defaults 0 0

  6. Reboot the guest:

    Rescue:/# reboot


Support of Red Hat 4 Update 6 Guests on Integrity VM V4.0
  		 


TC INIT Dump Messages Fail to Appear in SUSE Linux Guest Consoles Running Multi CPUs  
Printable version
Privacy statement Using this site means you accept its terms Feedback to webmaster
© 2008 Hewlett-Packard Development Company, L.P.