Your message dated Tue, 11 Jun 2019 15:05:49 +0200 with message-id <20190611130549.GA7139@pisco.westfalen.local> and subject line Re: Bug#771661: machine is completely unusable has caused the Debian Bug report #771661, regarding VM becomes unresponsive - soft lockup, RCU stall 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 owner@bugs.debian.org immediately.) -- 771661: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=771661 Debian Bug Tracking System Contact owner@bugs.debian.org with problems
--- Begin Message ---
- To: Debian Bug Tracking System <submit@bugs.debian.org>
- Subject: qemu-kvm: kernel crash on guest while pegged at 100% cpu
- From: Toni Mueller <support@oeko.net>
- Date: Sun, 30 Nov 2014 23:12:16 +0000
- Message-id: <20141130231211.GA6497@lappi1.office.oeko.net>
Package: qemu-kvm Version: 2.1+dfsg-5~bpo70+1 Severity: important Dear Maintainer, first off, I am not sure whether this is the right package to report the bug against. Feel free to re-assign as you see fit. One of my VMs will not run correctly. Under circumstances which I have not yet been able to pinpoint, the VM goes to 100% cpu and stops reacting to about any input. I have to kill it hard (eg. "Force off" in the virt-manager). The problem occurred twice today, always under load in the VM. The second time, it occurred while I tried to install a new kernel package (see screenshots). I have opened the console and saw a series of kernel oopsies floating by. I have attached two screenshots, one from my SSH session, and one from the console showing the kernel problems. Here is a list of related packages that I have installed on my host: $ dpkg -l|grep -E '(qemu|kvm)' ii etherboot-qemu 5.4.4-9 all Bootstrapping for various network adapters (qemu) ii ipxe-qemu 1.0.0+git-20131111.c3d1e78-2.1~bpo70+1 all PXE boot firmware - ROM images for qemu ii qemu 1.1.2+dfsg-6a+deb7u5 i386 fast processor emulator ii qemu-kvm 2.1+dfsg-5~bpo70+1 i386 QEMU Full virtualization on x86 hardware ii qemu-slof 20131015+dfsg-1~bpo70+1 all Slimline Open Firmware -- QEMU PowerPC version ii qemu-system 2.1+dfsg-5~bpo70+1 i386 QEMU full system emulation binaries ii qemu-system-arm 2.1+dfsg-5~bpo70+1 i386 QEMU full system emulation binaries (arm) ii qemu-system-common 2.1+dfsg-5~bpo70+1 i386 QEMU full system emulation binaries (common files) ii qemu-system-mips 2.1+dfsg-5~bpo70+1 i386 QEMU full system emulation binaries (mips) ii qemu-system-misc 2.1+dfsg-5~bpo70+1 i386 QEMU full system emulation binaries (miscelaneous) ii qemu-system-ppc 2.1+dfsg-5~bpo70+1 i386 QEMU full system emulation binaries (ppc) ii qemu-system-sparc 2.1+dfsg-5~bpo70+1 i386 QEMU full system emulation binaries (sparc) ii qemu-system-x86 2.1+dfsg-5~bpo70+1 i386 QEMU full system emulation binaries (x86) ii qemu-user 1.1.2+dfsg-6a+deb7u5 i386 QEMU user mode emulation binaries ii qemu-utils 2.1+dfsg-5~bpo70+1 i386 QEMU utilities $ Thank you! Kind regards, --Toni++ -- System Information: Debian Release: 7.7 APT prefers stable APT policy: (990, 'stable'), (500, 'stable-updates'), (500, 'unstable'), (500, 'testing') Architecture: i386 (i686) Kernel: Linux 3.16-0.bpo.3-686-pae (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages qemu-kvm depends on: ii dpkg 1.16.15 ii qemu-system-x86 2.1+dfsg-5~bpo70+1 qemu-kvm recommends no packages. qemu-kvm suggests no packages. -- no debconf informationAttachment: vm-hangs-kernel-crash.png
Description: PNG imageAttachment: vm-crash-what-i-was-doing.png
Description: PNG image
--- End Message ---
--- Begin Message ---
- To: Toni Mueller <support@oeko.net>
- Cc: 771661-done@bugs.debian.org
- Subject: Re: Bug#771661: machine is completely unusable
- From: Moritz Mühlenhoff <jmm@inutil.org>
- Date: Tue, 11 Jun 2019 15:05:49 +0200
- Message-id: <20190611130549.GA7139@pisco.westfalen.local>
- In-reply-to: <20150302121724.GA4431@lappi1.office.oeko.net>
- References: <20141209145227.GB27143@lappi1.office.oeko.net> <1418148669.3599.36.camel@decadent.org.uk> <20141209225118.GA15471@lappi1.office.oeko.net> <1419644346.4705.154.camel@decadent.org.uk> <20141227112034.GA11587@lappi1.office.oeko.net> <1419689590.4705.159.camel@decadent.org.uk> <1419689752.4705.160.camel@decadent.org.uk> <20150302121724.GA4431@lappi1.office.oeko.net>
On Mon, Mar 02, 2015 at 12:17:25PM +0000, Toni Mueller wrote: > > Hi Ben, > > On Sat, Dec 27, 2014 at 03:15:52PM +0100, Ben Hutchings wrote: > > Never mind, I've seen your later message with a complete log and I will > > reply to that. > > I haven't heard back from you, but in the meantime reformatted the > machine from i386 (i686) to amd64, but also upgraded to testing, and the > problem mostly went away. Closing the bug, then. Cheers, Moritz
--- End Message ---