Bug 894020
Summary: | PRD32 - [RFE] spice seamless migration support in win client | ||
---|---|---|---|
Product: | Red Hat Enterprise Virtualization Manager | Reporter: | Yonit Halperin <yhalperi> |
Component: | RFEs | Assignee: | Uri Lublin <uril> |
Status: | CLOSED ERRATA | QA Contact: | Desktop QE <desktop-qa-list> |
Severity: | unspecified | Docs Contact: | |
Priority: | unspecified | ||
Version: | 3.2.0 | CC: | acathrow, cfergeau, chetan, cpelland, dblechte, dyasny, iheim, lpeer, mkrcmari, sgrinber |
Target Milestone: | --- | Keywords: | FutureFeature |
Target Release: | 3.2.0 | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | spice | ||
Fixed In Version: | mingw-virt-viewer-0.5.3-18 mingw-spice-gtk-0.14-1 | Doc Type: | Enhancement |
Doc Text: |
Seamless migration of SPICE sessions is now supported for virtual machines running on Red Hat Enterprise Linux 6.4 hosts. This feature allows ongoing USB, vdagent, and smartcard data transfers between the server and the client to be continued smoothly after migration, with no data loss.
|
Story Points: | --- |
Clone Of: | Environment: | ||
Last Closed: | 2013-06-10 21:32:40 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | Spice | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: | |||
Bug Depends On: | 836123, 836133, 836135, 846910, 846911, 905898 | ||
Bug Blocks: | 894396 |
Description
Yonit Halperin
2013-01-10 14:34:47 UTC
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: https://bugzilla.redhat.com/page.cgi?id=fields.html#cf_release_notes 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. http://rhn.redhat.com/errata/RHSA-2013-0888.html |