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

[Pasi Kärkkäinen <pasik@xxxxxx>]

On Wed, Jan 13, 2010 at 09:38:56PM +0000, Andrew Lyon wrote:
> 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
> 

Good catch! And good timing, I was just about to start digging the
source :)

Thanks!

-- Pasi


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