PS, this is where the qcow extension came from... qemu copy-on-write. :-) > Snapshots take the image at the point of checkpointing and freeze it. Any > further writes to the image are handled using a copy-on-write approach. > > The state of the disk in your example should be nearly identical. The only > thing that should change is system logs and other files that are modified > on every boot. > > Tyler > >> This is probably a silly question since I don't have an in-depth >> knowledge >> of how QEMU checkpoints work, but when I create a checkpoint, is the >> original image changed? I know the qcow2 file is modified, but is the >> actual image content of the non-snapshot portion changed? >> >> In other words, if I boot up a some qcow2 file, call >> checkpoint_and_shutdown() and then boot up the same qcow2 file (without >> any >> -loadvm option) -- is the state of the disk identical between the two >> boots? >> >> 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 >
_______________________________________________ http://www.marss86.org Marss86-Devel mailing list [email protected] https://www.cs.binghamton.edu/mailman/listinfo/marss86-devel
