Kernel 2.6.32-11 fails to boot using VirtualBox

Bug #511557 reported by oCean
14
This bug affects 2 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Invalid
Medium
Unassigned
Lucid
Invalid
Medium
Unassigned

Bug Description

Using Virtualbox OSE [version: 3.0.8_ose r53138]
Fresh install of Lucid, Alpha 2.
Running kernel: 2.6.32-10.14 generic
Ran all updates (ca. 170+) including kernel update to 2.6.32-11.15
Rebooted, screen "GRUB loading" appears, then - nothing, only black screen, (virtual) machine is frozen
Holding shift key, does show grub menu (otherwise not starting) and 2.6.32-10 still boots fine
Choosing 2.6.32-11 recovery mode, shows:

  ] CPU supports 0 MCE banks
  ] using mwait in idle threads
  ] Performance Events: unsupported p6 CPU model 15 no PMU driver, software events only.
  ] Checking 'hlt' instruction... OK

Booting in 2-6.32-10 kernel, succeeds, but dmesg shows

  ] weird, boot CPU (#0) not listed by the bios.
  ] Brought up 1 CPUs
  ] CPU0 attaching NULL sched-domain

and further booting process.

What is holding back the 32-11 version to boot?

Revision history for this message
oCean (alex.harkema) wrote :

Typo in initial post. Actually strike the "after update to" in first line...

oCean (alex.harkema)
description: updated
Revision history for this message
Persio (persiobarros) wrote :

Same problem here, too. The solution for me was to enable the VT-x/AMD-V support for the virtual machine.

Revision history for this message
Rocko (rockorequin) wrote :

I have a similar problem with both VBox 3.1.2 and 3.1.4 beta when booting a VM with the 2.6.32 kernel. With VT-x off, when I try to boot a 32 bit Karmic guest running a 2.6.32.7 kernel (PAE enabled), it freezes partway into the boot process. The last message is " * could not access PID file for nmbd". It boots fine with VT-x on.

Revision history for this message
oCean (alex.harkema) wrote :

Updated (guest) to 2.6.32-12.16 kernel, problem is still there.
some more info:
- host OS is Ubuntu Karmic 9.10, x86_64
- host HW is x86_64
- guest OS is i386

Stefan Bader (smb)
Changed in linux (Ubuntu):
importance: Undecided → Medium
status: New → Triaged
Revision history for this message
oCean (alex.harkema) wrote :

Same error occurs in 2.6.32-13.18

Revision history for this message
oCean (alex.harkema) wrote :

error still occurs in 2.6.32-15.22, not able to boot.

Revision history for this message
Elbarbudo (patricearnal) wrote :

On VirtualBox 3.1.2 r56127, the "ubuntu-10.04-rc-desktop-i386.iso" freezes during boot.

First purple screen, then black screen. No disk/cdrom activity.
No way to get any information.

Host : Ubuntu 9.10 desktop 32bits.

Revision history for this message
Kees-Jan Dijkzeul (kees-jan.dijkzeul) wrote :

Error still occurs in 2.6.32-22.33, not able to boot.

Toggling VT-x seems to have no effect.

Revision history for this message
Kees-Jan Dijkzeul (kees-jan.dijkzeul) wrote :

Error doesn't occur anymore on VirtualBox 3.2.6. Maybe this was a VirtualBox problem?

Revision history for this message
Christopher M. Peñalver (penalvch) wrote :

oCean, this bug was reported a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue? If so, could you please test for this with the latest development release of Ubuntu? ISO images are available from http://cdimage.ubuntu.com/daily-live/current/ .

If it remains an issue, could you please run the following command in the development release from a Terminal (Applications->Accessories->Terminal), as it will automatically gather and attach updated debug information to this report:

apport-collect -p linux <replace-with-bug-number>

Also, could you please test the latest upstream kernel available following https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow additional upstream developers to examine the issue. Please do not test the daily folder, but the one all the way at the bottom. Once you've tested the upstream kernel, please comment on which kernel version specifically you tested. If this bug is fixed in the mainline kernel, please add the following tags:
kernel-fixed-upstream
kernel-fixed-upstream-VERSION-NUMBER

where VERSION-NUMBER is the version number of the kernel you tested. For example:
kernel-fixed-upstream-v3.11

This can be done by clicking on the yellow circle with a black pencil icon next to the word Tags located at the bottom of the bug description. As well, please remove the tag:
needs-upstream-testing

If the mainline kernel does not fix this bug, please add the following tags:
kernel-bug-exists-upstream
kernel-bug-exists-upstream-VERSION-NUMBER

As well, please remove the tag:
needs-upstream-testing

Once testing of the upstream kernel is complete, please mark this bug's Status as Confirmed. Please let us know your results. Thank you for your understanding.

Changed in linux (Ubuntu):
status: Triaged → Incomplete
Revision history for this message
oCean (alex.harkema) wrote :

"a while ago" indeed.

Currently running: 12.10 on 3.5.0-40-generic with vbox 4.2 (Installed: 4.2.18-88780~Ubuntu~quantal) where this problem definitely does not exist.

Revision history for this message
Christopher M. Peñalver (penalvch) wrote :

oCean, this bug report is being closed due to your last comment https://bugs.launchpad.net/ubuntu/+source/linux/+bug/511557/comments/11 regarding this being fixed with an update. For future reference you can manage the status of your own bugs by clicking on the current status in the yellow line and then choosing a new status in the revealed drop down box. You can learn more about bug statuses at https://wiki.ubuntu.com/Bugs/Status. Thank you again for taking the time to report this bug and helping to make Ubuntu better. Please submit any future bugs you may find.

Changed in linux (Ubuntu):
status: Incomplete → Invalid
Changed in linux (Ubuntu Lucid):
status: Triaged → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers