Your message dated Tue, 12 May 2020 12:05:23 +0300
with message-id <[email protected]>
and subject line Re: Stretch kvm accelerated qemu-system-i386 on i386
archirecture enters infinite loop at startup
has caused the Debian Bug report #902626,
regarding Stretch kvm accelerated qemu-system-i386 on i386 archirecture enters
infinite loop at startup
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
902626: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=902626
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: qemu-system-x86
Version: 1:2.8+dfsg-6+deb9u4
Severity: important
I am on i386 architecture with a CodeDuo processor.
# cat /proc/cpuinfo
rocessor : 0
vendor_id : GenuineIntel
cpu family : 6
model : 15
model name : Intel(R) Core(TM)2 CPU 6400 @ 2.13GHz
stepping : 6
microcode : 0xd0
cpu MHz : 1596.000
cache size : 2048 KB
physical id : 0
siblings : 2
core id : 0
cpu cores : 2
apicid : 0
initial apicid : 0
fpu : yes
fpu_exception : yes
cpuid level : 10
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov
pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx lm
constant_tsc arch_perfmon pebs bts rep_good nopl aperfmperf eagerfpu pni dtes64
monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr pdcm lahf_lm kaiser tpr_shadow dtherm
bugs : cpu_meltdown spectre_v1 spectre_v2
bogomips : 4270.08
clflush size : 64
cache_alignment : 64
address sizes : 36 bits physical, 48 bits virtual
power management:
processor : 1
vendor_id : GenuineIntel
cpu family : 6
model : 15
model name : Intel(R) Core(TM)2 CPU 6400 @ 2.13GHz
stepping : 6
microcode : 0xd0
cpu MHz : 1596.000
cache size : 2048 KB
physical id : 0
siblings : 2
core id : 1
cpu cores : 2
apicid : 1
initial apicid : 1
fpu : yes
fpu_exception : yes
cpuid level : 10
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov
pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx lm
constant_tsc arch_perfmon pebs bts rep_good nopl aperfmperf eagerfpu pni dtes64
monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr pdcm lahf_lm kaiser tpr_shadow dtherm
bugs : cpu_meltdown spectre_v1 spectre_v2
bogomips : 4270.08
clflush size : 64
cache_alignment : 64
address sizes : 36 bits physical, 48 bits virtual
power management:
I upgraded recently a Jessie system to Stretch. The old Jessie ran
flawlessly a few kvm accelerated qemu VMs (command
qemu-system-i386). The Debian upgrade went fine, except that now the
kvm accelerated qemu are stalled even before any Seabios message: the
screen is completely black, and I have 100% CPU for the qemu process.
In the qemu console I can verify that kvm is indeed activated (command
"info kvm" returns "kvm support: enabled").
Modules kvm.ko and kvm_intel.ko are loaded fine:
# lsmod|grep kvm
kvm_intel 192512 0
kvm 593920 1 kvm_intel
irqbypass 16384 1 kvm
# ls -alt /dev/kvm
crw-rw----+ 1 root kvm 10, 232 juin 27 23:17 /dev/kvm
But the sames VM without -enable-kvm work ok. Of course it's not
usable as it's extremely slow.
I tried the 4.16 kernel from stretch-backport, and the behaviour was
the same: ok without acceleration, black screen with -enable-kvm.
Workaround: my CPU is actually amd64 capable; I have a partition where
amd64 Strech is installed for tests, and surprise there the VMs are
running fine and are kvm accelerated with qemu-system-i386. So I ended
up crossgrading the kernel to amd64 (explains the "amd64" in the
system information section below) on my main brand new Stretch i386
system, and now the VMs are working ok and are accelerated.
So the problem seems kvm.ko and kvm_intel.ko related, but to me it
seemed more logical to raise the bug through the package triggering
the bug.
-- System Information:
Debian Release: 9.4
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: i386 (x86_64)
Foreign Architectures: amd64
Kernel: Linux 4.9.0-6-amd64 (SMP w/2 CPU cores)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8),
LANGUAGE=fr_FR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)
Versions of packages qemu-system-x86 depends on:
ii ipxe-qemu 1.0.0+git-20161027.b991c67-1
ii libaio1 0.3.110-3
ii libasound2 1.1.3-5
ii libbluetooth3 5.43-2+deb9u1
ii libbrlapi0.6 5.4-7
ii libc6 2.24-11+deb9u3
ii libcacard0 1:2.5.0-3
ii libfdt1 1.4.2-1
ii libgcc1 1:6.3.0-18+deb9u1
ii libglib2.0-0 2.50.3-2
ii libgnutls30 3.5.8-5+deb9u3
ii libjpeg62-turbo 1:1.5.1-2
ii libncursesw5 6.0+20161126-1+deb9u2
ii libnettle6 3.3-1+b2
ii libnuma1 2.0.11-2.1
ii libpixman-1-0 0.34.0-1
ii libpng16-16 1.6.28-1
ii libpulse0 10.0-1+deb9u1
ii libsasl2-2 2.1.27~101-g0780600+dfsg-3
ii libsdl1.2debian 1.2.15+dfsg1-4
ii libseccomp2 2.3.1-2.1
ii libspice-server1 0.12.8-2.1+deb9u1
ii libtinfo5 6.0+20161126-1+deb9u2
ii libusb-1.0-0 2:1.0.21-1
ii libusbredirparser1 0.7.1-1
ii libvdeplug2 2.3.2+r586-2.1
ii libx11-6 2:1.6.4-3
ii libxen-4.8 4.8.3+xsa267+shim4.10.1+xsa267-1+deb9u8
ii libxenstore3.0 4.8.3+xsa267+shim4.10.1+xsa267-1+deb9u8
ii qemu-system-common 1:2.8+dfsg-6+deb9u4
ii seabios 1.10.2-1
ii zlib1g 1:1.2.8.dfsg-5
Versions of packages qemu-system-x86 recommends:
ii qemu-utils 1:2.8+dfsg-6+deb9u4
Versions of packages qemu-system-x86 suggests:
ii kmod 23-2
pn ovmf <none>
pn qemu-block-extra <none>
pn samba <none>
pn sgabios <none>
pn vde2 <none>
-- no debconf information
--- End Message ---
--- Begin Message ---
Version: 1:5.0-1
Replying to a relatively old bugreport.
There were a few updates in qemu since version 2.8,
including i386 systems. Hopefully this bug has been fixed since that time,
closing this bugreport now. If not, please reopen it. Anyway I suggest you
to switch to a 64bit system, - 32bit is less and less tested these days,
and 32bit has lots of cludges to support large address space with 32bit
numbers.
Thanks,
/mjt
--- End Message ---
