Bug 861332 - Properly reset usb channels after non-seamless migration
Summary: Properly reset usb channels after non-seamless migration
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: spice-gtk
Version: 6.3
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Christophe Fergeau
QA Contact: Desktop QE
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-09-28 08:00 UTC by Hans de Goede
Modified: 2013-02-21 08:49 UTC (History)
5 users (show)

Fixed In Version: spice-gtk-0.14-3.el6
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-02-21 08:49:17 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2013:0343 0 normal SHIPPED_LIVE spice-gtk bug fix and enhancement update 2013-02-20 20:53:54 UTC

Description Hans de Goede 2012-09-28 08:00:52 UTC
Once bug 861331 is fixed it will be possible to migrate vms with usb-redir devices without using seamless migration. Currently spice-gtk gets confused about the USB state after a non-seamless (switch-host or semi-seamless) migration. It thinks a device is still redirected, un-redirecting and redirecting it again won't restore vm access to the device.

I've posted 2 patches upstream fixing this:
http://lists.freedesktop.org/archives/spice-devel/2012-September/011033.html
http://lists.freedesktop.org/archives/spice-devel/2012-September/011034.html

I believe we should fix this for 6.4 too.

Comment 5 errata-xmlrpc 2013-02-21 08:49:17 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-0343.html


Note You need to log in before you can comment on or make changes to this bug.