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?
The further reasons this a bit sounded known to me are: /bugs.launchpad .net/qemu/ +bug/1838569 /bugs.launchpad .net/cloud- archive/ +bug/1848497 /bugs.launchpad .net/cloud- archive/ +bug/1882416
https:/
https:/
https:/
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. >Queens- >Ussuri migrations and ensure those are not affected in any bad way by re-breaking on the next step due to this?
Could you please extend your tests that are Mitaka->Queens migrations to become Mitaka-