/qubes-issues

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

Backup restore of Qubes3.2 into Qubes4.0 attempts to create disp-$netvm VMs even if already present #3232

Open
qubesuser opened this Issue Oct 27, 2017 · 0 comments

Comments

Assignees
No one assigned
Labels
Projects
None yet
Milestone
  Release 4.0 updates
2 participants
@qubesuser @andrewdavidwong
@qubesuser

qubesuser commented Oct 27, 2017

Qubes OS version:

R4.0-rc2

Steps to reproduce the behavior:

  1. Restore a Qubes3.2 backup after already having restored another Qubes3.2 backup

Expected behavior:

If a disp-$netvm VM is already present, qvm-backup-restore just uses it and does not attempt to recreate it.

Actual behavior:

If a disp-$netvm VM is already present, qvm-backup-restore creates a new one renamed to avoid conflict.

General notes:

Also showing the disp-* VMs in the list of VMs to be restored with no explanation is extremely confusing.

I'm also not sure about this whole business of creating a dispvm for each netvm, although I can see the logic of it.

@andrewdavidwong andrewdavidwong added bug C: core labels Oct 28, 2017

@andrewdavidwong andrewdavidwong added this to the Release 4.0 milestone Oct 28, 2017

@andrewdavidwong andrewdavidwong modified the milestones: Release 4.0, Release 4.0 updates Mar 31, 2018

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment