Re: [opensuse-virtual] DomU cannot find /dev/hda2 after upgrading to SLES 10 SP1

Tyler, My comments are inline. Jason

...

...

On Tue, Jul 1, 2008 at 10:51 AM, in message <486A6090.4000404@planplus.com>, Tyler D wrote: Hello, I'm midway in the process of upgrading a server from SLES 10 GA to SP2.

I updated the Dom0 (host) to SP1, then recreated a test VM (DomU) that has the GA version on it (I made a new VM with the same specs, and pointed it to the old hda file). I then updated the VM to SP1 as well. When the installer first listed partitions, none were showing, until I ticked 'Show all partitions'. I installed to /dev/xda2.

When I try to boot the VM, it says:

Waiting for device /dev/hda2 to appear ... not found -- exiting to /bin/sh.

It sounds like your root= needs to be set to /dev/xvda2 (instead of /dev/hda2).

I can run a few basic commands at this point, and I checked for /etc/fstab, and for any hda files in /dev - none are there.

In the original config file for this VM is the following line:

bootentry = 'hda2:/boot/vmlinuz-xenpae,/boot/initrd-xenpae'

In addition to changing hda2 to xvda2 (based on your statement above), domUloader expects different arguments with SP1 than it did with GA. In SP1, the bootentry line should be replaced with a line that looks like this: bootargs="--entry=xvda2:/boot/vmlinuz-xenpae,/boot/initrd-xenpae" However, if you created a new vm config file using the SP1 vm-install tool, that line should already be correct.

My guess is that the VM's boot entry is still configured to search for /hda2, although there is no option for changing this in the new SP1 Virtual Machine Manager. Editing the config files for a VM under SP1 seems to have no effect as the settings appear to be stored elsewhere after the initial creation.

If you edit the config file manually, then you need to import it into "xenstore" by doing the following: 1. xm delete vm_name (this removes the config from xenstore) 2. xm new vm_config_file (this adds the config to xenstore) At that point, you can launch the VM from virt-manager. The alternative is to ignore virt-manager for starting the VM (for testing purposes). To launch the VM using the settings in the config file, you can run "xm create vm_config_file". Once it is launched, you can still start a viewer from virt-manager (or if the viewer window was already open for that VM, it should automatically connect).

If you would be so kind as to a) suggest how I can edit the VM's boot entry (no, GRUB is not installed on the VM) from Dom0 or the very limited /bin/sh mode), and/or b) offer other suggestions or solutions, it would be much appreciated.

Hopefully the suggestions above will help.

Thank you in advance. I've read the documentation and know that there may be further headaches in upgrading the VMs to SP2 (you're supposed to update the DomUs before the Dom). I'm waiting at SP1 until I can get the VMs properly upgraded.

At this point you might be better off moving dom0/hypervisor to SP2 and deal with all the problems at the same time. The xen 3.2.0 hypervisor is capable of running older guests, so that *shouldn't* be an issue, but I have definitely never tried the scenario you are attempting. Good luck! Jason -- To unsubscribe, e-mail: opensuse-virtual+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-virtual+help@opensuse.org