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,
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
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.
xen-api mailing list