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:
Vm failed to start on the target host but libvirt still keep the vm paused on the source host when do postcopy
Version-Release number of selected component (if applicable):
libvirt-8.5.0-5.el9.x86_64
qemu-kvm-7.0.0-11.el9.x86_64
How reproducible:
100%
Steps to Reproduce:
1.Do postcopy with a low postcopy speed(leave time to cancel postcopy):
# virsh migrate avocado-vt-vm1 qemu+ssh://*.com/system --live --p2p --verbose --bandwidth 10 --postcopy --timeout-postcopy --timeout 10 --postcopy-bandwidth 5
2.Open another terminal, change the ownership of vm's disk to 'root:root':
#chown root:root /var/lib/libvirt/images/nfs/ovmf.qcow2
3.The migration in step 1 failed because the guest can not run on the target host:
Migration: [ 1 %]error: internal error: unable to execute QEMU command 'cont': Could not open '/var/lib/libvirt/images/nfs/ovmf.qcow2': Permission denied
4.Check the guest status on both source and target:
source host:
#virsh list
Id Name State
-------------------------------
5 avocado-vt-vm1 paused
target host:
#virsh list
no output
5.Do migration again:
# virsh migrate avocado-vt-vm1 qemu+ssh://*.com/system --live --p2p --verbose --bandwidth 10 --postcopy --timeout-postcopy --timeout 10 --postcopy-bandwidth 5
error: Requested operation is not valid: another migration job is already running for domain 'avocado-vt-vm1'
Actual results:
Vm failed to start on the target host but libvirt still keep the vm paused on the source host when do postcopy
Expected results:
Libvirt should keep the vm on the source running if guest failed to start on the target host.
Additional info:
Currently when Finish phase on the destination fails, the source is unable to
see that the failure happened when the CPUs where not running yet and it is
safe to resume the domain. So the only thing it can do is to keep the domain
paused.
The solution would be non-trivial though, as our API for Finish phase is
stupid and only returns NULL...
A WIP implementation of the new Finish API and its usage to fix this bug is at
https://gitlab.com/jirkade/libvirt/-/commits/migrate-finish
But actually fixing this will need more time as the fix does not work with
current QEMU. So we will most likely need some changes there as well and/or
changes in the libvirt fixes.
Comment 4RHEL Program Management
2023-09-22 17:31:48 UTC
Issue migration from Bugzilla to Jira is in process at this time. This will be the last message in Jira copied from the Bugzilla bug.
Comment 5RHEL Program Management
2023-09-22 17:36:55 UTC
This BZ has been automatically migrated to the issues.redhat.com Red Hat Issue Tracker. All future work related to this report will be managed there.
Due to differences in account names between systems, some fields were not replicated. Be sure to add yourself to Jira issue's "Watchers" field to continue receiving updates and add others to the "Need Info From" field to continue requesting information.
To find the migrated issue, look in the "Links" section for a direct link to the new issue location. The issue key will have an icon of 2 footprints next to it, and begin with "RHEL-" followed by an integer. You can also find this issue by visiting https://issues.redhat.com/issues/?jql= and searching the "Bugzilla Bug" field for this BZ's number, e.g. a search like:
"Bugzilla Bug" = 1234567
In the event you have trouble locating or viewing this issue, you can file an issue by sending mail to rh-issues. You can also visit https://access.redhat.com/articles/7032570 for general account information.