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] Arbitrary reboot with xen 3.4.x

To: Guillaume Rousse <Guillaume.Rousse@xxxxxxxx>
Subject: Re: [Xen-devel] Arbitrary reboot with xen 3.4.x
From: Pasi Kärkkäinen <pasik@xxxxxx>
Date: Thu, 19 Nov 2009 20:09:51 +0200
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Thu, 19 Nov 2009 10:10:13 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <4B058940.2050009@xxxxxxxx>
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/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <4B058940.2050009@xxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mutt/1.5.13 (2006-08-11)
On Thu, Nov 19, 2009 at 07:06:56PM +0100, Guillaume Rousse wrote:
> Hello.
> I've a dom0 working perfectly under xen 3.3.x, with a bout 15 HVM domU. 
> When migrating to xen 3.4.1, with the same dom0 kernel (, 
> everything seems to be fine, I can launch the various hosts, but 5 to 10 
> minutes later, the host violently reboot... I can't find any trace in 
> the logs. I do have a second host with the same configuration and setup, 
> and the result is similar. It seems to be linked with domU activity, 
> because without any domU, or without any domU with actual activity, I 
> don't have any reboot. I had to rollback to xen 3.3.0.

Did you try the new Xen 3.4.2 ?

> I already attempted such upgrade to xen 3.4.0 this summer, with exactly 
> the same result.


> It seems like an hardware issue (but it doesn't appears with 3.3.0), or 
> a crash in the hypervisor, than syslog is unable to catch when it 
> appears. How can I try to get a trace ?

You should setup a serial console, so you can capture and
log the full console (xen + dom0 kernel) output to other computer..

-- Pasi

Xen-devel mailing list