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:

When there are active video streams during migration, it is possible that the src-spice server will send to the client stream-related messages after sending MSG_MIGRATE. This should not happen. The src server may only send MSG_MIGRATE_DATA after MSG_MIGRATE.
As a result of this bug, the client forwarded a wrong message as MSG_MIGRATE_DATA to the destination server and the destination server aborted.

In the remote-viewer log you can find:
(remote-viewer:30911): GSpice-WARNING **: expected SPICE_MSG_MIGRATE_DATA, got 124

The destination server aborts with "bad message size" error in
"display_channel_handle_migrate_data"

How reproducible:

Play video during migration. Use a setting with high latency and limited bandwidth between the client and the servers.

Yonit, the bug is in POST, but I don't see reference to the patch/change. You may also want to devel_ack+?

Created attachment 738600 [details]
fix: destroy video streams before sending MIGRATE_DATA

patch was acked and pushed upstream.

(In reply to comment #1)
> Yonit, the bug is in POST, but I don't see reference to the patch/change.
> You may also want to devel_ack+?

I attached the fix. For the devel-ack, I think we should wait for pm-ack. However, I think it should also be proposed for 6.4z, but I don't have the permissions to do so.

Reproduced. I took me a couple more of the rounds and I didn't get a dump because of host configuration but the client exited with precisely the exit code specified by Marc-André.

(In reply to comment #4)
> Reproduced. I took me a couple more of the rounds and I didn't get a dump
> because of host configuration but the client exited with precisely the exit
> code specified by Marc-André.

by Yonit?

Yes, by Yonit.

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.

http://rhn.redhat.com/errata/RHBA-2013-1571.html