Bug 1283033 - The uefi vars nvram is not deleted after the vm has been
Summary: The uefi vars nvram is not deleted after the vm has been
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Virtualization Tools
Classification: Community
Component: virt-manager
Version: unspecified
Hardware: Unspecified
OS: Linux
unspecified
low
Target Milestone: ---
Assignee: Cole Robinson
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-11-18 04:47 UTC by Andrew Chen
Modified: 2017-03-06 23:13 UTC (History)
4 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2017-03-06 23:13:04 UTC
Embargoed:

Attachments (Terms of Use)

Description Andrew Chen 2015-11-18 04:47:18 UTC 
Description of problem:
The per-vm specific uefi vars nvram should be deleted when the vm is.
This should normally not cause any harm, but if a vm is created with the same name as a previously deleted vm, but with a incompatible uefi (e.g. different architecture), this could cause problems.

Version-Release number of selected component (if applicable):
libvirt 1.2.21
virt-manager 1.2.1

How reproducible:
Always

Steps to Reproduce:
1. Create a VM named generic
2. Delete the VM
3. ls /var/lib/libvirt/qemu/nvram

Actual results:
generic_VARS.fd still remains there

Expected results:
generic_VARS.fd is deleted

Additional info:
Arch Linux
Comment 1 Cole Robinson 2017-03-06 23:13:04 UTC 
We use the UNDEFINE_NVRAM flag at delete time, so I think that covers this nowadays
Note You need to log in before you can comment on or make changes to this bug.