From mboxrd@z Thu Jan 1 00:00:00 1970 From: Andrew Lyon Subject: Re: domain id number on xen unstable Date: Mon, 9 Mar 2009 10:49:53 +0000 Message-ID: References: Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Return-path: In-Reply-To: List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: James Harper Cc: xen-devel@lists.xensource.com, Keir Fraser List-Id: xen-devel@lists.xenproject.org On Mon, Mar 9, 2009 at 10:35 AM, James Harper wrote: >> > Monday -- you could try reverting it (hg revert 19250), re-install dom= 0 >> > tools, and see if that helps. >> > >> > =A0-- Keir >> >> Keir, >> >> I tried that but it didn't help, however I noticed that there were >> several xen-hotplug-cleanup scripts running, and that script has >> changed between 3.3.1 and unstable, on my 3.3.1 system I can run the >> script and it exits very quickly, but on my unstable system the script >> can only be run once, after that it hangs trying to get the lock, I >> added a couple of echo's to the script as you can see below, only the >> first one is executed, the second is not and as the rest of the script >> is not run the lock is never released. >> >> So the offending line is vm=3D$(xenstore-read >> "/local/domain/${path_array[2]}/vm") >> >> Andy >> > > Andy, > > What Dom0 kernel are you actually running? I spent ages tracking down a p= roblem that didn't seem to be affecting anyone else but it turned out to be= a bug in the linux Dom0 kernel. > The latest from http://xenbits.xensource.com/ext/linux-2.6.27-xen.hg > The symptoms were (IIRC) that 'xm reboot' would shut the domain down but = it would still be there in a cleaning up state. If I executed 'xm create' i= t would complete the reboot, but bits and pieces were also left running in = xen and dom0 so you could only get dom id up to about 70 or so before the w= hole system ran out of resources. > > The bug would only come about if you limited Dom0 to a single CPU via '(d= om0-cpus 1)' in xend-config.sxp. > > If you are running a kernel that roughly matches your version of unstable= then this won't be your problem. > > James > >