Guest's built with Intrepid will not boot after upgrade to Jaunty

[Russell Nash]

Binary package hint: kvm

I have two KVM guests which I installed while running Intrepid:

- Ubuntu Intrepid Server x86
- Windows XP Home Edition

These two guests ran fine, however, since I performed a dist-upgrade to Jaunty neither of them will boot. Intrepid server boot fails right after the KVM bios with a 'BUG: Int14: CR2 ffb00000' error. A screen shot of the complete message is here:

http://www.hhoknowhow.info/~russ/images/kvm_boot_fail.jpg

The Windows XP guest hangs on a blank screen right after the KVM BIOS.

In both cases, it is as if the guest cannot access the hard drive?

Guests installed from scratch under Jaunty function fine. This is an up-to-date x86 Jaunty installation on an Intel i7 920.

Russ.

[Russell Nash (russnash37)]

Did I report this in the wrong place or do I need to provide further information?

[Dustin Kirkland  (kirkland)]

Hi Russell-

Are you running kvm from the command line? If so, what is the kvm
command line you're using to launch these two vm's?

If you're not, what are you using as a front end? virt-manager,
virsh, or something else? In those cases, once you have launched the
machine, can you post the output of:
 $ ps -ef | grep kvm

Thanks,
:-Dustin

[Russell Nash (russnash37)]

Hello Dustin,

I tend to use virt-manager to create my guests and then either start them through there or using virsh. Anyhow, here is the process output for the two intrepid created guests I'm having the issues with:

russ@defiant:~$ ps -ef | grep kvm
root 27112 1 21 18:18 ? 00:00:03 /usr/bin/kvm -S -M pc -m 256 -smp 1 -name ds9 -uuid 6743d0cc-5b1f-00a1-77a5-115b8a841de5 -monitor pty -pidfile /var/run/libvirt/qemu//ds9.pid -boot c -drive file=/dev/volume-a/ubuntu_8.10_server,if=virtio,index=0,boot=on -net nic,macaddr=00:16:36:5e:24:20,vlan=0 -net tap,fd=17,script=,vlan=0,ifname=vnet0 -serial pty -parallel none -usb -vnc 127.0.0.1:0
root 27123 1 69 18:18 ? 00:00:08 /usr/bin/kvm -S -M pc -m 512 -smp 1 -name WindowsXP -uuid b4757f32-448d-f68e-0f62-d272ab11ee76 -monitor pty -pidfile /var/run/libvirt/qemu//WindowsXP.pid -localtime -no-acpi -boot c -drive file=/dev/volume-a/windows_xp_kvm,if=ide,index=0,boot=on -net nic,macaddr=54:52:00:52:27:64,vlan=0 -net tap,fd=19,script=,vlan=0,ifname=vnet1 -serial pty -parallel none -usb -usbdevice tablet -vnc 127.0.0.1:1 -k en-us -soundhw es1370
russ 27126 26202 0 18:18 pts/0 00:00:00 grep kvm
russ@defiant:~$

Thanks in advance,

Russ.

[Dustin Kirkland  (kirkland)]

Hi Russ, thanks for the information.

Can you tell me if your disk devices exist?

 $ ls -alF /dev/volume-a/ubuntu_8.10_server /dev/volume-a/windows_xp_kvm

:-Dustin

[Russell Nash (russnash37)]

Hi Dustin,

Yes, the disks are definitely there... it seems to be some issue with accessing them with the new release:

russ@defiant:~$ sudo ls -alF /dev/volume-a/ubuntu_8.10_server /dev/volume-a/windows_xp_kvm
[sudo] password for russ:
lrwxrwxrwx 1 root root 40 2009-06-22 23:13 /dev/volume-a/ubuntu_8.10_server -> /dev/mapper/volume--a-ubuntu_8.10_server
lrwxrwxrwx 1 root root 36 2009-06-22 23:13 /dev/volume-a/windows_xp_kvm -> /dev/mapper/volume--a-windows_xp_kvm
russ@defiant:~$

The two drives are lvm partitions.

Russ.

[Dustin Kirkland  (kirkland)]

Russ,

Notice that your listing showed two symbolic links. Are the
destination files present as well?

ls -alF /dev/mapper/volume--a-ubuntu_8.10_server
/dev/mapper/volume--a-windows_xp_kvm

:-Dustin

[Russell Nash (russnash37)]

Dustin,

Yep, they are there:

root@defiant:/dev/volume-a# ls -al /dev/mapper
total 0
drwxr-xr-x 2 root root 300 2009-06-22 23:13 .
drwxr-xr-x 19 root root 5060 2009-06-23 06:48 ..
crw-rw---- 1 root root 10, 61 2009-06-22 23:13 control
brw-rw---- 1 root disk 252, 0 2009-06-22 23:13 isw_ecbbbfdiie_RAID1-A
brw-rw---- 1 root disk 252, 1 2009-06-22 23:13 isw_ecbbbfdiie_RAID1-A1
brw-rw---- 1 root disk 252, 2 2009-06-22 23:13 isw_ecbbbfdiie_RAID1-A2
brw-rw---- 1 root disk 252, 4 2009-06-22 23:13 volume--a-home
brw-rw---- 1 root disk 252, 11 2009-06-22 23:13 volume--a-jaunty
brw-rw---- 1 root disk 252, 7 2009-06-22 23:13 volume--a-opt
brw-rw---- 1 root disk 252, 3 2009-06-22 23:13 volume--a-root
brw-rw---- 1 root disk 252, 8 2009-06-22 23:13 volume--a-swap
brw-rw---- 1 root disk 252, 6 2009-06-22 23:13 volume--a-tmp
brw-rw---- 1 root disk 252, 10 2009-06-22 23:13 volume--a-ubuntu_8.10_server
brw-rw---- 1 root disk 252, 5 2009-06-22 23:13 volume--a-usr
brw-rw---- 1 root disk 252, 9 2009-06-22 23:13 volume--a-windows_xp_kvm
root@defiant:/dev/volume-a#

Russ.

[Dustin Kirkland  (kirkland)]

Hi Russ-

Is there any chance you can try Karmic and qemu-kvm-0.11, and tell me if you can reproduce there?

:-Dustin

[Dustin Kirkland  (kirkland)]

Haven't heard back in 7 months, expiring. Please reopen if you can reproduce this bug on the latest Lucid qemu-kvm.