I was able to confirm that this is due to
https://gitlab.com/libvirt/libvirt/-/commit/038dabc2a37e58afbfe3172c128f30533e920157
And fixed by
https://salsa.debian.org/libvirt-team/libvirt/-/merge_requests/112/diffs?commit_id=7fe2075ef7374a59880ec10e26fdd333d4bbd6c6
I've applied this to my PPA build
virtqemud-sock does not exist in either good/bad environment and should
not be needed as we are NOT running libvirt in split-daemon, but in
monolithic mode. Normal interaction like via virsh and all such work
just fine.
We had a similar bug a while back that tried to access virtqemud-sock.
That wa
Reproducible in local VM based autopkgtest with old vs new libvirt
Can be reduced to one test like
/tmp/autopkgtest.hEvpE1/build.rQh/src$ python3 -Wd -m pytest -vv -rs
tests/factory/test_factory.py::test_ubuntu
ubuntu@autopkgtest:/tmp/autopkgtest.Pe4Bbu/build.ROR/src$ python3 -Wd -m pytest
-vv
