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-API] how to use credit scheduler in xcp

To: Mike McClurg <mike.mcclurg@xxxxxxxxxx>
Subject: Re: [Xen-API] how to use credit scheduler in xcp
From: George Shuklin <george.shuklin@xxxxxxxxx>
Date: Tue, 24 May 2011 14:05:38 +0400
Cc: "xen-api@xxxxxxxxxxxxxxxxxxx" <xen-api@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Tue, 24 May 2011 03:06:26 -0700
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:subject:from:to:cc:in-reply-to:references :content-type:date:message-id:mime-version:x-mailer :content-transfer-encoding; bh=jtf+WOQQNdDV8vE0vRzRmskjBqOI4OugVt+oLB3XIZE=; b=usEWp58nK485PMmJI4XhXar1pmKNtxeBreAtod4kITda1AGb6aFHGEOX+V8bvART1d ztqTpbmw1gYSncpBnLPeQDws5Z2k5+MRH4EtA/SvzUiM2ygss3IIyve0OXPbax2xpkZ3 wpQUEWawKR2UO7LF2W/YE3+tFot4Mr5QNt2BE=
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=subject:from:to:cc:in-reply-to:references:content-type:date :message-id:mime-version:x-mailer:content-transfer-encoding; b=t6D+9qwnXlriTWFA5TLlkd56ryRX9acqLfnjWi5GztyPZC5Z7OO56tM2c1ddiRebKO O3VkFrvaud9ddDRFvXAj/IeTKGjWXl5gzw5wredRFBG8IShOHVsikVTypZ1KYycQ2FOy rrebHI2Ty/4n0sX3ZN+3MCOIHRSVhsoaOtI9s=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <4DDB6257.6070200@xxxxxxxxxx>
List-help: <mailto:xen-api-request@lists.xensource.com?subject=help>
List-id: Discussion of API issues surrounding Xen <xen-api.lists.xensource.com>
List-post: <mailto:xen-api@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-api>, <mailto:xen-api-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-api>, <mailto:xen-api-request@lists.xensource.com?subject=unsubscribe>
References: <4DDA57FB.5060305@xxxxxxxxx> <1306155312.6844.2.camel@mabase> <4DDB6257.6070200@xxxxxxxxxx>
Sender: xen-api-bounces@xxxxxxxxxxxxxxxxxxx
No, you can use xl/xc with xapi.

Python binding for xc is installed for python in XCP (import
xen.lowlevel.xc), and xl is avaible.

You can freely change weight/cap for domains online, this will works
until VM migrate/reboot.

You can not do following things with xl under xapi control: 

domain destroy, create domain save, resume, migrate, cd-insert/eject,
pci* commands

You can do xl list (and this is much faster, than xe vm-list
resident-on=`xe host-list name-label=$(hostname)`), xl pause/unpause
(but no domain state change). xl console (for domains with
no_pv_vnc_console attribute) and so on.

It's pretty simple to understand what is allowed: xapi control domain
life cycle, until you do not change it, everything is ok.

We, actually, do many things with domain via libxc  in product and this
does not mess with xapi. The most important thing is, f.e., domain
mandatory shutdown. If domain not responding, when you send shutdown,
xapi waiting until timeout before performing next (shutdown --force),
and if you do xc.domain_shutdown(), xapi found domain is shutdowned it
reacts normally,

I think, after XCP was published under free license, we can say it
starts to loosing it 'closed appliance' appearance: you can hack it any
comfortable way until you know what you do.

В Втр, 24/05/2011 в 08:46 +0100, Mike McClurg пишет:
> On 05/23/2011 01:55 PM, George Shuklin wrote:
> > Yeah, they are supported by xapi.
> >
> > xe vm-param-set uuid=... VCPU-params:caps=X VCPU-params:weight=Y
> >
> > (same xapi call is available).
> >
> > Note: xapi require to reboot VM to make this works. To change values
> > online you can use (without xapi) xl command line or libxc.
> >
> I wouldn't recommend using xm/xl on XCP. This could cause all kinds of havoc 
> with xapi's internal state, and I don't even think we have the xm/xl commands 
> installed in dom0. If you were using just the Xen hypervisor on its own, this 
> would be the way to go.
> Mike

xen-api mailing list

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