From: Nate Custer <nate@cpanel.net>
To: kvm@vger.kernel.org
Subject: kvm deadlock
Date: Mon, 5 Dec 2011 16:48:16 -0600 [thread overview]
Message-ID: <54FC5923-2123-4BDD-A506-EA57DCE0C1F6@cpanel.net> (raw)
Hello,
I am struggling with repeatable full hardware locks when running 8-12 KVM vms. At some point before the hard lock I get a inconsistent lock state warning. An example of this can be found here:
http://pastebin.com/8wKhgE2C
After that the server continues to run for a while and then starts its death spiral. When it reaches that point it fails to log anything further to the disk, but by attaching a console I have been able to get a stack trace documenting the final implosion:
http://pastebin.com/PbcN76bd
All of the cores end up hung and the server stops responding to all input, including SysRq commands.
I have seen this behavior on two machines (dual E5606 running Fedora 16) both passed cpuburnin testing and memtest86 scans without error.
I have reproduced the crash and stack traces from a Fedora debugging kernel - 3.1.2-1 and with a vanilla 3.1.4 kernel.
Nate Custer
QA Analyst
cPanel Inc
next reply other threads:[~2011-12-05 22:48 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-05 22:48 Nate Custer [this message]
2011-12-14 12:25 ` kvm deadlock Marcelo Tosatti
2011-12-14 13:43 ` Avi Kivity
2011-12-14 14:00 ` Marcelo Tosatti
2011-12-14 14:02 ` Avi Kivity
2011-12-14 14:06 ` Marcelo Tosatti
2011-12-14 14:17 ` Nate Custer
2011-12-14 14:20 ` Marcelo Tosatti
2011-12-14 14:28 ` Avi Kivity
2011-12-14 14:27 ` Avi Kivity
2011-12-14 16:03 ` Jens Axboe
2011-12-14 17:03 ` Vivek Goyal
2011-12-14 17:09 ` Jens Axboe
2011-12-14 17:22 ` Vivek Goyal
2011-12-14 18:16 ` Tejun Heo
2011-12-14 18:41 ` Vivek Goyal
2011-12-14 23:06 ` Vivek Goyal
2011-12-15 19:47 ` [RFT PATCH] blkio: alloc per cpu data from worker thread context( Re: kvm deadlock) Vivek Goyal
[not found] ` <E73DB38E-AFC5-445D-9E76-DE599B36A814@cpanel.net>
2011-12-16 20:29 ` Vivek Goyal
2011-12-18 21:25 ` Nate Custer
2011-12-19 13:40 ` Vivek Goyal
2011-12-19 17:27 ` Vivek Goyal
2011-12-19 17:35 ` Tejun Heo
2011-12-19 18:27 ` Vivek Goyal
2011-12-19 22:56 ` Tejun Heo
2011-12-20 14:50 ` Vivek Goyal
2011-12-20 20:45 ` Tejun Heo
2011-12-20 12:49 ` Jens Axboe
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=54FC5923-2123-4BDD-A506-EA57DCE0C1F6@cpanel.net \
--to=nate@cpanel.net \
--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.