To ask more specific, do you guys don't use snapshots because you don't need them for your use cases or do you have negative experiences and advice against using them? But a simple snapshot would save you some time because only blocks that are changing have to be written to disk not the whole file itself. To copy the whole qcow2 file may be a good choice for regular backups. ![]() Therefor it should not matter whether EFI or BIOS is being used either on the virtualization host or in the guest. It's just like a copy on write operation or at least it should be. Could you explain that in some more detail? In my understanding a snapshot is just a point in time where changes to the virtual disk are written to a new file. So I guess there is still a point for using snapshots.Ĭhristian, you mentioned that snapshots don't work with EFI based BIOS. I guess I could not solve this easily by creating a new VM each time an update needs to be applied because I would have to migrate the data as well each time. If something goes wrong I jump back to the snapshot and are up and running again. Today I'd like to take a snapshot from a production VM each time before I apply updates/patches to it. ![]() Red Hat JBoss Enterprise Application Platformįor testing purposes I think I could go the same way as Siem and just create new VMs from templates.Red Hat Advanced Cluster Management for Kubernetes.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |