Bug 725854 - Spice client is terminated when doing multiple migration
Summary: Spice client is terminated when doing multiple migration
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: spice-server
Version: 6.1
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: rc
: ---
Assignee: Uri Lublin
QA Contact: Desktop QE
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-07-26 18:28 UTC by Marian Krcmarik
Modified: 2011-08-08 14:06 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-08-08 14:06:01 UTC
Target Upstream Version:

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Description Marian Krcmarik 2011-07-26 18:28:36 UTC 
Description of problem:
Spice client is terminated when doing multiple migration of one spice client session. Just do migration from source host to target host and back. When doing the second migration client is closed with message (first migration is successful):
1311704317 INFO [5681:5681] main: Spice client terminated (exitcode = 0)
Migration was done through libvirt and RHEVM3 on RHEL6 host. Once I do migration with the same spice client version on RHEVM2.2 with RHEL5 hosts I am able to do multiple migration (that's why filing bug for spice-server).
After reconnecting with spice client everything is fine => migration itself of guest is successful.

Version-Release number of selected component (if applicable):
qemu-kvm-0.12.1.2-2.171
libvirt-0.9.3-7
spice-server-0.8.1-2
spice-client-0.8.0-2

How reproducible:
always

Steps to Reproduce:
1. Connect to a guest using RHEVM3.0 User portal or virsh
2. Keep spice client session.
3. Do migration to another host.
4. Keep spice client session.
5. Do migration back to original host.
  
Actual results:
1311704317 INFO [5681:5681] main: Spice client terminated (exitcode = 0)

Expected results:
No visible changes for user.

Additional info:
Comment 1 Uri Lublin 2011-07-28 18:43:16 UTC 
Investigation done together with Marian suggests that before the second migration libvirt does not send migrate_info to spice (via qemu-kvm monitor command), so upon migration the server disconnects the client.
Comment 2 Marian Krcmarik 2011-08-05 21:47:56 UTC 
Even though I hit it constantly on different setups, Now I am not able to reproduce, but almost all components got updated. I will do some more tests. In case I am not able to reproduce I will close this bug.
Comment 3 Christophe Fergeau 2011-08-05 22:02:55 UTC 
Ah, nice additional info, #727969 is a bit similar, but this bug seemed to be different. Given your last comment, maybe it was related to this one.
Comment 4 Marian Krcmarik 2011-08-07 17:47:19 UTC 
(In reply to comment #3)
> Ah, nice additional info, #727969 is a bit similar, but this bug seemed to be
> different. Given your last comment, maybe it was related to this one.

I will retest migration with latest components since there were several changes and sort out all those bugs.
Comment 5 Marian Krcmarik 2011-08-08 14:06:01 UTC 
I am not able to reproduce on updated components. Closing, will open If I hit that again.
Note You need to log in before you can comment on or make changes to this bug.