Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
+++ This bug was initially created as a clone of Bug #1679018 +++
Description of problem:
RuntimeError: Path does not exist: /var/lib/libvirt/qemu/nvram/test_VARS.fd
Version-Release number of selected component (if applicable):
virt-install-2.0.0-4.el8.noarch
How reproducible:
100%
Steps to Reproduce:
1. Create a uefi guest by '--import' and '--noreboot'.
# virt-install --name test --memory 1024 --disk /var/lib/libvirt/images/test.img,size=1 --import --boot uefi --noreboot
2. Clone the guest.
# virt-clone -o test --auto-clone
Actual results:
RuntimeError: Path does not exist: /var/lib/libvirt/qemu/nvram/test_VARS.fd
Expected results:
virt-clone should success.
Additional info:
'/var/lib/libvirt/qemu/nvram/test_VARS.fd' is created automatically when vm first boots up, so if the file doesn't exist,
virt-clone should not fail.
I can reproduce this issue with package:
virt-manager-1.5.0-1.el7.noarch
Then try to verify this bug with new build:
virt-manager-1.5.0-3.el7.noarch
virt-install-1.5.0-3.el7.noarch
libvirt-4.5.0-12.el7.x86_64
qemu-kvm-rhev-2.12.0-26.el7.x86_64
libvirt-python-4.5.0-1.el7.x86_64
Steps:
1.Create a uefi guest but nvram file doesn't exist by '-import' and 'noreboot'
#virt-install --name test --memory 1024 --disk /var/lib/libvirt/images/test.img,size=1 --import --boot uefi --noreboot
Starting install...
Allocating 'test.img' | 1.0 GB 00:01
Domain creation completed.
1.1 The uefi guest can be created successfully with xml info:'<nvram>/var/lib/libvirt/qemu/nvram/test_VARS.fd</nvram>'.
1.2 Check path(/var/lib/libvirt/qemu/nvram/) without file(test_VARS.fd)
# ls /var/lib/libvirt/qemu/nvram/test_VARS.fd
ls: cannot access /var/lib/libvirt/qemu/nvram/test_VARS.fd: No such file or directory
Result:the file does not exist.
2.Check the guest can be cloned successfully.
# virt-clone -o test --auto-clone
Allocating 'test-clone.img' | 1.0 GB 00:00
Clone 'test-clone' created successfully.
#virsh dumpxml test-clone | grep nvram
<nvram>/var/lib/libvirt/qemu/nvram/test-clone_VARS.fd</nvram>
#ll /var/lib/libvirt/qemu/nvram/test-clone_VARS.fd
ls: cannot access /var/lib/libvirt/qemu/nvram/test-clone_VARS.fd: No such file or directory
Result: virt-clone finishes successfully without flie 'test_VARS.fd' and the new guest can start successfully.
I move this bug from ON_QA to VERIFIED based on above testing.
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
https://access.redhat.com/errata/RHBA-2019:2232