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 up4rc1 - qvm-backup-restore restore borks entire system on one vm restore #3127
Comments
mannp
changed the title from
qvm-backup-restore restore borks entire system on one vm restore
to
4rc1 - qvm-backup-restore restore borks entire system on one vm restore
Sep 27, 2017
andrewdavidwong
added
bug
C: core
labels
Sep 29, 2017
andrewdavidwong
added this to the Release 4.0 milestone
Sep 29, 2017
marmarek
added
the
duplicate
label
Sep 29, 2017
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
Show comment
Hide comment
|
This looks like another instance of #3115 |
marmarek
closed this
Sep 29, 2017
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
mannp commentedSep 27, 2017
•
edited
Edited 1 time
-
mannp
edited Sep 27, 2017 (most recent)
Qubes OS version: R4rc1
Affected TemplateVMs: fedora-25
Steps to reproduce the behavior:
Have a working system and backup all vms with qvm-backup, encrypted.
Make sure the backup is good.
Restore all system including dom0 or just individual vms, with everything else excluded and the result is the same, a borked system.
I have taken photos again as I cannot copy and paste from the machine as nothing works at the moment.
http://safe.dsh.re/download/91162f31-b9a7-46e2-9a0c-de5e6e8a3ef0
Expected behavior:
Restoring any and all VM's should not be allowed to bork the system in a way to stop qubesd from starting.
Actual behavior:
FW and Net VM's as well as qubesd will not start.
General notes:
It appears to be another erro with qubes.xml but I have wasted a day trying to solve and cannot.
Related issues: