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:

If a user or QMP client enter a bad syntax for the migrate command in QMP/HMP, then the migrate command will never succeed from that point on.

Version-Release number of selected component (if applicable): qemu-kvm-1.5.3-30.el7


How reproducible:


Steps to Reproduce:
1. Start a source and a target guest for migration. For example:

Source guest: qemu-kvm [...] -monitor stdio
Target guest: qemu-kvm [...] -monitor stdio -incoming tcp:0:4444

2. On the source guest's monitor, type a bad migrate command:

(qemu) migrate ;0:4444
migrate: Parameter 'uri' expects a valid migration protocol

3. Now correct the syntax and try again:

(qemu) migrate tcp:0:4444
migrate: There's a migration process in progress

Actual results:

The migrate command still fails and will always fail after the first failure.

Expected results:

The migrate command works with the correct syntax.

Fix posted upstream. Will post downstream as soon as it's applied.

This is uptream commit c950114286ea358a93ce632db0421945e1008395, should be a clean backport, but I missed the downstream deadline :(

Now, this one doesn't seem so serious to request an exception or block flag as libvirt would have to be buggy to emit a bad syntax...

Deferring to RHEL7.1.