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.
Bug 866929 - seamless migration: assert at destination side after migration
Summary: seamless migration: assert at destination side after migration
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: spice-server
Version: 6.4
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: rc
: ---
Assignee: Yonit Halperin
QA Contact: Desktop QE
URL:
Whiteboard:
Depends On:
Blocks: 881827
TreeView+ depends on / blocked
 
Reported: 2012-10-16 10:49 UTC by Yonit Halperin
Modified: 2013-07-03 12:07 UTC (History)
8 users (show)

Fixed In Version: spice-server-0.12.0-5.el6
Doc Type: Bug Fix
Doc Text:
No documentation is needed. This bug is related to a new feature in RHEL-6.4, spice seamless migration. It was found and fixed during RHEL-6.4 development phase. Cause: Consequence: Fix: Result:
Clone Of:
Environment:
Last Closed: 2013-02-21 10:03:32 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2013:0529 0 normal SHIPPED_LIVE spice-server bug fix and enhancement update 2013-02-20 21:51:04 UTC

Description Yonit Halperin 2012-10-16 10:49:40 UTC 
Description of problem:

qemu sometimes aborts after migration of Windows 7 guest, when the migration is executed during rebooting the guest.

More specifically:
When executing migration, after the vm migration has completed, but before spice display channel migration completed (i.e., the server display channel hasn't yet received from the client the migration data required for restoring its state).
If:(1) The qxl command ring is not empty, and (2) reset of qxl occurs,
the destination qemu will abort due to 
assert(!spice_display_running || SPICE_RING_IS_EMPTY(&ram->cmd_ring));
(see the stack trace below)

It is more easy to reproduce this over WAN, because then spice seamless migration data transfer takes longer, and also, the cmd ring is more likely to be occupied with commands.

The origin of this bug can also cause other inconsistencies, when instead of reboot, there are resolution changes during migration.

#0  0x00007ffff41ec285 in raise () from /lib64/libc.so.6
#1  0x00007ffff41edb9b in abort () from /lib64/libc.so.6
#2  0x00007ffff41e4e9e in __assert_fail_base () from /lib64/libc.so.6
#3  0x00007ffff41e4f42 in __assert_fail () from /lib64/libc.so.6
#4  0x0000000000593028 in qxl_check_state (d=<optimized out>) at /home/tlv/yhalperi/projects/redhat/qemu/hw/qxl.c:911
#5  qxl_check_state (d=<optimized out>) at /home/tlv/yhalperi/projects/redhat/qemu/hw/qxl.c:906
#6  0x0000000000593045 in qxl_reset_state (d=0x1557530) at /home/tlv/yhalperi/projects/redhat/qemu/hw/qxl.c:919
#7  0x0000000000594910 in qxl_hard_reset (d=0x1557530, loadvm=0) at /home/tlv/yhalperi/projects/redhat/qemu/hw/qxl.c:955
#8  0x000000000041253d in qemu_system_reset () at /home/tlv/yhalperi/projects/redhat/qemu/vl.c:3343
#9  0x0000000000430cc1 in qemu_kvm_system_reset () at /home/tlv/yhalperi/projects/redhat/qemu/qemu-kvm.c:1978
#10 kvm_main_loop () at /home/tlv/yhalperi/projects/redhat/qemu/qemu-kvm.c:2258
#11 0x000000000040c6aa in main_loop () at /home/tlv/yhalperi/projects/redhat/qemu/vl.c:4202
#12 main (argc=<optimized out>, argv=<optimized out>, envp=<optimized out>) at /home/tlv/yhalperi/projects/redhat/qemu/vl.c:6430
Comment 1 Yonit Halperin 2012-11-12 17:27:02 UTC 
fixed it upstream
Comment 6 errata-xmlrpc 2013-02-21 10:03:32 UTC 
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-0529.html
Note You need to log in before you can comment on or make changes to this bug.