From: "Jan C. Bernauer" <jan.bernauer@t-online.de>
To: kvm@vger.kernel.org
Subject: BUG: Guest lockup and 100% CPU load on host
Date: Thu, 15 Jan 2009 23:10:25 +0100 [thread overview]
Message-ID: <496FB451.3020002@t-online.de> (raw)
Hi,
while I was trying to get pci passthrough to work without vt-d using
the 1to1 mapping (it works ;),
I stumbled upon a solid lock up of the guest.
(Unpatched source shows the same behaviour)
I see a strange look up of the guest OS with the following "features":
- guest doesn't respond anymore
- triggered by load in the guest.
- it seems it is easier to trigger with -smp 2
- host shows qemu process with 100% cpu
- seems to be cured by --no-kvm-irqchip
- --no-kvm-pit does not help
- qmeu console command system_reset works
Right now, guest OS is linux 2.6.27.1
Latest KVM from git, host is 2.6.28.
Older kvms seem to exhibit the same problem.
short gdb session:
Program received signal SIGINT, Interrupt.
[Switching to Thread 0x7f9dfbb7c6f0 (LWP 13898)]
0x00007f9dfa4e1a92 in select () from /lib/libc.so.6
(gdb) info threads
2 Thread 0x7f9dd7d54950 (LWP 13907) 0x00007f9dfa4e1027 in ioctl ()
from /lib/libc.so.6
* 1 Thread 0x7f9dfbb7c6f0 (LWP 13898) 0x00007f9dfa4e1a92 in select ()
from /lib/libc.so.6
(gdb) bt
#0 0x00007f9dfa4e1a92 in select () from /lib/libc.so.6
#1 0x0000000000409a2b in main_loop_wait (timeout=0) at
/usr/src/kvm-userspace/qemu/vl.c:3639
#2 0x0000000000518c6a in kvm_main_loop () at
/usr/src/kvm-userspace/qemu/qemu-kvm.c:600
#3 0x000000000040db93 in main (argc=<value optimized out>,
argv=0x7fff03badc08, envp=<value optimized out>)
at /usr/src/kvm-userspace/qemu/vl.c:3801
(gdb) thread 2
[Switching to thread 2 (Thread 0x7f9dd7d54950 (LWP 13907))]#0
0x00007f9dfa4e1027 in ioctl () from /lib/libc.so.6
(gdb) bt
#0 0x00007f9dfa4e1027 in ioctl () from /lib/libc.so.6
#1 0x0000000000545d8e in kvm_run (kvm=0xde1040, vcpu=0, env=0xe5b070)
at libkvm.c:887
#2 0x0000000000518d89 in kvm_cpu_exec (env=<value optimized out>) at
/usr/src/kvm-userspace/qemu/qemu-kvm.c:210
#3 0x0000000000519078 in ap_main_loop (_env=<value optimized out>) at
/usr/src/kvm-userspace/qemu/qemu-kvm.c:417
#4 0x00007f9dfb032007 in start_thread () from /lib/libpthread.so.0
#5 0x00007f9dfa4e838d in clone () from /lib/libc.so.6
#6 0x0000000000000000 in ?? ()
kvm is started by:
/usr/local/bin/qemu-system-x86_64 -vnc :2 -drive
file=/dev/mapper/mykvmparition,if=virtio,boot=on -net
nic,model=virtio,macaddr=52:54:00:12:34:a0 -net
tap,script=/etc/kvm/kvm-ifup,downscript=/etc/kvm/kvm-ifdown -m 512
Host is an AMD 4850e, all OS are 64bit.
The syslog on the host seems clean.
If you have anything for me to try or need some more information, let me
know.
Best regards,
Jan
next reply other threads:[~2009-01-15 22:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-15 22:10 Jan C. Bernauer [this message]
2009-01-15 23:00 ` BUG: Guest lockup and 100% CPU load on host James Thomason
2009-01-16 10:13 ` Jan Bernauer
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=496FB451.3020002@t-online.de \
--to=jan.bernauer@t-online.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox