FS#50586 - [virt-manager] Cloning a UEFI machine doesn't clone/copy the NVRAM EFIVARS.

Attached to Project: Community Packages
Opened by Tobias Dahlberg (TobiasD) - Tuesday, 30 August 2016, 09:48 GMT
Last edited by Christian Rebischke (Shibumi) - Wednesday, 03 January 2018, 19:37 GMT
Task Type Bug Report
Category Upstream Bugs
Status Closed
Assigned To Christian Rebischke (Shibumi)
Architecture All
Severity Medium
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:
Cloning a UEFI machine in virt-manager doesn't clone/copy the NVRAM EFIVARS for the cloned machine.
The OVMF EFIVARS aren't copied and renamed when you clone a virtual machine. The cloned machine refers to the EFIVARS file of the original machine.
This creates problems once the machines start writing to the NVRAM. The NVRAM can (will, inevitably) become corrupt and machines unbootable.
The cloning should clone the NVRAM just like it clones the storage devices.

packages:
* community/virt-manager
* community/libvirt
* extra/ovmf

Steps to reproduce:
Clone a virtual machine (that has OVMF firmware) in virt-manager.

Tested in a test environment.
Example XML, the original (name=centos01):
<domain type='kvm'>
<os>
<loader readonly='yes' type='pflash'>/usr/share/ovmf/x64/ovmf_x64.bin</loader>
<nvram>/var/lib/libvirt/qemu/nvram/centos01_VARS.fd</nvram>
</os>
...
Example XML, the clone (name=centos02):
<domain type='kvm'>
<os>
<loader readonly='yes' type='pflash'>/usr/share/ovmf/x64/ovmf_x64.bin</loader>
<nvram>/var/lib/libvirt/qemu/nvram/centos01_VARS.fd</nvram>
</os>
...
This task depends upon

Closed by  Christian Rebischke (Shibumi)
Wednesday, 03 January 2018, 19:37 GMT
Reason for closing:  No response
Comment by Christian Rebischke (Shibumi) - Thursday, 14 December 2017, 15:36 GMT
Hello,
I am the new maintainer. Is this issue still a problem? If I don't get any response I'll close this bug in 1 week.
It's already over a year old.

Loading...