On Fri, Feb 25, 2022 at 06:40:23PM +0100, Hans van Kranenburg wrote: > > However, I hope you understand that there's no way we can help when you > use something else than the actual packages in Debian, do not provide > any error messages seen, and describe what you see instead as "it felt > like everything wanted to explode".
I'm aware I've got things in a state which is outside the support envelope. I was hoping observations might also apply inside the support envelope. > For me, Xen 4.16 does run OK on my test servers, FWIW. That doesn't surprise me, it didn't take long to get things into a working state for me. Just I was able to get things into a problematic state which the packaging is supposed to prevent. xen-utils-4.16 depends on: libxencall1, libxenevtchn1, libxenforeignmemory1, libxengnttab1, and libxentoollog1. On a system being upgraded there will be 3 versions of each of these libraries available. 4.14.3+32-g9de3671772-1 4.14.3+32-g9de3671772-1~deb11u1 4.16.0-1~exp1 Issue is the rebuilt xen-hypervisor-4.16 and xen-utils-4.16 could be installed without updating libxencall1, libxenevtchn1, libxenforeignmemory1, libxengnttab1, and libxentoollog1. With the 4.14.3+32-g9de3671772-1~deb11u1 versions of libraries things were broken. I'm unsure which one(s) was the problem, though the problem disappeared once all 5 were updated. That enough for you? -- (\___(\___(\______ --=> 8-) EHM <=-- ______/)___/)___/) \BS ( | [email protected] PGP 87145445 | ) / \_CS\ | _____ -O #include <stddisclaimer.h> O- _____ | / _/ 8A19\___\_|_/58D2 7E3D DDF4 7BA6 <-PGP-> 41D1 B375 37D0 8714\_|_/___/5445
