On 04/19/2012 03:00 PM, Jiri Denemark wrote:
> On Mon, Apr 16, 2012 at 23:06:03 -0600, Eric Blake wrote:
>> In qemu, it is possible to call 'migrate_set_speed' prior to
>> 'migrate', and therefore ensure a constant throttling through the
>> entire migration. However, this is not possible with
>> '
On Mon, Apr 16, 2012 at 23:06:03 -0600, Eric Blake wrote:
> In qemu, it is possible to call 'migrate_set_speed' prior to
> 'migrate', and therefore ensure a constant throttling through the
> entire migration. However, this is not possible with
> 'block-job-set-speed', which fails if a job is not a
In qemu, it is possible to call 'migrate_set_speed' prior to
'migrate', and therefore ensure a constant throttling through the
entire migration. However, this is not possible with
'block-job-set-speed', which fails if a job is not already active.
This means that you can't detect a device that does
