Alexander, On Sat, Dec 31, 2022 at 10:28:21AM +0100, Alexander Graf wrote: > On 30.12.22 19:16, Vitaly Chikunov wrote: > > On Fri, Dec 30, 2022 at 06:44:14PM +0100, Alexander Graf wrote: > > > > > > This is a kvm kernel bug and should be fixed with the latest stable releases. Which kernel version are you running? > > This is on latest v6.0 stable - 6.0.15. > > > > Maybe there could be workaround for such situations? (Or maybe it's > > possible to make this error non-fatal?) We use qemu+kvm for testing and > > now we cannot test on x86. > > I'm confused what's going wrong for you. I tried to reproduce the issue > locally, but am unable to: > > $ uname -a > Linux server 6.0.15-default #1 SMP PREEMPT_DYNAMIC Sat Dec 31 07:52:52 CET > 2022 x86_64 x86_64 x86_64 GNU/Linux > $ linux32 chroot . > $ uname -a > Linux server 6.0.15-default #1 SMP PREEMPT_DYNAMIC Sat Dec 31 07:52:52 CET > 2022 i686 GNU/Linux > $ cd qemu > $ file ./build/qemu-system-i386 > ./build/qemu-system-i386: ELF 32-bit LSB shared object, Intel 80386, version > 1 (SYSV), dynamically linked, interpreter /lib/ld-linux.so.2, for GNU/Linux > 3.2.0, BuildID[sha1]=f75e20572be5c604c121de4497397665c168aa4c, with > debug_info, not stripped > $ ./build/qemu-system-i386 --version > QEMU emulator version 7.2.0 (v7.2.0-dirty) > Copyright (c) 2003-2022 Fabrice Bellard and the QEMU Project developers > $ ./build/qemu-system-i386 -nographic -enable-kvm > SeaBIOS (version rel-1.16.1-0-g3208b098f51a-prebuilt.qemu.org) > [...] > > > Can you please double check whether your host kernel version is 6.0.15? > Please paste the output of "uname -a". Excuse me, I'm incorrectly reported kernel version I tried to boot instead of host one. Host kernels are quite old, 5.15.59 and even 5.17.15 -- where failure is occurring. I just tested on 5.15.85 and there is no failure. builder@i586:/.in$ uname -a Linux localhost.localdomain 5.15.85-std-def-alt1 #1 SMP Wed Dec 21 21:14:40 UTC 2022 i686 GNU/Linux builder@i586:/.in$ qemu-system-i386 -nographic -enable-kvm SeaBIOS (version 1.16.1-alt1) Perhaps, one of solutions it to reboot our build fleet to newer kernels. [This maybe hard, though, since special builder node image should be created and reboot shall be coordinated through all systems, in compare, updating QEMU would be easier since chroot is created on every build]. Thanks for your helpful replies! Thanks, > > > Alex
