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

Re: [Xen-users] Xen4: problem with vcpu_avail

  • To: xen-users@xxxxxxxxxxxxxxxxxxx
  • From: Tim Evers <it@xxxxxxxxxx>
  • Date: Mon, 13 Sep 2010 17:07:18 +0200
  • Delivery-date: Mon, 13 Sep 2010 08:22:22 -0700
  • List-id: Xen user discussion <xen-users.lists.xensource.com>


I think I've found a bug in xm/create.py which leads to this behaviour:

introduces the "maxvcpus" parameter. It states that

"this is patch to add maxvcpus support to xen xm command. It's using
vcpu_avail bitmask and sets the number of vcpus to maxvcpus if
present.  If it's not present, old behavior is preserved."

The last part is untrue as far as I understand. If maxvcpus is unset,
vcpu_avail is not read at all. The patch removes it from the parameter
list given to add_conf without adding it in another place. As a result
vcpu_avail remains unset and is filled with the default value of 255 (?)

This patch to fixes the issue for me:

--- create.py   2010-09-08 15:52:18.000000000 +0200
+++ create.py.af        2010-09-13 16:59:48.000000000 +0200
@@ -1120,8 +1120,10 @@

         # For case we don't have maxvcpus set but we have vcpus we preserve
         # old behaviour
+       # te@xxxxxxxxxxx: need to read vcpu_avail here since it isn't done 
         if not maxvcpus and vcpus:
             config.append(['vcpus', vcpus])
+            config.append(['vcpu_avail', getattr(vals, 'vcpu_avail'])

     def add_conf(n):
         if hasattr(vals, n):

I would have filed a bug report for this but I have not found Xen4 on
Xen Bugzilla. Any hints on this?


Tim Evers
Artfiles GmbH

Xen-users mailing list



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