[Libvir] [PATCH 1/2] virDomainMigrate implementation (Xen only, no remote, no qemu, no virsh)

Richard W.M. Jones rjones at redhat.com
Mon Jul 16 16:09:28 UTC 2007


John Levon wrote:
> On Mon, Jul 16, 2007 at 04:56:53PM +0100, Richard W.M. Jones wrote:
> 
>>  * @resource: (optional) specify resource limit in Mbps
>>  *
>>  * The maximum bandwidth (in Mbps) that will be used to do migration
>>  * can be specified with the resource parameter.  If set to 0,
>>  * libvirt will choose a suitable default.  Some hypervisors do
>>  * not support this feature and will return an error if resource
>>  * is not 0.
> 
> Will there be another way to find this out? It would be unfortunate if
> the only way was to actually attempt it.

virConnectGetCapabilities should return something to say whether this is 
supported.  I'll add that to my implementation.

> Also, are there any backends that /do/ support it? (Xen's option has
> always been ignored)

That is a very good point actually.  xend does ignore the resource 
parameter :-(

I was rather hoping that KVM would be doing the right thing.

Rich.

-- 
Emerging Technologies, Red Hat - http://et.redhat.com/~rjones/
Registered Address: Red Hat UK Ltd, Amberley Place, 107-111 Peascod
Street, Windsor, Berkshire, SL4 1TE, United Kingdom.  Registered in
England and Wales under Company Registration No. 03798903
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/x-pkcs7-signature
Size: 3237 bytes
Desc: S/MIME Cryptographic Signature
URL: <http://listman.redhat.com/archives/libvir-list/attachments/20070716/b4562984/attachment-0001.bin>


More information about the libvir-list mailing list