Re: [Qemu-block] [PATCH] migration: flush the bdrv before stopping VM

2015-06-25 Thread Stefan Hajnoczi
On Wed, Jun 24, 2015 at 11:08:43AM +, Li, Liang Z wrote: Right now, we don't have an interface to detect that cases and got back to the iterative stage. How about go back to the iterative stage when detect that the pending_size is larger Than max_size, like this:

Re: [Qemu-block] [PATCH] migration: flush the bdrv before stopping VM

2015-06-24 Thread Li, Liang Z
Right now, we don't have an interface to detect that cases and got back to the iterative stage. How about go back to the iterative stage when detect that the pending_size is larger Than max_size, like this: +/* do flush here is aimed to shorten the VM

Re: [Qemu-block] [PATCH] migration: flush the bdrv before stopping VM

2015-03-25 Thread Juan Quintela
Li, Liang Z liang.z...@intel.com wrote: Right now, we don't have an interface to detect that cases and got back to the iterative stage. How about go back to the iterative stage when detect that the pending_size is larger Than max_size, like this: +/* do flush here

Re: [Qemu-block] [PATCH] migration: flush the bdrv before stopping VM

2015-03-18 Thread Kevin Wolf
Am 18.03.2015 um 13:36 hat Juan Quintela geschrieben: Kevin Wolf kw...@redhat.com wrote: The problem is that the block layer really doesn't have an option to control what is getting synced once the data is cached outside of qemu. Essentially we can do an fdatasync() or we can leave it,