Thank I test the 2 patches and they worked for me.
It works also if you apply only the qemu patch,
in combination the ubuntu kernel 4.4.0-38.57 and qemu 2.6.1.
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
When I set -rtc clock=vm the mig problem is solved, but what does this
flag exactly?
In the docu there is only
" If you want to isolate the guest time from the host, you can set clock to
"rt" instead.
To even prevent it from progressing during suspension, you can set it to
"vm"."
what does
I can reproduce this bug also on Ubuntu 16.04 with libvirt.
The interesting thing is that this bug triggers faster,
if I use tunneled migration instead direct.
Using the virt-manager for migration.
The test VM is a Win10 with virtio driver from fedora 0.1.118.
win10-1
