Red Hat Bugzilla – Bug 894020
PRD32 - [RFE] spice seamless migration support in win client
Last modified: 2016-02-10 15:21:06 EST
Description of feature:
When a VM migrates from one host to another destination host, an essential spice session data should be migrated as well. Then, the server-client session can be restored on the destination side, without losing any mandatory information.
(a) Data that has been in-flight between the server and the client during migration is not lost. As a result, ongoing usb, vdagent, and smartcard transfers are not aborted, and can continue smoothly after migration.
(b) Without this feature, the primary display surface and other off-screen surfaces that were already sent to the client, have to be resent to the client after migration has completed. With Seamless migration, this data is not resent. Thus, the performance of the spice session is less affected by migration, and as a result the migration is less noticeable by the user.
affected components: spice-server, spice-gtk, spice-protocol, qemu-kvm, libvirt
If one of the components does not support seamless migration, we fallback to the old migration.
back to RFEs for consistency with other spice rfe bugs
This bug is currently attached to errata RHEA-2013:14491. If this change is not to be documented in the text for this errata please either remove it from the errata, set the requires_doc_text flag to minus (-), or leave a "Doc Text" value of "--no tech note required" if you do not have permission to alter the flag.
Otherwise to aid in the development of relevant and accurate release documentation, please fill out the "Doc Text" field above with these four (4) pieces of information:
* Cause: What actions or circumstances cause this bug to present.
* Consequence: What happens when the bug presents.
* Fix: What was done to fix the bug.
* Result: What now happens when the actions or circumstances above occur. (NB: this is not the same as 'the bug doesn't present anymore')
Once filled out, please set the "Doc Type" field to the appropriate value for the type of change made and submit your edits to the bug.
For further details on the Cause, Consequence, Fix, Result format please refer to:
Thanks in advance.
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.