Re: domain id number on xen unstable

["Pasi Kärkkäinen" <pasik@iki.fi>]

On Mon, Mar 09, 2009 at 10:49:53AM +0000, Andrew Lyon wrote:
> On Mon, Mar 9, 2009 at 10:35 AM, James Harper
> <james.harper@bendigoit.com.au> wrote:
> >> > Monday -- you could try reverting it (hg revert 19250), re-install dom0
> >> > tools, and see if that helps.
> >> >
> >> >  -- 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=$(xenstore-read
> >> "/local/domain/${path_array[2]}/vm")
> >>
> >> Andy
> >>
> >
> > Andy,
> >
> > What Dom0 kernel are you actually running? I spent ages tracking down a problem 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
> 

Afaik that tree is not maintained by anyone.. ie. there was only the initial
commit, and all the known bugs etc are not fixed in that tree.

I don't know why Novell guys don't submit their patches/fixes there..

-- Pasi