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

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

To: Pasi Kärkkäinen <pasik@xxxxxx>
Subject: [Xen-users] Re: [Xen-devel] dom0-cpus problem with Xen 3.4.1-rc6
From: Nerijus Narmontas <n.narmontas@xxxxxxxxx>
Date: Wed, 22 Jul 2009 19:42:14 +0300
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx, xen-users@xxxxxxxxxxxxxxxxxxx
Delivery-date: Wed, 22 Jul 2009 09:43:02 -0700
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type; bh=CSSKrUu7DpQjFJ5lgqcrjlq+J3I9KFKpNzuYroeHhbI=; b=DYjixMhZ/4nTifYY2AdSehJfixWK7UhXmmoknDAcJaNe6F+/D3xWnvMsuiN2Bm4HiZ g4lU+/ZwSrgiSbi4qNSrNAOnu4mJXva2OF7KF2yAgfRV4/z1rZFYv9X+2Xqq+R2lbhqE oS3KI0C3aUvUTcBCyThlOJDxsCuoy+23OEQ/I=
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=nGNqCXy4Sg5TELQbVNLXekNvlGIA3z2ZxncfhhdDC/HtgVynrv02miPq14x40q6CgQ 6D8g1+DwBJSkvnvTWuwQRUqUDR/ie+m1KlvTua5FFROitBG9lgzljn/vDwboaNfFcqjD HTOqLmtTAxIDmKwEZVbYDTOlyOdLv3Tk0n3fA=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <20090722163903.GG24960@xxxxxxxxxxxxxxx>
List-help: <mailto:xen-users-request@lists.xensource.com?subject=help>
List-id: Xen user discussion <xen-users.lists.xensource.com>
List-post: <mailto:xen-users@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
References: <AEC6C66638C05B468B556EA548C1A77D016DDD27@trantor> <771c502a0907210353o49ed1f29i8a0540e0572b5d9f@xxxxxxxxxxxxxx> <20090721110138.GP24960@xxxxxxxxxxxxxxx> <771c502a0907220818v41307fe4m9040336191ea2341@xxxxxxxxxxxxxx> <20090722152134.GD24960@xxxxxxxxxxxxxxx> <771c502a0907220934m3593602dv830d49fa219f6c4c@xxxxxxxxxxxxxx> <20090722163903.GG24960@xxxxxxxxxxxxxxx>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
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.
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?

_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users
<Prev in Thread] Current Thread [Next in Thread>