Booting Xen dom0 hangs on ACPI when VMX is enabled

Bug #164803 reported by Ross Patterson
4
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Invalid
Undecided
Unassigned
linux-source-2.6.22 (Ubuntu)
Won't Fix
Undecided
Unassigned

Bug Description

Binary package hint: linux-image-2.6.22-14-xen

The linux-image-xen kernel boots fine as long as the virtualization support (VMX) is turned off in the BIOS, but when I turn it on in the BIOS, boot on dom0 hangs. The last console output is:

  Setting up standard PCI resources

I note that on a successful boot with VMX disabled in the BIOS, the line above comes right before the following ACPI stuff:

  ACPI: EC: Look up EC in DSDT
  ACPI: Interpreter enabled
  ACPI: (supports S0 S3 S4 S5)
  ACPI: Using IOAPIC for interrupt routing

Xen dom0 would boot when "acpi=off" was passed to Xen on boot. I tried all the acpi Xen boot options I could find with the following effects:

acpi=off -> Boots, no ACPI
acpi=ht -> Boots, no ACPI
acpi=force -> Hangs
acpi=noirq -> Hangs
acpi -> Hangs
acpi=strict -> Hangs
acpi=1 -> Hangs

There is no combination that boots dom0 with VMX enabled and ACPI working.

My system is a Core 2 Duo T7200 Toshiba Satellite U205-5067 laptop running gutsy x86.

Ross Patterson (rossp)
description: updated
Revision history for this message
Ross Patterson (rossp) wrote :

I also tried the following:

acpi_skip_timer_override -> Hangs
noapic -> Hangs
lapic -> Hangs
nolapic -> Hangs

Revision history for this message
Leann Ogasawara (leannogasawara) wrote :

Hi Ross,

The Hardy Heron Alpha series is currently under development and contains an updated version of the kernel. Care to test the linux-image-2.6.24-11-xen and verify if this is still an issue? Thanks.

Changed in linux-source-2.6.22:
status: New → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote : This bug is now reported against the 'linux' package

Beginning with the Hardy Heron 8.04 development cycle, all open Ubuntu kernel bugs need to be reported against the "linux" kernel package. We are automatically migrating this bug to the new "linux" package. However, development has already began for the upcoming Intrepid Ibex 8.10 release. It would be helpful if you could test the upcoming release and verify if this is still an issue - http://www.ubuntu.com/testing . If the issue still exists, please update this report by changing the Status of the "linux" task from "Incomplete" to "New". We appreciate your patience and understanding as we make this transition. Thanks!

Revision history for this message
Leann Ogasawara (leannogasawara) wrote :

The Ubuntu Kernel Team is planning to move to the 2.6.27 kernel for the upcoming Intrepid Ibex 8.10 release. As a result, the kernel team would appreciate it if you could please test this newer 2.6.27 Ubuntu kernel. There are one of two ways you should be able to test:

1) If you are comfortable installing packages on your own, the linux-image-2.6.27-* package is currently available for you to install and test.

--or--

2) The upcoming Alpha5 for Intrepid Ibex 8.10 will contain this newer 2.6.27 Ubuntu kernel. Alpha5 is set to be released Thursday Sept 4. Please watch http://www.ubuntu.com/testing for Alpha5 to be announced. You should then be able to test via a LiveCD.

Please let us know immediately if this newer 2.6.27 kernel resolves the bug reported here or if the issue remains. More importantly, please open a new bug report for each new bug/regression introduced by the 2.6.27 kernel and tag the bug report with 'linux-2.6.27'. Also, please specifically note if the issue does or does not appear in the 2.6.26 kernel. Thanks again, we really appreicate your help and feedback.

Revision history for this message
Michele Mangili (mangilimic) wrote :

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!

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

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.