/ 3.6. Using an Existing SUSE Linux Enterprise Server Virtual Machine | ||||
|---|---|---|---|---|
 | 3.5. Deleting Virtual Machines | 3.7. Troubleshooting |  | |
/ 3.6. Using an Existing SUSE Linux Enterprise Server Virtual Machine | ||||
|---|---|---|---|---|
| 3.5. Deleting Virtual Machines | 3.7. Troubleshooting | | |
In SUSE Linux Enterprise Server 10, the device naming is different than the device naming of SUSE Linux Enterprise Server 9. Therefore, a SUSE Linux Enterprise Server 9 VM Guest will not be able to find its root file system when running on a SUSE Linux Enterprise Server 10 VM Host Server.
To be able to still boot the system, you must know which device
is used for the root partition of your virtual system. For
example, hdaxx will be changed to
xvdaxx where
xx is the partition number.
When booting the system, you have to append an extra root option
to the kernel command line, that tells the system about its root
file system. If your VM Guest used to live on
/dev/hda2, append the string
root=/dev/xvda2 to the kernel command line.
This option should enable you to boot the system, although
additional filesystems still will not be available to the system.
To make all the needed file systems available to the VM Guest, do the following:
In order to have a valid initial ramdisk that knows about the new location of the root filesystem, run the command mkinitrd.
Start the VM Guest with the extra root=
command line as explained above.
Log into the system as user root.
Edit the file /etc/fstab and correct all
device entries.
Edit the virtual machine’s /boot/grub/menu.lst
file. At the kernel line, fix the root=
and the resume= parameters according the new
naming schema.
Reboot the virtual machine.
