Ubuntu
qemu package

  1. Bug #1783140
  2. Comment #10

Comment 10 for bug 1783140

Revision history for this message
bugproxy (bugproxy) wrote : Comment bridged from LTC Bugzilla

------- Comment From <email address hidden> 2018-07-30 10:24 EDT-------
The host (KVM hypervisor) is 16.04.
So you suggest to install newer UCA qemu on the hypervisors.
That is something I have to decline today. Those hosts are runnung some more VMs. So to update the hypervisors I need a service window aggreed with my customers. And I have to stay on a kind of supported mainstream level, no experimental stuff.
Until then I can do some tests with some guest VMs.
Or someone other has a test environment where he/she can play also with the hypervisors. As I mentioned: the problem is reproducible !

----------

So now I did another test with a 16.04 guest. The problem gets worse, but maybe it helps in catching the bug.

I did a new installation of a VM with Ubuntu 16.04.5 LTS, kernel 4.4.0-131-generic #157-Ubuntu SMP.
Live migration succeeded.
Then I installed linux-generic-hwe-16.04.
The system booted with kernel 4.15.0-29-generic #31~16.04.1-Ubuntu SMP.
And live migration failed:
# virsh migrate --persistent --live p8lnxtst1 qemu+ssh://pkvm1/system
error: internal error: early end of file from monitor, possible problem: 2018-07-30T14:13:34.381447Z qemu-system-ppc64: VQ 0 size 0x100 Guest index 0x302 inconsistent with Host index 0x16c: delta 0x196
2018-07-30T14:13:34.381496Z qemu-system-ppc64: error while loading state for instance 0x0 of device 'pci@800000020000000:01.0/virtio-net'
2018-07-30T14:13:34.381806Z qemu-system-ppc64: load of migration failed: Operation not permitted

It is still very reproducible!

This means the new hwe kernel introduced the problem !!! Or it is just not compatible with 4.4.0-130-generic of the KVM hypervisor.
BTW, no entry in the /var/log/libvirt/qemu log files regarding the migration attempts. Any other log or trace files I could look for or activate?