/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

Renaming vm from secondary drive puts new vm on first drive. #4145

Open
qubenix opened this Issue Jul 25, 2018 · 0 comments

Comments

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

qubenix commented Jul 25, 2018

Qubes OS version:

R4.0

Affected component(s):

Steps to reproduce the behavior:

  1. Set up a secondary drive: https://www.qubes-os.org/doc/secondary-storage/.

  2. Clone a vm to the new pool with qvm-clone -P NEWPOOL VMNAME NEWVM.

  3. Rename the new vm, residing in the new pool, via Qubes Manager settings.

Expected behavior:

Renamed vm resides in same spot as original.

Actual behavior:

New vm will end up in /dev/qubes_dom0/ instead of where it originated.

General notes:

Related issues:

@andrewdavidwong andrewdavidwong added bug C: other labels Jul 26, 2018

@andrewdavidwong andrewdavidwong added this to the Release 4.0 updates milestone Jul 26, 2018

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