Bug 427788 - Kernel panic when booting xen kernel (Xen BUG at vmcs.c:121)
Summary: Kernel panic when booting xen kernel (Xen BUG at vmcs.c:121)
Alias: None
Product: Red Hat Enterprise Linux 5
Classification: Red Hat
Component: xen
Version: 5.1
Hardware: x86_64
OS: Linux
Target Milestone: rc
: ---
Assignee: Xen Maintainance List
QA Contact: Virtualization Bugs
Depends On:
TreeView+ depends on / blocked
Reported: 2008-01-07 16:10 UTC by Gino Rossen
Modified: 2009-12-14 21:25 UTC (History)
0 users

Clone Of:
Last Closed: 2008-01-21 14:28:27 UTC

Attachments (Terms of Use)
Kernel panic log (16.79 KB, text/plain)
2008-01-07 16:10 UTC, Gino Rossen
no flags Details

Description Gino Rossen 2008-01-07 16:10:30 UTC
Description of problem:
On a IBM X3650/7979(71G) server booting the system with the xen kernel
(2.6.18-53.1.4.el5xen) results in a kernel panic.
Using the standard kernel (2.6.18-53.1.4.el5) the system boots fine. 
Since we have 2 identical X3650 servers which are both giving a kernel panic
when booting in the xen kernel i think we can rule out faulty hardware.
"Intel Virtual Technology" option is enabled in BIOS

Version-Release number of selected component (if applicable):
Xen version 3.1.0-53.1.4.el5

How reproducible:
Every time

Steps to Reproduce:
1. Boot Xen kernel
2. Panic
Actual results:
Kernel panic

Expected results:

Additional info:
I've attached the kernel log.

Comment 1 Gino Rossen 2008-01-07 16:10:31 UTC
Created attachment 290970 [details]
Kernel panic log

Comment 2 Chris Lalancette 2008-01-07 16:37:11 UTC
We've seen this one before; it's most likely a BIOS bug.  See
https://bugzilla.redhat.com/show_bug.cgi?id=249300 for details, and check if
there is an updated BIOS from your vendor.

Chris Lalancette

Comment 3 Gino Rossen 2008-01-07 18:08:28 UTC
When trying to open bug #249300 i get:

You are not authorized to access bug #249300. 
Access to some bugs is restricted due to embargoed security issues or respect for customer and partner 
information which must remain confidential.

Latest BIOS upgrade from IBM has been applied (1.07).

Comment 4 Gino Rossen 2008-01-21 09:48:55 UTC
Issue has been resolved. Problem was caused by different CPU steppings. We
changed one of the cpu's so both cpu's are now the same stepping. After that the
xen kernel booted fine.

Comment 5 Bill Burns 2008-01-21 14:28:27 UTC
Closed as not a bug, per commment #4.

Note You need to log in before you can comment on or make changes to this bug.