I just updated from a working 193 setup with a UEFI booting VM on it to 194 and the VM doesn’t boot any longer. It still reaches Grub so I assume it isn’t the recent UEFI firmware addition, but after that it just hangs (only a force stop or reset is still recognized).
I didn’t change anything else, so I assume something in 194 must be causing issues with libvirt.
Thanks for the help.
Libvirt itself has not been changed since CU192.
In CU194 libvirt was shipped so that the version linked to an updated libxml2 was shipped due to an sobump in libxml2.
libxml2 is a library used to parse xml documents, and libvirt uses it to parse the vm definitions etc.
However libxml2 has nothing to do with the booting phase of libvirt.
Is there any message at all in the boot logs or does it just hang at the grub screen?
No one highlighted any problems with libvirt during the CU194 Testing phase but also no one said that they had tested it and it worked.
Hopefully other users of libvirt on IPFire can report if their libvirt also hung after the CU194 update or if they have a working system.
It just hangs after the grub screen.