Assuming a standard qubes 4.0.x install, just clone the VM each time you are making risky changes...before each change of course.*
The use of lvm thin pool makes clones essentially use zero storage other that the bits where they diverge from the original VM, where copy on write preserves the differences. Brendan * ok, technically...make the clone anytime *before* shutting down the vm after the risky change...but purposely cutting it that close has risks. -- 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 qubes-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/8f1c91d3-c6ae-4822-9e0c-5daa55d5c29d%40googlegroups.com.
