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: Fri, 20 Nov 2009 15:35:37 +0200
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Fri, 20 Nov 2009 05:36:03 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <4B06728F.1050008@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> <20091119180951.GF16033@xxxxxxxxxxx> <4B06728F.1050008@xxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mutt/1.5.13 (2006-08-11)
On Fri, Nov 20, 2009 at 11:42:23AM +0100, Guillaume Rousse wrote:
> Pasi Kärkkäinen a écrit :
> >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 just did this morning. Without any changelog, it's a bit 'upgrade and 
> pray'...

Changelog is here: http://xenbits.xen.org/xen-3.4-testing.hg

> >>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..
> Indeed.
> Here is the output. At first domU crash, because of memory ballooning 
> issue, is not fatal. The second crash, however is. I don't know if it's 
> because of uncorrect state after initial crash, or because of additional 
> domUs launched in the interim.


> My domUs all have this configuration:
> memory = 256
> maxmem = 512
> Or different values, but always with the same ratio between memory and 
> max memory. Which seems to be quite useless for hvm domUs, as memory 
> ballooning is not supported AFAIK, unless using pv-drivers (which I 
> can't manage to build).
> With identical values, the issue does'nt appear.

Hmm.. so it's definitely related to ballooning.

> With Xen 3.4.2, the domUs still crash, but at least dom0 does not 
> reboot. So it's just less worst :)

So 3.4.2 fixes the hypervisor crash. That's good.

-- Pasi

Xen-devel mailing list