On Fri, Nov 4, 2011 at 12:19 PM, DRAM Ninjas <[email protected]> wrote:
> Greetings, > > I noticed one of the git commits was for a read only mode for qcow2 > images. I'm rather excited about this feature, but I just wanted to double > check -- this doesn't actually change the outcome of simulation/emulation, > right? > > Say a workload wants to write some file to the filesystem and then read > back the data from the file at a later time, does using read only mode > still guarantee that it will read the correct value from disk? > > Yes. All updates are written separately in a temporary file. On a disk read first the temporary file is checked for most recent copy if not there then the original disk file is read. QEMU had this feature since QCOW2 but in 0.12 or later they changed few things and disallowed 'read only' mode with 'loadvm' (loading checkpoints). They still allow read-only mode but you have to boot the whole VM all the time. - Avadh > Thanks, > Paul > > _______________________________________________ > http://www.marss86.org > Marss86-Devel mailing list > [email protected] > https://www.cs.binghamton.edu/mailman/listinfo/marss86-devel > >
_______________________________________________ http://www.marss86.org Marss86-Devel mailing list [email protected] https://www.cs.binghamton.edu/mailman/listinfo/marss86-devel
