Pasi Kärkkäinen a écrit :
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
The exhaustive list of all files modifications is totally useless for an
admin to decide if the risk of updating a working system is worth the
attempt. What is missing in all Xen releases is a comprehensive,
user-targeted list of bug fixed and behavior changes.
[..]
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.
Yes, that's lesser evil :)
What is really strange, tough, is the difference behaviour exhibited by
this new feature. On other systems, I just can't launch any HVM with
different values for 'memory' and 'maxmem'.
--
BOFH excuse #179:
multicasts on broken packets
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
|
Home