Comment 46 for bug 1787405

Some noise in libvirt, I'm not entirely sure if VIR_ENUM_IMPL would need all the bumps up to 415 or if inserting it at 282 (next) is safe. I thnik as long as it is the same enum at virQEMUCapsFlags in the header it should be ok right?

Some more missing bits since vfio-ccw isn't available in libvirt 4.0, but it seemed doable as well.
Some more around qemuDomainPrimeVfioDeviceAddresses not yet existing. In general vfio-ccw and some later Mdev code is missing there, I don't think that will work without backporting some more.
The series around 72241444002678f7a8e2f423ff14fcbc27ab0fa5 in particular might be needed - but is that too much?

I'd highly appreciate if Boris (or whoever can afford the time, but was working on this and knows the context) could give that a review. The Debianized and backported changes can be found at [1] - also [3] for qemu, but that was a much safer backport as mentioned before.

Lets see what build and test will say, but maybe here some help to backport it to 4.0 the way you want it might be appreciated - at least in identifying the extended series.
It is now in the same PPA [2] that I referred to before.
[...]
Yeah it failed to build.
I could now just pick above referenced commit on top of what I have, but I think giving you a chance to look at it what you think will be required for a 4.0 backport is probably much more efficient.

[1]: https://git.launchpad.net/~paelzer/libvirt/commit/?id=19e25b48b31f8d717ea466ce2eb9537f5c5b07ea
[2]: https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/3520
[3]: https://git.launchpad.net/~paelzer/ubuntu/+source/qemu/commit/?id=912b6b5ba1c774eb1251f06a3ffb8ba0cf1c1ea2