This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
Home Products Support Community News


Re: [Xen-devel] DomU crashing on x86

To: David F Barrera <dfbp@xxxxxxxxxx>
Subject: Re: [Xen-devel] DomU crashing on x86
From: Nivedita Singhvi <niv@xxxxxxxxxx>
Date: Wed, 13 Jul 2005 14:55:40 -0700
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Wed, 13 Jul 2005 21:54:38 +0000
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <1121291042.5164.12.camel@xxxxxxxxxxxxxxxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <1121291042.5164.12.camel@xxxxxxxxxxxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mozilla Thunderbird 0.8 (X11/20041020)
David F Barrera wrote:
We are seeing a problem in xen-unstable where DomU crashes immediately
after booting on some x86 boxes. In my case, it is happening on a couple
of machines that have SCSI drives and where DomU is a SLES 9
installation. Here's some data on my setup:

                Dom0            DomU            Dom U Crash?    SCSI

Machine A       SLES 9          SLES 9          Yes             Yes
Machine B       SLES 9          RHEL 4          No              Yes
Machine C       RHEL 4          SLES 9          Yes             Yes
Machine D       FC3       SLES 9 and Debian     No              No
The only thing I see in common in the machines that fail is the SCSI
drives.  Machines B and C are identical; the others are different

Dave, what are your boot options?


This is the Oops info that I am seeing (no other info is displayed):

Oops:   0002 [#1]
PREEMPT SMP modules linked in:
CPU:    0
EIP:    0061:[<00244ec0>]       Not tainted VLI

David Wolinsky (david_wolinsky@xxxxxxxx) has also reported seeing the

------- Additional Comments From david_wolinsky@xxxxxxxx  2005-07-13
21:26 -------
I put together a testing suite to figure out the problem… and it seems
related to two parts of my machine.

A)  Fedora Core 3
B)  SATA drive (as you are probably aware these use the same scsi

To test A out, I installed Debian (known for its stability, etc)… And
ran with SATA in SATA mode and in IDE emulation mode (cominbation mode as listed in the bios)… both tests passed (not concrete, I only ran it as long as I had known the test of Fedora Core to last… I'll run it over night for 100%).
To test B out, I set my SATA mode into IDE emulation mode and ran it in
FC3, this time it crashed the DomU and not Dom0.

My conclusion is... an issue between the SCSI driver, Xen hypervisor,
and the memory driver
-------------------end of David Wolinsky's comments ---------------

Has anyone else observed this problem?  I believe this is a serious
problem that requires some attention.

Xen-devel mailing list

<Prev in Thread] Current Thread [Next in Thread>