Anthony Liguori <anth...@codemonkey.ws> wrote: > > Michael basically was trying to avoid having a VM's state change after > you stopped the guest. > > With something like cache=unsafe that periodically flushes based on a > timer (I think), you want to make sure that that doesn't happen after > stop occurs.
Even then, we want to have "qcow2_flush_dirty_buffer_to_disk()" or whatever is going to be called the method. Doing a full "drop all cache" and "reread" it is using a cannon to fight flies IMHO. Especially because there are "lots" of uses of stop, and only a minority of them want this flushed to disk (if ever). My recount of mst problems were with networking (vhost) than something touch the guest image while VM is stopped. This is not the case here, as we are not doing anything with the guest memory, no? Later, Juan.
