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 884631 - after connection to in-migration VM, block features that depend on seamless-migration till migration finishes
Summary: after connection to in-migration VM, block features that depend on seamless-m...
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: spice-server
Version: 6.4
Hardware: Unspecified
OS: Unspecified
low
low
Target Milestone: beta
: 6.8
Assignee: Default Assignee for SPICE Bugs
QA Contact: SPICE QE bug list
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-12-06 13:02 UTC by David Jaša
Modified: 2015-10-26 16:57 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-10-26 16:57:34 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description David Jaša 2012-12-06 13:02:11 UTC 
Description of problem:
when user connects to in-migration VM, the client isn't able to connect to dst qemu because it is not processing main event loop during migration. That in turn means that some features, such as USB redirection won't survive SWITCH_HOST migration.

The right thing to do in such cases is to block use of such features till the VM is migrated and if user triggers an action that would enable such features, a warning should be issued (preferably non-intrusive one like warnings trough libnotify can do)

If we have non-intrusive notifications, another can be issued that the featurea are available again after SWITCH_HOST migration is performed.

Version-Release number of selected component (if applicable):
spice-gtk-0.14-4.el6.x86_64

How reproducible:
always

Steps to Reproduce:
1. trigger VM migration
2. connect to the VM
3. redirect USB flash drive, start copying some files to/from it
  
Actual results:
flash drive is redirected and when SWITCH_HOST migration takes place, the flash is forcibly disconnected

Expected results:
it is not possible to redirect the flash drive till migration finishes

Additional info:
Comment 1 RHEL Program Management 2013-10-14 04:33:20 UTC 
This request was not resolved in time for the current release.
Red Hat invites you to ask your support representative to
propose this request, if still desired, for consideration in
the next release of Red Hat Enterprise Linux.
Comment 2 Marc-Andre Lureau 2014-04-16 11:59:09 UTC 
David, is this still not working? I think all channels support seamless migrations now.
Comment 3 David Jaša 2014-04-22 13:17:35 UTC 
This was never working: when you connect to already migrating VM, the migration will use switch_host mode in all cases because clients can not connect to destiantion qemu (it's main loop is paused during incoming migration). Since 3.3, RHEV-M uses a workaround - blocking connections to migrating VMs and I'm not aware of any customers complaining so IMO the bug severity is quite low.
Comment 4 Marc-Andre Lureau 2014-04-22 13:26:30 UTC 
(In reply to David Jaša from comment #3)
> This was never working: when you connect to already migrating VM, the
> migration will use switch_host mode in all cases because clients can not
> connect to destiantion qemu (it's main loop is paused during incoming
> migration). Since 3.3, RHEV-M uses a workaround - blocking connections to
> migrating VMs and I'm not aware of any customers complaining so IMO the bug
> severity is quite low.

I think the server should also block new connection during migrations..
Comment 5 David Blechter 2014-06-09 17:25:27 UTC 
low priority, moving to 6.6 for triage
Comment 7 David Blechter 2015-10-26 16:57:34 UTC 
This is low priority improvement, closing as WONTFIX in rhel 6.x
Note You need to log in before you can comment on or make changes to this bug.