[pve-devel] Baloon Device is the problem! Re: migration problems since qemu 1.3

[Dietmar Maurer]

> I remember same problem with qemu_block_set_io_throttle()
> vm_mon_cmd($vmid, "block_set_io_throttle", device => $deviceid, bps =>
> int($bps), bps_rd => int($bps_rd), bps_wr => int($bps_wr), iops => int($iops),
> iops_rd => int($iops_rd), iops_wr => int($iops_wr));
> 
> So maybe does it send crap if the value is not casted ?

No, it send a string value instead (value => "1").

> Also the value should not be int but float, qmp doc said that we can use 0.5,
> 0.30, as value.

honestly, I am glad if migration work at all ;-) What is the use case of setting it
to 0.5 or 0.3?

Note: The current time estimation is wrong anyways, and it will always be  a rough
estimation.
   
> also query-migrate returns some new 2 cools values about downtime, I think
> we should display them in query migrate log
> 
> - "downtime": only present when migration has finished correctly
>               total amount in ms for downtime that happened (json-int)
> - "expected-downtime": only present while migration is active
>                 total amount in ms for downtime that was calculated on
> 		the last bitmap round (json-int)

Yes, that sounds interesting.