From mboxrd@z Thu Jan 1 00:00:00 1970 From: Mike Wray Subject: Re: More Xen troubles (with xend this time) Date: Wed, 01 Dec 2004 10:19:23 +0000 Message-ID: <41AD9AAB.60800@hpl.hp.com> References: <41ACA3A9.20305@enix.org> <20041130165753.GE22112@cl.cam.ac.uk> <41ACA972.2090200@enix.org> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: quoted-printable Return-path: In-Reply-To: <41ACA972.2090200@enix.org> Sender: xen-devel-admin@lists.sourceforge.net Errors-To: xen-devel-admin@lists.sourceforge.net List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , List-Archive: To: =?ISO-8859-1?Q?J=E9r=F4me_Petazzoni?= Cc: xen-devel@lists.sourceforge.net List-Id: xen-devel@lists.xenproject.org J=E9r=F4me Petazzoni wrote: >=20 >>> Okay, and once we "lost" xend, there is no way to do anything ?=20 >>> (create, destroy, shutdown, get a console...) >>> =20 >> You could try removing xend's database in /var/xen/xend-db -- you will >> lose your domain's names but I've found that sometimes this allows >> restarting xend when it's in the state where it doesn't want to start >> anymore. >> =20 > Interesting ! I did that, and then : >=20 > # xm list > Name Id Mem(MB) CPU State Time(s) Console > Domain-0 0 59 0 r---- 5915.7 =20 > Domain-16 16 63 0 -b--- 328.7 =20 > Domain-17 17 127 0 -b--- 699.8 =20 > Domain-21 21 0 0 ----c 0.0 =20 > Domain-22 22 0 0 ----c 0.0 =20 > I could successfully create a new domain attached to a console, and sto= p=20 > it ; but other stuff didn't work : >=20 > # xm console 16 > Error: No console information The problem is that if you remove xend-db xend no longer knows anything a= bout the running domains (like what inter-domain ports their consoles are on, what their names are, what devices they have). So xend can no longer shut them down properly because it doesn't know what devices to release. This is why you get all the errors. > And xm shutdown didn't do anything, it seems. Destroying crashed domain= s=20 > didn't work either. It keeps spitting those messages every couple of=20 > seconds in xend.log : >=20 > [2004-11-30 18:06:44 xend] DEBUG (XendDomain:244) XendDomain>reap>=20 > domain died name=3DDomain-21 id=3D21 > [2004-11-30 18:06:44 xend] INFO (XendDomain:564) Destroying domain:=20 > name=3DDomain-21 > [2004-11-30 18:06:44 xend] DEBUG (XendDomain:244) XendDomain>reap>=20 > domain died name=3DDomain-22 id=3D22 > [2004-11-30 18:06:44 xend] INFO (XendDomain:564) Destroying domain:=20 > name=3DDomain-22 > [2004-11-30 18:06:44 xend] INFO (XendRoot:91) EVENT> xend.domain.exit=20 > ['Domain-21', '21', 'crash'] > [2004-11-30 18:06:44 xend] INFO (XendRoot:91) EVENT> xend.domain.destro= y=20 > ['Domain-21', '21'] > [2004-11-30 18:06:44 xend] INFO (XendRoot:91) EVENT> xend.domain.exit=20 > ['Domain-22', '22', 'crash'] > [2004-11-30 18:06:44 xend] INFO (XendRoot:91) EVENT> xend.domain.destro= y=20 > ['Domain-22', '22'] Xend is trying to get rid of the domains, but because their devices aren'= t freed (because you removed the info about them) the domains won't go away= . So xend keeps detecting crashed domains and trying to get rid of them. Not the nicest behaviour - crashes don't happen very much so this path is not well-explored. > xend-debug.log and xm dmesg are silent. >=20 > Anything useful I can try to get more information about this before I=20 > reboot the beast ? :-) At this point you're pretty stuck. Time for a reboot. Mike ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://productguide.itmanagersjournal.com/