Bug 1283033 - The uefi vars nvram is not deleted after the vm has been
The uefi vars nvram is not deleted after the vm has been
Status: CLOSED CURRENTRELEASE
Product: Virtualization Tools
Classification: Community
Component: virt-manager (Show other bugs)
unspecified
Unspecified Linux
unspecified Severity low
: ---
: ---
Assigned To: Cole Robinson
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2015-11-17 23:47 EST by Andrew Chen
Modified: 2017-03-06 18:13 EST (History)
4 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2017-03-06 18:13:04 EST
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Andrew Chen 2015-11-17 23:47:18 EST
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 18:13:04 EST
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.