From mboxrd@z Thu Jan 1 00:00:00 1970 From: Guillaume Rousse Subject: Re: Arbitrary reboot with xen 3.4.x Date: Sat, 21 Nov 2009 14:49:36 +0100 Message-ID: <4B07EFF0.3060503@inria.fr> References: <4B058940.2050009@inria.fr> <20091119180951.GF16033@reaktio.net> <4B06728F.1050008@inria.fr> <20091120133537.GJ16033@reaktio.net> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: quoted-printable Return-path: In-Reply-To: <20091120133537.GJ16033@reaktio.net> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: =?ISO-8859-1?Q?Pasi_K=E4rkk=E4inen?= Cc: xen-devel@lists.xensource.com List-Id: xen-devel@lists.xenproject.org Pasi K=E4rkk=E4inen a =E9crit : > On Fri, Nov 20, 2009 at 11:42:23AM +0100, Guillaume Rousse wrote: >> Pasi K=E4rkk=E4inen a =E9crit : >>> 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 do= mU.=20 >>>> When migrating to xen 3.4.1, with the same dom0 kernel (2.6.27.37),=20 >>>> everything seems to be fine, I can launch the various hosts, but 5 t= o 10=20 >>>> minutes later, the host violently reboot... I can't find any trace i= n=20 >>>> the logs. I do have a second host with the same configuration and se= tup,=20 >>>> and the result is similar. It seems to be linked with domU activity,= =20 >>>> because without any domU, or without any domU with actual activity, = I=20 >>>> 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 an= d=20 >> pray'... >> >=20 > Changelog is here: http://xenbits.xen.org/xen-3.4-testing.hg The exhaustive list of all files modifications is totally useless for an=20 admin to decide if the risk of updating a working system is worth the=20 attempt. What is missing in all Xen releases is a comprehensive,=20 user-targeted list of bug fixed and behavior changes. [..] >> With Xen 3.4.2, the domUs still crash, but at least dom0 does not=20 >> reboot. So it's just less worst :) >> >=20 > 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=20 this new feature. On other systems, I just can't launch any HVM with=20 different values for 'memory' and 'maxmem'. --=20 BOFH excuse #179: multicasts on broken packets