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] Problems booting Domain 0 ES7000 x86_64

To: "Ian Pratt" <m+Ian.Pratt@xxxxxxxxxxxx>, <xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject: RE: [Xen-devel] Problems booting Domain 0 ES7000 x86_64
From: "Subrahmanian, Raj" <raj.subrahmanian@xxxxxxxxxx>
Date: Mon, 25 Jul 2005 16:52:14 -0400
Cc: "Magolan, John F" <John.Magolan@xxxxxxxxxx>, "Davis, Jason" <jason.davis@xxxxxxxxxx>, "Vessey, Bruce A" <Bruce.Vessey@xxxxxxxxxx>
Delivery-date: Mon, 25 Jul 2005 20:51:23 +0000
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
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>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: AcWRSZApBFRebCSETWmdUWOZlIIlzgAAd0/AAAE9cqA=
Thread-topic: [Xen-devel] Problems booting Domain 0 ES7000 x86_64
EARLY_PRINTK has already been enabled in domain0 .config.
I am also wondering why it doesn't show Domain 0 as having crashed.
The earlier times we have had issues with Domain 0 crashing, we have always 
seen a message from Xen saying 'crashed on cpu #0'.

-----Original Message-----
From: Ian Pratt [mailto:m+Ian.Pratt@xxxxxxxxxxxx]
Sent: Monday, July 25, 2005 3:04 PM
To: Subrahmanian, Raj; xen-devel@xxxxxxxxxxxxxxxxxxx
Cc: Magolan, John F; Davis, Jason; Vessey, Bruce A;
Subject: RE: [Xen-devel] Problems booting Domain 0 ES7000 x86_64

> I am trying to boot 32-bit Xen on an ES7000 x86_64 box. I am 
> running 32 bit Sles9 on the box. 
> Xen boots fine, but Domain 0 shuts down very early in the 
> boot process.
> I don't even see a 'Domain 0 crashed on vcpu #0' type message.
> All I see is.
> (XEN) Scrubbing Free RAM: ......................................done.
> (XEN) *** Serial input -> DOM0 (type 'CTRL-a' three times to 
> switch input to Xen).
> (XEN) Domain 0 shutdown: rebooting machine.

Enable EARLY_PRINTK in the domain0 config, or alternatively, rename
xprintk to printk.


Xen-devel mailing list