Hi, we''ve started using Xen 4.0.1 yesterday and know we have a problem with vcpu_avail within our domu configs, which work as intended with Xen 3.2. In our config we have the following 2 lines: vcpus = 8 vcpu_avail = 1 After starting the domu, it has got 8 cpus instead of 1. Does anyone know if this option has changed with Xen4 or what may cause vcpu_avail to fail? Thanks in advance for your help. Cheers, Jan _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
On 09/09/2010 04:08 PM, Jan Marquardt wrote:> Hi, > > we''ve started using Xen 4.0.1 yesterday and know we have a problem with > vcpu_avail within our domu configs, which work as intended with Xen 3.2. > > In our config we have the following 2 lines: > > vcpus = 8 > vcpu_avail = 1 > > After starting the domu, it has got 8 cpus instead of 1. Does anyone > know if this option has changed with Xen4 or what may cause vcpu_avail > to fail?I did some testing on this topic and found out that in /var/log/xen/xend.log it always says "''vcpu_avail'': ''255''". It makes no difference if I set vcpu_avail to 1, 8, 255 or anything else or remove it completely from the config. Any ideas? [2010-09-10 11:02:45 6309] DEBUG (XendDomainInfo:3400) Storing VM details: {''on_xend_stop'': ''ignore'', ''shadow_memory'': ''0'', ''uuid'': ''58c2fdf8-3ef0-3924-cb3f-1cc955913503'', ''on_reboot'': ''restart'', ''start_time'': ''1284109365.08'', ''on_poweroff'': ''destroy'', ''bootloader_args'': '''', ''on_xend_start'': ''ignore'', ''on_crash'': ''restart'', ''xend/restart_count'': ''0'', ''vcpus'': ''8'', ''vcpu_avail'': ''255'', ''bootloader'': '''', ''image'': "(linux (kernel /home/xen/shared/boot/debian/vmlinuz-2.6.26-2-xen-686) (ramdisk /home/xen/shared/boot/debian/initrd.img-2.6.26-2-xen-686) (args ''root=/dev/md0 ro 2 TERM=xterm xencons=tty console=tty1 clock=jiffies'') (superpages 0) (tsc_mode 0) (videoram 4) (pci ()) (nomigrate 0) (notes (HV_START_LOW 4118806528) (FEATURES ''writable_page_tables|writable_descriptor_tables|auto_translated_physmap|pae_pgdir_above_4gb|supervisor_mode_kernel'') (VIRT_BASE 3221225472) (GUEST_VERSION 2.6) (PADDR_OFFSET 0) (GUEST_OS linux) (HYPERCALL_PAGE 3222278144) (LOADER generic) (SUSPEND_CANCEL 1) (PAE_MODE yes) (ENTRY 3222274048) (XEN_VERSION xen-3.0)))", ''name'': ''www434''}> Thanks in advance for your help. > > Cheers, > > Jan > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xensource.com > http://lists.xensource.com/xen-users_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Hi,
I think I''ve found a bug in xm/create.py which leads to this behaviour:
http://lists.xensource.com/archives/html/xen-changelog/2009-11/msg00132.html
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 (?)
later.
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@artfiles.de: need to read vcpu_avail here since it isn''t done
later.
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?
Regards
Tim Evers
Artfiles GmbH
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users
On Mon, Sep 13, 2010 at 10:07 PM, Tim Evers <it@niemail.de> wrote:> Hi, > > I think I''ve found a bug in xm/create.py which leads to this behaviour: > > http://lists.xensource.com/archives/html/xen-changelog/2009-11/msg00132.html > introduces the "maxvcpus" parameter> I would have filed a bug report for this but I have not found Xen4 on > Xen Bugzilla. Any hints on this?Try posting your mail to xen-devel -- Fajar _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users