-
-
Notifications
You must be signed in to change notification settings - Fork 50
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[R4.0 RC2] qvm-backup-restore or qvm-backup error #3211
Comments
Thanks! I'll test the proposed fix later to see if it works. In my case it was Qubes 4.0 RC2 backups failing to be restored in the same RC2 machine, but it looks like the same issue and error. Earlier today I had only very minor problems restring 3.2 backups in 4.0 RC2 - application shortcuts needed to be refreshed and virt_mode defaults to pv, but the restored VMs work perfectly. My current issue is that it's very hard to know how much free space I have left in 4.0, but that's a separate issue 😺 |
For the record, after implementing the quick fix, we were able to
successfully restore rc1 to rc1 and rc2, and rc2 to rc2.
On Fri, Oct 27, 2017 at 5:11 AM na-- ***@***.***> wrote:
Thank, I'll test the proposed fix later to see if it works. In my case it
was Qubes 4.0 RC2 backups failing to be restored in the same RC2 machine,
but it looks like the same issue and error.
Earlier today I had only very minor problems restring 3.2 backups in 4.0
RC2 - application shortcuts needed to be refreshed and virt_mode defaults
to pv, but the restored VMs work perfectly. My current issue is that it's
very hard to know how much free space I have left in 4.0, but that's a
separate issue 😺
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#3211 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AOvthvPviu1U2RxcBAEsTK4U3noib14kks5swZ0jgaJpZM4QGm-K>
.
--
Sent from my Commodore64
|
I encountered this error when trying --verify-only on a new backup, and unsuccessfully tried @jwoytek workaround like this:
This yields the same error. I then tried commenting-out the first "vm.label =" line and got: I successfully restored an R3.2 backup a few days ago, but currently I have to assume R4 qvm-backup is broken and that the new archive file is bad, so I am looking for a simple alternative. |
The backup archive produced by R4 qvm-backup is ok. The restore code is broken. I'm working on this right now. |
See the commit I've just pushed (automatically linked above). |
@marmarek Maybe there is a different issue related to file paths, as I'm still getting the AttributeError shown above (KeyError is gone). |
Automated announcement from builder-github The package
|
Automated announcement from builder-github The package
|
Automated announcement from builder-github The package
|
Automated announcement from builder-github The package
|
Automated announcement from builder-github The package
|
Automated announcement from builder-github The package
|
Automated announcement from builder-github The package
|
Automated announcement from builder-github The package
|
Automated announcement from builder-github The package
Or update dom0 via Qubes Manager. |
Automated announcement from builder-github The package
|
Automated announcement from builder-github The package
|
Automated announcement from builder-github The package
|
Does it still apply? |
Your original commit fixed the issue for me and, if memory serves, I've restored backups after that with no problems. So I'm closing this and if @opposablebrain or someone else still has problems, creating a new issue would probably be better. |
Qubes OS version:
R4.0 RC2
Affected TemplateVMs:
none (dom0 issue)
Steps to reproduce the behavior:
Create a backup with
qvm-backup --compress /some/file some-vm
and then try to restore from it viaqvm-backup-restore /some/file
Expected behavior:
Successful restore of the backed up VM.
Actual behavior:
The following error is displayed:
General notes:
I'm not even sure why the
KeyError
isred
, since the backup contained only a single VM - the defaultdebian-8
template that has a black label...Related issues:
None that I could find
The text was updated successfully, but these errors were encountered: