[Spice-devel] virtio device/drive hangs after live migrate

[Rozen Lin]

Hi,all!
   Currently I'm trying to use the current libvirt/qemu-kvm/spice to do
the live migrate for the WindowsXP guests. This is the env I use:

1.  libvirt-0.9.12 + qemu-kvm-1.1.0 + spice-gtk-0.11 +
spice-guest-tools-0.1.exe(this is the qxl/virtio drivers/services)
2.  src/dest host: all ubuntu1004 x86_64; data server:redhat.
3.  the VM image is stored in data server and mounted by the two hosts. 
4.  do the live migrate by 'virsh migrate --live domainName qemu
+ssh://hostB/system'
5.  when finished, spice client will automatically connect to hostB, but
the guest machine acts very slow and the spice client shows that vdagent
is down but in guest it show vdagent/vdservice is still running, this
will keep hang util a reboot and all be fine again.
6.  the hang will not happen if not use the virtio device.

 This is all the virtio the qemu use: -device virtio-serial-pci and
-device virtio-ballon-pci
  Nothing suspicious found in spicec/spiceserver/vdagent/vdservice log.
and during the hang, qemu strace are looping in this:

rt_sigaction(SIGALRM, NULL, {0x7f47f6594290, ~[KILL STOP RTMIN RT_1],
SA_RESTORER, 0x7f47f472c8f0}, 8) = 0
write(9, "\1\0\0\0\0\0\0\0", 8)         = 8
read(7, 0x7fff46820f80, 128)            = -1 EAGAIN (Resource
temporarily unavailable)
timer_settime(0, 0, {it_interval={0, 0}, it_value={0, 374585}}, NULL) =
0
timer_gettime(0, {it_interval={0, 0}, it_value={0, 292451}}) = 0
    ...
select()
read(8, "\1\0\0\0\0\0\0\0", 512)        = 8
timer_gettime(0, {it_interval={0, 0}, it_value={0, 0}}) = 0
timer_settime(0, 0, {it_interval={0, 0}, it_value={0, 743430}}, NULL) =
0
read(7, "\16\0\0\0\0\0\0\0\376\377\377\377\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0
\0\0\0\0\0"..., 128) = 128
rt_sigaction(SIGALRM, NULL, {0x7f47f6594290, ~[KILL STOP RTMIN RT_1],
SA_RESTORER, 0x7f47f472c8f0}, 8) = 0
   
    So now I lose my clue here, I found some others have met the issue
but it's on debian guest:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=580649
    Anyone else faced this and tried to resolve this? shall I debug the
virtio device/drive to detect this?
 Thanks in advance.
 Best regards.