The further reasons this a bit sounded known to me are: https://bugs.launchpad.net/qemu/+bug/1838569 https://bugs.launchpad.net/cloud-archive/+bug/1848497 https://bugs.launchpad.net/cloud-archive/+bug/1882416 They ended up fixing a similar baloon migration issue around "Bad config data" but the "VQ 2 size 0x80" you address here was mentioned there as well.
These also illustrate some danger of these changes, that they might immediately work, but later on break. Could you please extend your tests that are Mitaka->Queens migrations to become Mitaka->Queens->Ussuri migrations and ensure those are not affected in any bad way by re-breaking on the next step due to this? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1894772 Title: live migration of windows 2012 r2 instance with virtio balloon driver fails from mitaka to queens. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1894772/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
