On Thu, Nov 19, 2009 at 07:06:56PM +0100, Guillaume Rousse wrote:
> 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 (188.8.131.52),
> 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..
Xen-devel mailing list