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


[Xen-users] Reboot instead of dom0 starupt

To: xen-users@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-users] Reboot instead of dom0 starupt
From: Michael Gruetzner <Michael_Gruetzner@xxxxxx>
Date: Thu, 10 May 2007 15:15:31 +0200
Delivery-date: Thu, 10 May 2007 06:14:02 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-users-request@lists.xensource.com?subject=help>
List-id: Xen user discussion <xen-users.lists.xensource.com>
List-post: <mailto:xen-users@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx

I just updated to xen 3.0.4 and linux- (gentoo linux). After reboot xen starts up just fine but instead of starting the dom0 kernel the machine just
reboots. The last messages I see on my screen are:

(XEN) Scrubbing Free RAM: .......done.
(XEN) Xen trace buffers: disabled
(XEN) Std. Loglevel: Errors and warnings
(XEN) Guest Loglevel: Nothing (Rate-limited: Errors and warnings)

... reboot

My dom0 kernel is compiled with all the backend drivers and no compatibility code.

How can I figure out the reason for the sudden reboot? Is there a way to enable a mor verbose output without recompiling xen? I didn't find any command line parameter ...

Thanks for any help in advance,


Xen-users mailing list

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