Sks
October 31, 2024, 8:02am
1
I tried to restore some vm with the paranoid mode in fedora and it would not work. The error has something to do with a missing package `qvm-backup-restore tool missing in fedora 40-xfce template, install qubes-core-admin-client there. Now this is pretty self explanatory but shouldn’t this be already installed? And how do i install it becuase i have no idea how fedora works.
sudo dnf install qubes-core-admin-client
Maybe you’ll have an issue with policies as well and you’ll need to add them manually:
opened 10:44PM - 03 Sep 23 UTC
T: bug
C: core
P: major
needs diagnosis
affects-4.1
affects-4.2
### Qubes OS release
4.1.2
### Brief summary
So I'm trying to restore… my backup done on 4.1.2 to a machine also running 4.1.2 and doing so in "plan-b" mode with the following command:
`qvm-backup-restore --plan-b --rename-conflicting -d sys-usb /path/to/backup`
I verified the backup and it checks out, but running the above command will fail with the same error reported [here](https://forum.qubes-os.org/t/how-do-you-use-qvm-backup-restore-paranoid-mode/12221) a year ago, i.e. due to misconfigured policy.
Using the workaround in the above link I was able to restore the qubes with my data, but it still threw some errors:
`Error adding tag created-by-dom0 to vmname: Got empty response from qubesd.`
for each restored qube. And after closing the xterm at the end of the process in the dom0 terminal I got:
`qubesadmin.backup.dispvm: Restored domain vmname was not tagged with restored-from-backup-* tag`
for each restored qube.
Without the workaround it did create the "restored" qubes, but they didn't actually contain my user data, but had private images like a newly created VM. A popup notification appeared saying `Denied: admin.vm.tag.Get+created-by-dom0 from disp-backup-restore to vmname`
and the program exited with error code 1 and `qvm-backup-restore: error: Service call error: Request refused`.
With the workaround in the link I have my data but I don't know what consequences the missing tag will have; please advise if the missing tag will mess something up later on.
### Steps to reproduce
Run command as above and optionally use workaround.
### Expected behavior
It normally restores the qubes without throwing errors.
### Actual behavior
Without workaround: creates new qubes that have the correct name, but don't actually contain the user data of the backup.
With workaround: qubes seem to be restored with data, but some errors about tags are still thrown.
Sks
October 31, 2024, 11:47am
4
How could i add the rules? It is not clear.
Thanks
You can open Qubes Policy Editor GUI tool and create new policy file there with the name e.g. 30-user
.
Then add policies there and save the file.
1 Like
Sks
October 31, 2024, 2:45pm
6
It still fails even after adding the policy error:
What could this error mean
Is USB-dvm a named disposable that is used as sys-usb and not a disposable template for sys-usb?
Do you have the USB-dvm qube running and the /run/media/user/caf2… directory with your backup present?
Sks
October 31, 2024, 7:29pm
8
Yes sir it is based on default-dvm based on fedora. And the directory exists.
Specify the full path to the backup file e.g. /run/media/user/caf2…/qubes-backup-X
.
1 Like
Sks
November 1, 2024, 12:50pm
10
It worked, yeah i forgot to put the backup in the command thanks.