search for: bdrv_is_allocated_above

...;:"fd:migrate"},"id":"libvirt-223"} > > > However I observe what you do - disk migration is not shaped, while internal state is. Thanks for raising this. I noticed that mirror_run() does not throttle the first loop where it populates the dirty bitmap using bdrv_is_allocated_above(). The main copy loop does take the speed limit into account but perhaps that's broken too. Paolo, Jeff: Any ideas? Stefan

> Thanks for raising this. > > I noticed that mirror_run() does not throttle the first loop where it > populates the dirty bitmap using bdrv_is_allocated_above(). This is on purpose. Does it causes a noticeable stall in the guest? > The main > copy loop does take the speed limit into account but perhaps that's > broken too. Yeah, it looks broken. Each iteration of the loop can write much more than sectors_per_chunk sectors, but here:...

On 24/02/14 23:26, Paolo Bonzini wrote: >> Thanks for raising this. >> >> I noticed that mirror_run() does not throttle the first loop where it >> populates the dirty bitmap using bdrv_is_allocated_above(). > This is on purpose. Does it causes a noticeable stall in the guest? > >> The main >> copy loop does take the speed limit into account but perhaps that's >> broken too. > Yeah, it looks broken. Each iteration of the loop can write much more > than sectors_per...

Hi all, As I am doing some tests with qemu, I realized that the way it does 'migrate -i tcp:DEST:444' is not the same as 'libvirt migrate --copy-storage-inc'. Basically qemu uses the same stream as RAM migration and libvirt takes advantage of NBD transfer. With virsh migrate-setspeed I observed that one can only control the transfer throughput of RAM, but not disk