Bug 1283033

Summary:	The uefi vars nvram is not deleted after the vm has been
Product:	[Community] Virtualization Tools	Reporter:	Andrew Chen <andrew.chuanye.chen>
Component:	virt-manager	Assignee:	Cole Robinson <crobinso>
Status:	CLOSED CURRENTRELEASE	QA Contact:
Severity:	low	Docs Contact:
Priority:	unspecified
Version:	unspecified	CC:	berrange, crobinso, gscrivan, rbalakri
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2017-03-06 23:13:04 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

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