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.
Description of problem:
No ABI check for /memoryBacking/[source|access|allocation] in guest xml
Version-Release number of selected component (if applicable):
libvirt-3.2.0-4.el7.x86_64
How reproducible:
100%
Steps to Reproduce:
1.prepare a guest with xml like this:
<memoryBacking>
<source type='file'/>
<access mode='private'/>
<allocation mode='ondemand'/>
</memoryBacking>
2.start guest and save this guest:
# virsh start r7
Domain r7 started
# virsh managedsave r7
Domain r7 state saved by libvirt
3. use save-image-edit to change the source type or access mode or allocation mode:
# virsh save-image-edit /var/lib/libvirt/qemu/save/r7.save
change to:
<memoryBacking>
<source type='anonymous'/>
<access mode='private'/>
</memoryBacking>
State file /var/lib/libvirt/qemu/save/r7.save edited.
4. try to restore guest:
# virsh start r7
error: Failed to start domain r7
error: operation failed: job: unexpectedly failed
5. check guest log
2017-05-12T10:10:30.322768Z qemu-kvm: Unknown ramblock "/objects/ram-node0", cannot accept migration
2017-05-12T10:10:30.322799Z qemu-kvm: error while loading state for instance 0x0 of device 'ram'
2017-05-12T10:10:30.323204Z qemu-kvm: load of migration failed: Invalid argument
Actual results:
No ABI check for /memoryBacking/[source|access|allocation] in guest xml
Expected results:
Libvirt should not allow this change since it will effect the guest resource, and won't pass qemu ABI
Additional info:
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/RHEA-2017:1846
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/RHEA-2017:1846
Description of problem: No ABI check for /memoryBacking/[source|access|allocation] in guest xml Version-Release number of selected component (if applicable): libvirt-3.2.0-4.el7.x86_64 How reproducible: 100% Steps to Reproduce: 1.prepare a guest with xml like this: <memoryBacking> <source type='file'/> <access mode='private'/> <allocation mode='ondemand'/> </memoryBacking> 2.start guest and save this guest: # virsh start r7 Domain r7 started # virsh managedsave r7 Domain r7 state saved by libvirt 3. use save-image-edit to change the source type or access mode or allocation mode: # virsh save-image-edit /var/lib/libvirt/qemu/save/r7.save change to: <memoryBacking> <source type='anonymous'/> <access mode='private'/> </memoryBacking> State file /var/lib/libvirt/qemu/save/r7.save edited. 4. try to restore guest: # virsh start r7 error: Failed to start domain r7 error: operation failed: job: unexpectedly failed 5. check guest log 2017-05-12T10:10:30.322768Z qemu-kvm: Unknown ramblock "/objects/ram-node0", cannot accept migration 2017-05-12T10:10:30.322799Z qemu-kvm: error while loading state for instance 0x0 of device 'ram' 2017-05-12T10:10:30.323204Z qemu-kvm: load of migration failed: Invalid argument Actual results: No ABI check for /memoryBacking/[source|access|allocation] in guest xml Expected results: Libvirt should not allow this change since it will effect the guest resource, and won't pass qemu ABI Additional info: