Control: severity -1 serious
On Sun, 5 Sep 2021 11:36:56 +0200 Marc Haber <[email protected]>
wrote:
On Sat, Sep 04, 2021 at 09:18:10PM +0200, Marc Haber wrote:
> This is possibly a compatibility issue between qemu, libvirt and
> virt-manager. I am not in a position to debug this in any detail, but I
> think that there should be some versioned dependencies.
This seems to be intentional change in QEMU 6.0 that breaks
compatibility with libvirt, see
https://gitlab.com/libvirt/libvirt/-/issues/212
This is.. um.. really unexpected, to me at least.
They intentionally broke libvirt back in Feb-2011, with a change to
libvirt introduced only 3 weeks ago.
And the most shocking to me was the "why?". /dev/blockdevice is a file
in *nix, and has always been, there's no actual usage difference between
a regular file and a block device, every other tool in linux accepts
either of them, but qemu is different? Why?.. Oh well.
I'll dig around.
Filing an appropriate issue with libvirt as well so that people notice
the incompatibility. Unless libvirt has adapted, I think there should be
versioned dependencies to avoid the qemu update. This incompatibility is
probably release critical to either qemu or libvirt.
Indeed. This is shocking really.
/mjt
