pae kernel installed by kvm will not boot

[Ralph Green]

Binary package hint: qemu-kvm

I am running an AMD-64 system with 32 bit kernel and all updates as of today for Release 10.04. I have 2 GB of ram and I installed kvm and a couple of related tools today. My hard drive is laid out like this.
  sda1 - /boot ext2
  sda2 - encrypted swap
  sda3 - /usr xfs
  sda5 - / xfs
  sda6 - /public xfs

 Installing kvm caused a new kernel to be installed and grub.cfg was modified to make the new kernel the default. The menu entry for the new kernel describes it as: Ubuntu, with Linux 2.6.32-22-generic-pae. These 3 lines in grub.cfg(last part is munged because I don't know if this is sensitive) were also edited:
- - It used to say- - - - -
insmod ext2
set root='(hd0,1)'
search --no-floppy --fs-uuid --set eab686fd-b09a-4386-bb51-xxxxxxxxx
- - It now says- - - - -
insmod xfs
set root='(hd0,3)'
search --no-floppy --fs-uuid --set 83428bb0-2072-4330-b0a5-xxxxxxxxx

 When the computer boots this kernel, it stop and says "uuid=c239b85b-fbd4-4d6e-9524-xxxxxxx does not exist. Dropping to shell!" and I get an initramfs prompt. That is the uuid of /dev/sda5, which is the root partition. I edited grub.cfg to fix the 3 lines, and put /dev/sda5 on the kernel line and now I get "/dev/sda5 does not exist. Dropping to shell!"

 I then edited the default to make it boot my old kernel and the system comes up fine.

 I found the bug when installing kvm, but I don't know if that is the right package to report this under. It may be the kernel, and so I specified the kernel above.

[Scott Moser (smoser)]

This would almost certainly be a issue with linux, not with kvm.

[Jeremy Foshee (jeremyfoshee)]

Hi Ralph,

Please be sure to confirm this issue exists with the latest development release of Ubuntu. ISO CD images are available from http://cdimage.ubuntu.com/daily-live/current/ . If the issue remains, please run the following command from a Terminal (Applications->Accessories->Terminal). It will automatically gather and attach updated debug information to this report.

apport-collect -p linux 589108

Also, if you could test the latest upstream kernel available that would be great. It will allow additional upstream developers to examine the issue. Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Once you've tested the upstream kernel, please remove the 'needs-upstream-testing' tag. This can be done by clicking on the yellow pencil icon next to the tag located at the bottom of the bug description and deleting the 'needs-upstream-testing' text. Please let us know your results.

Thanks in advance.

    [This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]

[Ralph Green (severian)]

Howdy,
  I am confused about the apport-collect part. I understand how to use that program once the system is booted. In this case, I don't get the kernel loaded, because it cannot find my root filesystem. Do I run it after I reboot back with the non pae kernel and will it still have any useful information to collect?

 I can take a spare hard drive and install the daily build of Maverick to test as you ask. I don't see any alternate installer images. The regular image does not let me setup an encrypted swap, so I would not really use the system much. This leads to a follow-up question. Do you know if alternate installer images will be arriving soon? If so, I should probably wait a bit. If they won't be here soon, I can do the test and then wipe the disk. The bug was fairly easy to reproduce on Lucid. I can see why you would also want to know if it exists in the current Maverick. I'll wait until I see a response here and then I can decide what to download and test.
Good day

[Jeremy Foshee (jeremyfoshee)]

This bug report was marked as Incomplete and has not had any updated comments for quite some time. As a result this bug is being closed. Please reopen if this is still an issue in the current Ubuntu release http://www.ubuntu.com/getubuntu/download . Also, please be sure to provide any requested information that may have been missing. To reopen the bug, click on the current status under the Status column and change the status back to "New". Thanks.

[This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]