[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-devel] Xen hypervisor dom0_vcpus option broken in Xen 3.4 ?


  • To: Pasi Kärkkäinen <pasik@xxxxxx>
  • From: Andrew Lyon <andrew.lyon@xxxxxxxxx>
  • Date: Wed, 13 Jan 2010 21:38:56 +0000
  • Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
  • Delivery-date: Wed, 13 Jan 2010 13:39:37 -0800
  • 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:content-transfer-encoding; b=KXwG754B7bMr15/0pu0LoGd1ytSF/fh799wXwwrbM/KiPW0DBGR76Bwg6h9CeC+Yv+ TTvpkpcLGlTFW6f7iNNUW4qlx7jZBcS2UI3nbZIWhFNLoa63W3gFLZiKAAXTD72N8RwH 9xykX2It2fKJi4A0N39NiMnZwZeFe+12NQYTQ=
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>

On Wed, Jan 13, 2010 at 8:36 PM, Pasi Kärkkäinen <pasik@xxxxxx> wrote:
> Hello,
>
> while discussing things on xen-users we noticed this:
>
> (XEN) Xen version 3.4.2 (root@(none)) (gcc version 4.4.2 20091027 (RedHat 
> 4.4.2-7) (GCC) ) Mon Dec 14 06:53:18 EET 2009
> (XEN) Latest ChangeSet: unavailable
> (XEN) Command line: dom0_mem=1G loglvl=all guest_loglvl=all com1=38400,8n1 
> console=com1 dom0_vcpus=1
> ..
> (XEN) Dom0 has maximum 4 VCPUs
> ..
>
> Has dom0_vcpus option name changed, or is it just broken?
>
> -- Pasi
>
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/xen-devel
>

Looks like it is called dom0_max_vcpus in 3.4.2:

cat xen-3.4.2.gz |gzip -d | strings | grep cpus | grep dom0
dom0_vcpus_pin
dom0_max_vcpus

Andy

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


 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.