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 622278 - SPICE: Client connected to win7-X64 Guest crashed on migration.
Summary: SPICE: Client connected to win7-X64 Guest crashed on migration.
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: spice-server
Version: 6.0
Hardware: All
OS: Windows
high
high
Target Milestone: rc
: ---
Assignee: Uri Lublin
QA Contact: Desktop QE
URL:
Whiteboard: VDI
Depends On: 599496
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-08-08 15:04 UTC by Uri Lublin
Modified: 2015-09-28 02:18 UTC (History)
13 users (show)

Fixed In Version: spice-server-0.7.2-2.el6
Doc Type: Bug Fix
Doc Text:
The palette cache was not always synchronized between client and server following live migration of a virtual machine with multiple monitors. The client side palette cache was not cleaned after migration, which caused the client to terminate unexpectedly. The target server now sends the "RESET" instruction to the client for all monitors, so this crash no longer occurs.
Clone Of: 599496
Environment:
Last Closed: 2011-05-19 14:07:33 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2011:0705 0 normal SHIPPED_LIVE spice-server bug fix and enhancement update 2011-05-18 18:10:05 UTC

Comment 3 Uri Lublin 2011-01-31 17:05:18 UTC 
upstream commit ae1de849acd1e58772dc3f318324ed936ff5f21c
Comment 12 Laura Bailey 2011-04-20 06:08:04 UTC 
    Technical note added. If any revisions are required, please edit the "Technical Notes" field
    accordingly. All revisions will be proofread by the Engineering Content Services team.
    
    New Contents:
The palette cache was not always synchronized between client and server following live migration of a virtual machine with multiple monitors. The client side palette cache was not cleaned after migration, which caused the client to terminate unexpectedly. The target server now sends the "RESET" instruction to the client for all monitors, so this crash no longer occurs.
Comment 13 Lubos Kocman 2011-04-20 09:20:36 UTC 
Verfied on spice-client-0.8.0-2.el6.x86_64

Seems like rhevm/libvirt/vdsm is not passing host-subject to controler => spice-client to the migration. But this is an unrelated bug and needs to be reported separately.

Spice-client does not crash during migration with two monitors. But it's disconnected as it does get new host subject.

re-connecting to the guest after migration works fine. Except small redraw issue.

So seems like issue with palette clean up is fixed.
Comment 14 errata-xmlrpc 2011-05-19 14:07:33 UTC 
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.

http://rhn.redhat.com/errata/RHBA-2011-0705.html
Note You need to log in before you can comment on or make changes to this bug.