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-devel] Question about vcpu_avail

To: Michal Novotny <minovotn@xxxxxxxxxx>, "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject: Re: [Xen-devel] Question about vcpu_avail
From: Keir Fraser <keir.fraser@xxxxxxxxxxxxx>
Date: Tue, 24 Nov 2009 15:20:52 +0000
Delivery-date: Tue, 24 Nov 2009 07:21:27 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <4B0BF6E0.4070707@xxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: AcptGAlwyM1ifyyfRXy2iKeck9lvOQAAawPl
Thread-topic: [Xen-devel] Question about vcpu_avail
User-agent: Microsoft-Entourage/
On 24/11/2009 15:08, "Michal Novotny" <minovotn@xxxxxxxxxx> wrote:

>> Yeah, I think you get it. In your example: if the user specifies maxvcpus=4,
>> vcpus=2 then xm turns that into vcpus=4, vcpu_avail=3 before sending it to
>> xend.
> Right, so, you mean that I should implement it into `xm` command itself
> and not XenD ? Well, what about people using eg. libvirt with upstream
> Xen? This way it should not be working since XM is not used... right?

If you add new config fields to xend, then libvirt callers are going to need
to be modified to expose them to users, aren't they (e.g., in a GUI or
whatever)? If the callers need modifying anyway, then they can just be
modified in a similar way to what I propose for xm, and deconstruct into the
config primitives that xend already understands.

 -- Keir

Xen-devel mailing list