RE: [Xen-devel] domain id number on xen unstable

["Venefax" <venefax@xxxxxxxxx>]

I had the same bug and Suse support determined that you need at least two
processors assigned to dom0, otherwise you get that odd behavior.
Federico

-----Original Message-----
From: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
[mailto:xen-devel-bounces@xxxxxxxxxxxxxxxxxxx] On Behalf Of Andrew Lyon
Sent: Monday, March 09, 2009 6:50 AM
To: James Harper
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx; Keir Fraser
Subject: Re: [Xen-devel] domain id number on xen unstable

On Mon, Mar 9, 2009 at 10:35 AM, James Harper
<james.harper@xxxxxxxxxxxxxxxx> 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


> 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' it
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 whole
system ran out of resources.
>
> The bug would only come about if you limited Dom0 to a single CPU via
'(dom0-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
>
>

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel


_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel