Hello everyone, there is documentation about 'root-cow.img' online [1], but nothing about 'private-cow.img'. Am I right to assume that the 'private.img' is the writable part the VM sees, with the changes the VM wrote saved on 'private-cow.img', which is rotated with 'private-img.old.img' after each VM restart for rollback possibility? This is how I understand 'root-cow.img' at least.
If this is correct, and I backup only 'private.img' of a running VM, I would miss on all changes the VM did since its current start? Would 'private.img' be enough when the VM is shut down? It does sound like 'root.img' need one of the two .old as "binary patches" in any case. And just to be sure: 'root-cow.img' and 'volatile.img' shouldn't contain any backup-worthy data of a VM, right? Thank you, Stickstoff [1] https://www.qubes-os.org/doc/template-implementation/ -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/d8f35e70-4900-62fe-e4ae-2ba4c654d7b0%40posteo.de. For more options, visit https://groups.google.com/d/optout.
signature.asc
Description: OpenPGP digital signature
