My bad. I found that in the 0.9.3 tags. Thanks.
- Hui
On 7/15/11 2:57 PM, "Eric Blake" wrote:
>On 07/15/2011 12:34 PM, Hui Kang wrote:
>> Hi,
>> I checked the libvirt git tree. It seems that this patch has not been
>>applied.
>> I think to use virsh command line to control the migration ban
On 07/15/2011 12:34 PM, Hui Kang wrote:
> Hi,
> I checked the libvirt git tree. It seems that this patch has not been applied.
> I think to use virsh command line to control the migration bandwidth is
> useful. Thanks.
>
> - Hui
>
>
>
> API virDomainMigrateSetMaxSpeed was introduced since
Hi,
I checked the libvirt git tree. It seems that this patch has not been applied.
I think to use virsh command line to control the migration bandwidth is useful.
Thanks.
- Hui
API virDomainMigrateSetMaxSpeed was introduced since 0.9.0, but
no command in virsh yet.
---
tools/virsh.c |
On 06/07/2011 08:38 PM, Eric Blake wrote:
On 06/07/2011 06:45 AM, Osier Yang wrote:
API virDomainMigrateSetMaxSpeed was introduced since 0.9.0, but
no command in virsh yet.
---
tools/virsh.c | 46 ++
tools/virsh.pod |5 +
2 files change
On 06/07/2011 06:45 AM, Osier Yang wrote:
> API virDomainMigrateSetMaxSpeed was introduced since 0.9.0, but
> no command in virsh yet.
> ---
> tools/virsh.c | 46 ++
> tools/virsh.pod |5 +
> 2 files changed, 51 insertions(+), 0 deletions(-)
API virDomainMigrateSetMaxSpeed was introduced since 0.9.0, but
no command in virsh yet.
---
tools/virsh.c | 46 ++
tools/virsh.pod |5 +
2 files changed, 51 insertions(+), 0 deletions(-)
diff --git a/tools/virsh.c b/tools/virsh.c
index d98b
