Hi, I mean this function will be called after migration to do something for the block device. I tried and debugged the qemu code. (like you have a qcow2 format device. This function will be called. We can put anything we want here. We can reopen a new device. We have a new format block device which has a cache created by myself. I can modify and control the cache after migration. Do you have any suggestions? Thanks. )
On Mon, Jun 30, 2014 at 10:35 AM, Paolo Bonzini <pbonz...@redhat.com> wrote: > Il 30/06/2014 16:03, Xiongzi Ge ha scritto: > > I tried. It invalidated the cache of the block device after migration. >> > > It didn't invalidate anything in the guest, and there's *NO WAY* > absolutely for QEMU to influence the cache in the guest. > > Again: all you can do is use O_DIRECT in the guest. > > > So, here, we can use a new cache for the block device after migration. >> > > I don't understand what you mean. > > > Is it right? I can implement a simple block driver in block/ directory. >> > > Probably not. > > Paolo >
