On 2023-04-30 14:56 +0200, Andreas Haumer wrote: > I have several virtualized systems around here. > > Yesterday I upgraded some of our Bullseye VMs to 11.7 and found, > that now all systems running on a host with an AMD Ryzen 5950X CPU now > crash with segfaults at various commands. > > I have other VMs running on a server with an AMD EPYC CPU. > Those VMs work fine with Debian 11.7 > > But the VMs on the AMD Ryzen 5950X host now all crash. > > The kernel boots and I see the following messages (excerpt): > [ 2.696267] modprobe[296]: segfault at 7ffee6eaeef8 ip > 00007f6c836f2133 sp 00007ffee6eaeed0 error 25 in > libc-2.31.so[7f6c83629000+159000] > [ 2.696272] Code: Unable to access opcode bytes at RIP 0x7f6c836f2109. > [ 2.710874] mount[284]: segfault at 7ffed19f7f78 ip 00007ff4b09b1632 > sp 00007ffed19f7f78 error 25 in libc-2.31.so[7ff4b08d7000+159000] > [ 2.711774] Code: Unable to access opcode bytes at RIP 0x7ff4b09b1608.
Interesting, but certainly not good. On Stackoverflow you can find a thread[1] how to interpret these segfault messages. > The VMs are configured to use the hosts CPU configuration. > On the host I use QEMU/KVM/libvirt as virtualization software: > > root@pauli:~# virsh version > Compiled against library: libvirt 7.0.0 > Using library: libvirt 7.0.0 > Using API: QEMU 7.0.0 > Running hypervisor: QEMU 5.2.0 > > The host is still running Debian 11.6 > > I'm currently trying to figure out what is going on here. My first idea would be that the libc6 upgrade triggered these problems, although the new kernel could also be at fault. Try downgrading libc6 in one of the VMs to version 2.31-13+deb11u5 and see if that helps. Good luck, Sven 1. https://stackoverflow.com/questions/2549214/interpreting-segfault-messages
