Date: Wed, 27 Nov 2024 01:01:07 +0000 From: bugzilla-noreply@freebsd.org To: virtualization@FreeBSD.org Subject: [Bug 279901] glibc-2.39-2 and above on the host segfault Message-ID: <bug-279901-27103-H3HXy0g8F9@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-279901-27103@https.bugs.freebsd.org/bugzilla/> References: <bug-279901-27103@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D279901 Koichiro Iwao <meta@FreeBSD.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |meta@FreeBSD.org URL| |https://sourceware.org/bugz | |illa/show_bug.cgi?id=3D309= 94 --- Comment #15 from Koichiro Iwao <meta@FreeBSD.org> --- Hi, I'm also an AlmaLinux member and encountered the same issue with AlmaLi= nux 9.5 and 10 Kitten. AlmaLinux 10 Kitten has glibc 2.39 but 9.x has older versions. In AlmaLinux 9, glibc-2.34-100.el9_4.4 for 9.4 doesn't have the issue but glibc-2.34-125.el9_5.1 for 9.5 does. So I guess some changes between the versions affects. It was the offending commit the reporter mentioned.=20 https://git.almalinux.org/rpms/glibc/commit/4da5357bcd7b44f2ee8891f477a5a6c= 34973ddba https://gitlab.com/redhat/centos-stream/rpms/glibc/-/commit/6dbf26d6f46fce3= 7e63fcf2eec542b03ef4e0704 AlmaLinux team reverted the changes and it avoided the issue. I'm still not sure if this issue is glibc bug or bhyve bug. At least I've never seen this issue except bhyve. Have anyone seen this on bare Zen 3/4 machines? --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-279901-27103-H3HXy0g8F9>