[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] Re: [Xen-devel] How to activate all VPCUS for a domU?
On Fri, Nov 16, 2012 at 08:19:07PM +0000, Omer K. wrote: > Hi, > > Apologies for earlier spamming the xen-devel list but this message might be > relevant as I think there is a bug in xm/create.py where 'vcpu_avail' > option doesn't get properly set. > > I manage to solve the issue of activating all of the vcpus by apply a > modified version of the patch earlier discussed: > > http://old-list-archives.xen.org/archives/html/xen-users/2010-09/msg00353.html > > The following patch fixed the issue for me and after this bitmask value was > activating required vpcu's read from the xen configuration file. Prior to > that, vpcu_avail was always set to '1' (also verified from 'xenstore-ls -f' > output). > > --- create.py > +++ create.py.af > > if maxvcpus and vcpus: > config.append(['vcpus', vcpus]) > - config.append(['vcpu_avail', (1 << vcpus) -1)]) > + config.append(['vcpu_avail', getattr(vals, 'vcpu_avail']) > > def add_conf(n): > if hasattr(vals, n): Could you want repost this with an Signed-off-By. There is a nice description here on how to do it: http://wiki.xen.org/wiki/Submitting_Xen_Patches > > Regards. > Omer > > > On Fri, Nov 16, 2012 at 6:21 PM, Mats Petersson > <mats.petersson@xxxxxxxxxx>wrote: > > > On 16/11/12 18:09, Omer K. wrote: > > > >> Hi, > >> > >> I have set maxvcpus and vcpus options in my domU configuration file, and > >> I can see that X number of vcpu are set for the domU. > >> > >> I tried to activate all the vpcus by using vpcu_avail option (using > >> decimal to represent vpcu bitmask e.g. 24=11000) but it doesn't seem to > >> work, and only the first vpcu is activated (i.e. has -b- state) while all > >> other vpcu's set for the domU are in the paused state. > >> > >> Can any one share more insights on how to activate all the vpcu's for the > >> guest domain ? > >> > >> Thanks > >> > > This definitely belongs to the Xen-Users list, not on Xen-Devel. Please > > don't post to both lists, it just confuses people. > > > > -- > > Mats > > > > ______________________________**_________________ > > Xen-devel mailing list > > Xen-devel@xxxxxxxxxxxxx > > http://lists.xen.org/xen-devel > > > _______________________________________________ > Xen-devel mailing list > Xen-devel@xxxxxxxxxxxxx > http://lists.xen.org/xen-devel _______________________________________________ Xen-devel mailing list Xen-devel@xxxxxxxxxxxxx http://lists.xen.org/xen-devel
|
Lists.xenproject.org is hosted with RackSpace, monitoring our |