Very interesting, thank you Mike for reporting that.
I never drove this through virt-mananger, but I've seen simlar through
the commandline.
I happened to get it working via:
$ virsh undefine --nvram testguest
Now maybe the cancel/delete from virt-manager does not do so.
Could you try the following:
1. if the guest is still defined after that cancel undefine it in commandline
with
$ virsh undefine --nvram TEST123
Check if that did remove the file
2. If the cancel did remove the definition please try to find a way to abort it
hard. We need to
find out if virt-manager needs to call differently or if in your case the
"undefine including
nvram" fails to remove the file.
Once you aborted do the undefine as mentioned above and check if the file
was removed.
If the file was not removed we might also want to check dmesg for
apparmor Denies.
Also there is this code in virt-manager:
if force:
flags |= getattr(libvirt,
"VIR_DOMAIN_UNDEFINE_SNAPSHOTS_METADATA", 0)
flags |= getattr(libvirt, "VIR_DOMAIN_UNDEFINE_MANAGED_SAVE", 0)
if (self.get_xmlobj().os.loader_ro is True and
self.get_xmlobj().os.loader_type == "pflash"):
flags |= getattr(libvirt, "VIR_DOMAIN_UNDEFINE_NVRAM", 0)
try:
self._backend.undefineFlags(flags)
That reads like the right thing, but it depends on the force flag.
Not sure if that is set on the path you trigger.
** Changed in: virt-manager (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1701344
Title:
virt-manager fails to delete
/var/lib/libvirt/qemu/nvram/VMName_VARS.fd after installation is
cancelled.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/virt-manager/+bug/1701344/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
