Comment 1 for bug 1640676

Hi,
so it is writing huge buffers and corrupts on migration - interesting.
Might I ask what Release and versions qemu/libvirt are you on with this?

We have a regular set of migration Tests that we are running since recently.
One of the cases is a guest with workload that might be critical - I added yours.

Also what exactly do you mean by "do a hard reboot"?
Reboot from the guest - virsh shutdown and wait and start - virsh destroy and start?
For now I added a normal shutdown, wait-til-gone,start iteration.

In my tests on Xenial (I had to pick one to be fast) I migrated 5 times with and 5 times without workload (including yours now) with live and offline migration and afterwards restarted the guest.

They worked for me, so please share more details.

P.S. no matter what it already was worth to make this part of the regular tests - we will see after the weekend how that went on more architectures and releases.