© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
bbfa235
(Get the code!)
as far as im aware the nvram file can contain data set by the guest os.
from the libvirt docs
“””
nvram
Some UEFI firmwares may want to use a non-volatile memory to store some variables. In the host, this is represented as a file and the absolute path to the file is stored in this element. Moreover, when the domain is started up libvirt copies so called master NVRAM store file defined in qemu.conf. If needed, the template attribute can be used to per domain override map of master NVRAM stores from the config file. Note, that for transient domains if the NVRAM file has been created by libvirt it is left behind and it is management application's responsibility to save and remove file (if needed to be persistent). Since 1.2.8
Since 8.5.0, it's possible for the element to have type attribute (accepts values file, block and network) in that case the NVRAM storage is described by a <source> sub-element with the same syntax as disk's source. See Hard drives, floppy disks, CDROMs.
Note: network backed NVRAM the variables are not instantiated from the template and it's user's responsibility to provide a valid NVRAM image.
This element supports a format attribute, which has the same semantics as the attribute of the same name for the <loader> element. Since 9.2.0 (QEMU only)
It is not valid to provide this element if the loader is marked as stateless.
“””
deleting this on rebuild may be ok. deleting this always could be a pretty major regression and is not something we should do with out carful discussion.
nova does not supprot stateless firemware todya. there is a request to supprot it going forward but today our uefi support is ment to be stateful and the nvram file should be preserved in general.