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

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



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.

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

KVM supports it and does respect it. You really have to be able to adjust the bandwidth depending on your transport and network capabilities or you'll burn too much CPU and not converge.

Regards,

Anthony Liguori

regards
john


--
Libvir-list mailing list
Libvir-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/libvir-list

[Index of Archives]     [Virt Tools]     [Libvirt Users]     [Lib OS Info]     [Fedora Users]     [Fedora Desktop]     [Fedora SELinux]     [Big List of Linux Books]     [Yosemite News]     [KDE Users]     [Fedora Tools]