From: Bernd Schubert <bernd.schubert@itwm.fraunhofer.de>
To: kvm@vger.kernel.org
Subject: 3.9 / 3.10: Reliable host crashes
Date: Wed, 10 Jul 2013 16:16:46 +0200 [thread overview]
Message-ID: <krjqc7$a8c$1@ger.gmane.org> (raw)
Hi all,
I found a way to reliably crash my host system:
1) Boot guest VM with init=/bin/bash
2) In guest VM: echo b >/proc/sysrq-trigger
3) Try to reboot the guest -> crashes the host during kernel initialization
When I checked the logs I first thought it would be a KSM issue:
> Jul 10 15:33:37 fsdevel7 kernel: [ 507.995602] br0: port 3(tap2) entered disabled state
> Jul 10 15:33:37 fsdevel7 kernel: [ 508.043454] BUG: unable to handle kernel NULL pointer dereference at 0000000000000020
> Jul 10 15:33:37 fsdevel7 kernel: [ 508.043487] IP: [<ffffffff811825b9>] get_ksm_page+0x39/0x130
and
> Jul 10 15:34:49 fsdevel7 kernel: [ 580.274709] RIP: 0010:[<ffffffff8116d694>] [<ffffffff8116d694>] anon_vma_clone+0x94/0x1a0
> Jul 10 15:34:49 fsdevel7 kernel: [ 580.274710] RSP: 0018:ffff880406495cf0 EFLAGS: 00010286
> Jul 10 15:34:49 fsdevel7 kernel: [ 580.274721] Call Trace:
> Jul 10 15:34:49 fsdevel7 kernel: [ 580.274724] [<ffffffff8116d868>] anon_vma_fork+0x38/0x130
> Jul 10 15:34:49 fsdevel7 kernel: [ 580.274728] [<ffffffff8105770f>] dup_mmap+0x1bf/0x420
But then I simply disabled KSM in rc.local
(echo 0 > /sys/kernel/mm/ksm/run) before starting the VMs. Now the
system still crashes, but now without any logs message.
At least sysrq-b still works, but I don' see any
"SysRq : Emergency Sync" messages in log files. So log messages are not
written properly anymore. Unfortunately I don't have a serial console on
my desktop system.
I don't have the time now, but the next step is probably to get a
crash-dump and to see if that has something useful. And I'm also going
to run the VM from a tty without X, maybe it prints something to the
console.
Anything else you might want? Or already any idea?
Crashes do not happen with 3.8-ubuntu, but very reliably with 3.9.9 or
3.10.1 (host).
Here's my kvm command line:
> qemu-system-x86_64 \
> -m 8192 \
> -machine type=pc,accel=kvm,kernel_irqchip=on \
> -netdev type=tap,script=${kvm_ifup},downscript=${kvm_ifdown},ifname=$iface,vhost=on,id=guest0 \
> -device virtio-net-pci,netdev=guest0,mac=52:54:00:12:34:11 \
> -boot c \
> -drive file=${FILE},if=${DISKIF},cache=unsafe \
> -drive file=${META},if=${DISKIF},cache=writeback \
> -drive file=${STORAGE},if=${DISKIF},cache=writeback \
> -enable-kvm \
> -vga vmware \
> -cpu host \
> -smp 4 \
> "$@"
Thanks,
Bernd
next reply other threads:[~2013-07-10 14:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-10 14:16 Bernd Schubert [this message]
2013-07-10 16:02 ` 3.9 / 3.10: Reliable host crashes Gleb Natapov
2013-07-10 16:06 ` Bernd Schubert
2013-07-10 16:16 ` Gleb Natapov
[not found] ` <51DD8A7E.6070508@itwm.fraunhofer.de>
2013-07-10 16:25 ` Gleb Natapov
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='krjqc7$a8c$1@ger.gmane.org' \
--to=bernd.schubert@itwm.fraunhofer.de \
--cc=kvm@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.