Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.
Sign upDon't leak all VM config in backup of single VM. #2645
Comments
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
Show comment
Hide comment
marmarek
Feb 22, 2017
Member
This is a duplicate of #1747. Design goal of backup utility is to preserve data/configuration as closely as possible (including dependencies on other VMs, even if not directly included in backup).
|
This is a duplicate of #1747. Design goal of backup utility is to preserve data/configuration as closely as possible (including dependencies on other VMs, even if not directly included in backup). |
marmarek
closed this
Feb 22, 2017
marmarek
added
the
duplicate
label
Feb 22, 2017
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
jpouellet commentedFeb 22, 2017
Qubes OS version (e.g.,
R3.2):R3.2
Affected TemplateVMs (e.g.,
fedora-23, if applicable):dom0
Actual behavior:
Currently, the qubes.xml in a backup of a single VM includes the details of all your VMs.
A backup of just one VM (in this case idle-test):
includes info on all my VMs:
Expected behavior:
It would be nice if VM backups did not leak all that info.
Steps to reproduce the behavior:
Back up a single VM. Follow manual restore instructions to extract qubes.xml. Observe the contents.