From mboxrd@z Thu Jan 1 00:00:00 1970 From: Tiago Teresa Teodosio Subject: Re: Re: DomU not rebooting in 3.0.1 Date: Wed, 01 Mar 2006 23:14:27 +0000 Message-ID: <44062AD3.8030500@rnl.ist.utl.pt> References: <20060227153317.GL27353@leeni.uk.xensource.com> <20060227190613.GA24879@dargo.dague.pvt> <20060227191353.GC26305@leeni.uk.xensource.com> <20060227193742.GB24879@dargo.dague.pvt> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Return-path: In-Reply-To: <20060227193742.GB24879@dargo.dague.pvt> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Brian Hays Cc: Sean Dague , Ewan Mellor , xen-devel@lists.xensource.com List-Id: xen-devel@lists.xenproject.org -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Sean Dague wrote: > On Mon, Feb 27, 2006 at 07:13:53PM +0000, Ewan Mellor wrote: >=20 >>On Mon, Feb 27, 2006 at 02:06:14PM -0500, Sean Dague wrote: >> >> >>>On Mon, Feb 27, 2006 at 03:33:17PM +0000, Ewan Mellor wrote: >>> >>>>On Sat, Feb 25, 2006 at 11:31:57AM -0500, Brian Hays wrote: >>>> >>>> >>>>>In 3.0.1 it appears that reboots from within a domU result in the do= mU >>>>>shutting down but not coming back up. >>>>> >>>>>/var/log/xen-hotplug.log reports something similar to "xenstore-list= : >>>>>could not read path backend/vbd/40" >>>>> >>>>>Attempts to manually start the domU up again via "xm create" fail un= til >>>>>first running "xenstore-rm backend/vbd/40" >>>>> >>>>>This has happened on several occasions within different domU's on >>>>>different machines. Is there a known workaround... Is this already f= ixed >>>>>in unstable? >>>> >>>>This is being tracked as bug #514. I think I have a fix, which shoul= d be in >>>>today, all being well. >>> >>>Ewan, I didn't notice 514, but I submitted a related bug >>>http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=3D549. It appe= ars that >>>the big deciding factor on whether or not I see the race is is the Dom= U that >>>is rebooting running on a fully independant CPU from Dom0. If it is, = it >>>breaks every time, if it isn't (i.e. it is on the *same* phys CPU as D= om0) >>>it works every time. Hi I had the same problem in 3.0.0 and the workaround I found was to assign more than one vcpu to the DomU. (The Dom0 has only runs only on one cpu) I left xen to assign the cpus to each VM so I can not tell if the fact of running on the same cpu of the Dom0 has any effect. If it is of any help, the physical machine is a Dual Xeon 3.0 GHz, so the hypervisor sees 4 cpus. Bye >> >>Please could you use xen-bugtool to attach your logs to that bug #549 -= - I'm >>not sure it's the same root cause. >=20 >=20 > No problem, xen-bugtool now run with files attached. >=20 > -Sean >=20 >=20 >=20 > -----------------------------------------------------------------------= - >=20 > _______________________________________________ > Xen-devel mailing list > Xen-devel@lists.xensource.com > http://lists.xensource.com/xen-devel - -- Tiago Teresa Teod=F3dio tiago@rnl.ist.utl.pt Administra=E7=E3o da Rede das Novas Licenciaturas Instituto Superior T=E9cnico web: http://www.rnl.ist.utl.pt email: rnl@rnl.ist.utl.pt tel: +351 218 41 77 71 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFEBirTQO/Tafxh35cRAhi3AKDNe9RHp7VLON7EP5j0TFR5FDz64ACg0C35 3fF0FG864dUmcm2hnNAUcgU=3D =3DC+kk -----END PGP SIGNATURE-----