![]() ![]() ![]() Then you have all those other files which may or may not be important like memory files, lock files, more.Ĭlone a machine. Copying only a diskfile is possible, but did you copy all the diskfiles if there is one or more snapshots? BTW - Is one reason to merge snapshots ASAP when they’re no longer needed… many times snapshots won’t be recoverable or read in a recovery of any type. ![]() Same applies to all virtualization technologies, there is no difference for example between VBox and KVM… The directory will contain the necessary files plus possibly some unnecessary to run. What if I need to copy directly to a USB stick or external hard disk? Wouldn’t it be highly insecure to access any external storage as root?Īnd for some reason I feel modifying ownerships and/or permissions would somewhat break virt-manager (not to mention some security flaws?) What would be a “best practice” to be able to backup VM? Or is it that the only one supposed to do any KVM related stuff is root indeed? So by default it doesn’t allow to copy the VM as normal user.Īre such ownership and permissions certainly default behavior of virt-manager? So inside is the VM file, but it was created with permissions “root:root -rw-”. Of course I manually created the directory beforehand. Thing is, for almost obvious reasons, I created the VM in a different storage pool than the default one: a directory called “VirtualMachines” just inside home directory. Reviewing some past threads I read one common way to backup a VM is just copying the entire VM file similar to VirtualBox except that here one copies an entire directory instead of a single file. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |