[Bug 510571] Re: Lucid guest won't boot with acpi in virtualbox

Mark Foster mark at g.foster.cc
Fri Apr 9 19:32:26 BST 2010


Trying this on lucid beta2
With acpi=off kernel arg it boots up fine and I can install.
Without acpi=off it boots extremely sluggish and debinstaller is unusable.

In both cases, the VirtualBox settings have ACPI enabled.

-- 
Lucid guest won't boot with acpi in virtualbox
https://bugs.launchpad.net/bugs/510571
You received this bug notification because you are a member of Ubuntu
Sponsors Team, which is a direct subscriber.

Status in The Linux Kernel: Invalid
Status in Virtualbox: Fix Released
Status in “linux” package in Ubuntu: Invalid
Status in “virtualbox-ose” package in Ubuntu: Fix Released
Status in “linux” source package in Jaunty: Invalid
Status in “virtualbox-ose” source package in Jaunty: Triaged
Status in “linux” source package in Karmic: Invalid
Status in “virtualbox-ose” source package in Karmic: Triaged

Bug description:
Lucid is unable to boot as a guest operating system in VirtualBox when having acpi enabled.
Applies to Karmic & earlier versions of VirtualBox

------

TEST CASE:
0.1 Boot a pre-Lucid release of ubuntu
0.2 Install VirtualBox
1. Create a new virtual machine in VirtualBox
2. Attach a Lucid liveCD (e.g. beta1) and start the virtual machine
* The machine is unable to boot
! Expected is that the machine should be able to boot

Workaround:
Either disable acpi in the VirtualBox settings, or use acpi=off as a kernel parameter when booting.

Impact:
This affects the testing of Lucid as well as running any distributions with a newer kernel.
The number of affected users can be expected to increase

Scope:
Issue first triggered on kernel 2.6.32-11 in Lucid and is present on all later versions.
This seems to apply to all versions of VirtualBox prior to 3.1.4 beta (OSE and PUEL) when booting Lucid (or any other system with a newer kernel). That is, all versions prior to Lucid's (Karmic & Jaunty confirmed)

Fix:
Changesets r26129 (http://www.virtualbox.org/changeset/26129) and r26130 (http://www.virtualbox.org/changeset/26130) from upstream SVN fixes this bug, and testing of these through patched PPA package (https://launchpad.net/~arand/+archive/virtualbox) seems to be successful





More information about the Ubuntu-sponsors mailing list