WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

Re: [Xen-devel] dom0-cpus problem with Xen 3.4.1-rc6

On Wed, Jul 22, 2009 at 07:42:14PM +0300, Nerijus Narmontas wrote:
> On Wed, Jul 22, 2009 at 7:39 PM, Pasi Kärkkäinen <pasik@xxxxxx> wrote:
> 
> > On Wed, Jul 22, 2009 at 07:34:16PM +0300, Nerijus Narmontas wrote:
> > > On Wed, Jul 22, 2009 at 6:21 PM, Pasi Kärkkäinen <pasik@xxxxxx> wrote:
> > >
> > > > On Wed, Jul 22, 2009 at 06:18:37PM +0300, Nerijus Narmontas wrote:
> > > > > On Tue, Jul 21, 2009 at 2:01 PM, Pasi Kärkkäinen <pasik@xxxxxx>
> > wrote:
> > > > >
> > > > > > On Tue, Jul 21, 2009 at 01:53:25PM +0300, Nerijus Narmontas wrote:
> > > > > > > Hello,
> > > > > > > If I set (dom0-cpus 1) in /etc/xen/xend-config.sxp, after I
> > > > gracefully
> > > > > > > shutdown domU, the domain stays in ---s- state.
> > > > > > >
> > > > > > > Is this fixed in 3.4.1-rc8?
> > > > > > >
> > > > > >
> > > > > > Hello.
> > > > > >
> > > > > > Please don't hijack threads - you replied to a thread about network
> > > > > > problems
> > > > > > and gplpv drivers. Always start a new thread for new subjects.
> > > > > >
> > > > > > What version are you seeing this behaviour with? Xen 3.4.0 ? What
> > dom0
> > > > > > kernel version?
> > > > > >
> > > > > > -- Pasi
> > > > > >
> > > > >
> > > > > Sorry for the threads thing.
> > > > >
> > > > > root@xen1:/# more /etc/xen/xend-config.sxp | grep cpu
> > > > > # In SMP system, dom0 will use dom0-cpus # of CPUS
> > > > > # If dom0-cpus = 0, dom0 will take all cpus available
> > > > > (dom0-cpus 1)
> > > > >
> > > > > root@xen1:/# xm dmesg | grep Command
> > > > > (XEN) Command line: console=com2 com2=115200,8n1
> > > > >
> > > > > root@xen1:/# xm dmesg | grep VCPUs
> > > > > (XEN) Dom0 has maximum 8 VCPUs
> > > > >
> > > > > root@xen1:/# xm vcpu-list
> > > > > Name                                ID  VCPU   CPU State   Time(s)
> > CPU
> > > > > Affinity
> > > > > Domain-0                             0     0     5   r--       9.2
> > any
> > > > cpu
> > > > > Domain-0                             0     1     -   --p       1.8
> > any
> > > > cpu
> > > > > Domain-0                             0     2     -   --p       1.7
> > any
> > > > cpu
> > > > > Domain-0                             0     3     -   --p       1.6
> > any
> > > > cpu
> > > > > Domain-0                             0     4     -   --p       1.4
> > any
> > > > cpu
> > > > > Domain-0                             0     5     -   --p       1.4
> > any
> > > > cpu
> > > > > Domain-0                             0     6     -   --p       1.5
> > any
> > > > cpu
> > > > > Domain-0                             0     7     -   --p       1.3
> > any
> > > > cpu
> > > > >
> > > > > root@xen1:/# xm create /etc/xen/dc3.conf
> > > > > Using config file "/etc/xen/dc3.conf".
> > > > > Started domain dc3 (id=1)
> > > > >
> > > > > root@xen1:/# xm vcpu-list
> > > > > Name                                ID  VCPU   CPU State   Time(s)
> > CPU
> > > > > Affinity
> > > > > Domain-0                             0     0     7   r--      36.5
> > any
> > > > cpu
> > > > > Domain-0                             0     1     -   --p       1.8
> > any
> > > > cpu
> > > > > Domain-0                             0     2     -   --p       1.7
> > any
> > > > cpu
> > > > > Domain-0                             0     3     -   --p       1.6
> > any
> > > > cpu
> > > > > Domain-0                             0     4     -   --p       1.4
> > any
> > > > cpu
> > > > > Domain-0                             0     5     -   --p       1.4
> > any
> > > > cpu
> > > > > Domain-0                             0     6     -   --p       1.5
> > any
> > > > cpu
> > > > > Domain-0                             0     7     -   --p       1.3
> > any
> > > > cpu
> > > > > dc3                                  1     0     0   -b-      15.2 0
> > > > > dc3                                  1     1     1   -b-       6.8 1
> > > > > dc3                                  1     2     2   -b-       7.5 2
> > > > > dc3                                  1     3     3   -b-       8.0 3
> > > > >
> > > > > After HVM Windows domU shutdown, it stays in ---s- state.
> > > > >
> > > > > root@xen1:/# xm li
> > > > > Name                                        ID   Mem VCPUs      State
> > > > > Time(s)
> > > > > Domain-0                                     0 24106     1     r-----
> > > > > 58.7
> > > > > dc3                                          1  8192     4     ---s--
> > > > > 59.0
> > > > >
> > > > > root@xen1:/# xm vcpu-list
> > > > > Name                                ID  VCPU   CPU State   Time(s)
> > CPU
> > > > > Affinity
> > > > > Domain-0                             0     0     4   r--      48.4
> > any
> > > > cpu
> > > > > ...
> > > > > Domain-0                             0     7     -   --p       1.3
> > any
> > > > cpu
> > > > > dc3                                  1     0     0   ---      20.0 0
> > > > > dc3                                  1     1     1   ---      10.9 1
> > > > > dc3                                  1     2     2   ---      15.2 2
> > > > > dc3                                  1     3     3   ---      12.9 3
> > > > >
> > > > > The problem goes away if I tell Xen to boot with options
> > dom0_max_vcpus=1
> > > > > dom0_vcpus_pin.
> > > > >
> > > > > What's the difference between Xen boot options to limit vcpus for
> > dom0 to
> > > > > /etc/xen/xend-config.sxp?
> > > > >
> > > > > I am running Xen 3.4.1-rc6 version.
> > > >
> > > > OK.
> > > >
> > > > What dom0 kernel version are you running?
> > > >
> > > > -- Pasi
> > > >
> > >
> > > From Ubuntu hardy-backports repositories 2.6.24-24-xen.
> >
> > Maybe dom0 kernel is your problem.. I remember there was a bug in kernel
> > that caused that kind of problems.
> >
> > That hardy's dom0 kernel is known to have other bugs aswell.
> >
> > If possible, try running the latest linux-2.6.18-xen from xenbits.
> > Or some other dom0 kernel, and see if that fixes the problem.
> >
> > -- Pasi
> >
> 
> Ok I will try to build the latest 2.6.18 kernel.

hg clone http://xenbits.xen.org/linux-2.6.18-xen.hg

> Can you tell me what's the difference between Xen boot
> option dom0_max_vcpus=1 and (dom0-cpus 1) option
> in /etc/xen/xend-config.sxp?

If I haven't misunderstood this dom0-cpus option in xend-config.sxp tells 
which physical CPUs/cores vcpu's of dom0 will use..

ie. if you limit dom0_max_vcpus=1, then you can use dom0-cpus to tell which
one of the 8 available cpus/cores dom0's 1 vcpu will run on.

So you can use that option do dedicate a core for dom0, and then use the
cpus= option for other domains to make them use other cores.. and this way
you'll be able to dedicate a core _only_ for dom0.

But yeah, I don't know why you're seeing problems with shutting down HVM
domains.. sounds like a bug, like I said earlier..

-- Pasi

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

<Prev in Thread] Current Thread [Next in Thread>