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 - Restored vm will not start due to uuid already existing? #3144
Comments
andrewdavidwong
added
bug
C: core
labels
Oct 4, 2017
andrewdavidwong
added this to the Release 4.0 milestone
Oct 4, 2017
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
marmarek
Oct 6, 2017
Member
Do you see the VM on virsh -c xen:/// list --all after removing with qvm-remove?
|
Do you see the VM on |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
mannp
commented
Oct 7, 2017
|
Its giving me a 'command not found' executing that in the dom0 command line. |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
marmarek
Oct 16, 2017
Member
Install libvirt-client package in dom0 (sudo qubes-dom0-update libvirt-client) and try again.
|
Install |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
mannp
Oct 16, 2017
@marmarek I have reinstalled again so that I could continue using qubes, so can no longer debug this item.
mannp
commented
Oct 16, 2017
|
@marmarek I have reinstalled again so that I could continue using qubes, so can no longer debug this item. |
mannp commentedOct 3, 2017
•
edited
Edited 1 time
-
mannp
edited Oct 3, 2017 (most recent)
Qubes OS version: 4rc1
Affected TemplateVMs: fedora-25
Steps to reproduce the behavior:
Restore a previously backed up vm and try to start it.
Expected behavior:
vm should not already have a uuid set as it was deleted after backup.
Actual behavior:
qvm-remove does not appear to fully delete a vm from the system, leaving crud that stops a subsequent restore starting.
General notes:
I also note that qvm-remove -v does not add any verbosity? gives no output as without it.
Related issues: