Re: [Xen-devel] Arbitrary reboot with xen 3.4.x

[Pasi Kärkkäinen <pasik@xxxxxx>]

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 (2.6.27.37), 
> >>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.
> 

<snip>

> 
> 
> 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
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel