This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
Home Products Support Community News


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

To: xen-users@xxxxxxxxxxxxxxxxxxx
Subject: Re: [Xen-users] Xen4: problem with vcpu_avail
From: Jan Marquardt <jm@xxxxxxxxxxx>
Date: Fri, 10 Sep 2010 11:08:21 +0200
Delivery-date: Fri, 10 Sep 2010 02:09:35 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <4C88EA70.4040300@xxxxxxxxxxx>
List-help: <mailto:xen-users-request@lists.xensource.com?subject=help>
List-id: Xen user discussion <xen-users.lists.xensource.com>
List-post: <mailto:xen-users@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
References: <4C88EA70.4040300@xxxxxxxxxxx>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv: Gecko/20100713 Lightning/1.0b1 Thunderbird/3.0.6
On 09/09/2010 04:08 PM, Jan Marquardt wrote:

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.



Xen-users mailing list

Xen-users mailing list

<Prev in Thread] Current Thread [Next in Thread>