Comment 31 for bug 1913266

Non-fixed builds do not accept the required configuration at all.

error: XML document failed to validate against schema: Unable to validate doc against /usr/share/libvirt/schemas/domain.rng
Extra element devices in interleave
Element domain failed to validate content

Failed. Try again? [y,n,i,f,?]:

But specifying cid/iommu is reuqired to be usable in SE environments.

Now I upgraded to the new builds that are in proposed.
  Unpacking libvirt-daemon-system (6.0.0-0ubuntu8.7) over (6.0.0-0ubuntu8.5) ...
  Unpacking libvirt-daemon-system (6.6.0-1ubuntu3.3) over (6.6.0-1ubuntu3.1) ...
Both worked without issues

With those the new config could be added.
That is one check passed \o/

But the second check I need IBM for.
We have discussed/thought that we can check the commandline that is generated and ignore that this is eventually to help an SE environment. But TBH in my case there is no iommu rendered in the commandline.

It is not even adding any -device vhost-vsock-ccw or such. Maybe in my restricted environment another pre-check fails.
I've had a focal LPAR around that I was able to use, there things work as expected.

ubuntu@s1lp5:~$ sudo grep -e iommu -e vsock /var/log/libvirt/qemu/h-test.log
-device vhost-vsock-ccw,id=vsock0,guest-cid=3,vhostfd=27,iommu_platform=on,devno=fe.0.0005 \

I just can't bump this to groovy atm.
So I've used a 2nd level KVM for groovy.
Finally there I can confirm as well:
ubuntu@g-test:~$ sudo grep -e iommu -e vsock /var/log/libvirt/qemu/testvm.log
-device vhost-vsock-ccw,id=vsock0,guest-cid=3,vhostfd=25,iommu_platform=on,devno=fe.0.0005 \

So - both releases verified