From: Dave Young <hidave.darkstar@gmail.com>
To: kvm@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [BUG] kvm: guest can not startup due to triple fault
Date: Sun, 17 Oct 2010 16:54:17 +0800 [thread overview]
Message-ID: <20101017085416.GA1758@darkstar> (raw)
linux guest can not startup normally, qemu keep rebooting.
host & guest both use linux-2.6.36-rc8+ kernel
Add a dump_stack in x86.c around EXIT_SHUTDOWN code, I got:
[ 3924.503041] Pid: 1685, comm: qemu-system-x86 Not tainted 2.6.36-rc8+ #62
[ 3924.503045] Call Trace:
[ 3924.503055] [<ffffffffa0176047>] handle_triple_fault+0x11/0x26 [kvm_intel]
[ 3924.503060] [<ffffffffa01772d2>] vmx_handle_exit+0x3df/0x474 [kvm_intel]
[ 3924.503080] [<ffffffffa021f203>] kvm_arch_vcpu_ioctl_run+0x95f/0xc43 [kvm]
[ 3924.503087] [<ffffffff81503e54>] ? __mutex_unlock_slowpath+0x11c/0x131
[ 3924.503101] [<ffffffffa021e1f9>] ? kvm_arch_vcpu_load+0x90/0xe6 [kvm]
[ 3924.503112] [<ffffffffa0210faf>] kvm_vcpu_ioctl+0x109/0x54a [kvm]
[ 3924.503117] [<ffffffff810bee76>] ? fire_user_return_notifiers+0x2c/0x36
[ 3924.503122] [<ffffffff8106be93>] ? trace_hardirqs_on+0xd/0xf
[ 3924.503127] [<ffffffff81002789>] ? do_notify_resume+0x717/0x73d
[ 3924.503131] [<ffffffff8103994e>] ? finish_task_switch+0x69/0xda
[ 3924.503135] [<ffffffff8110628c>] do_vfs_ioctl+0x4c3/0x50d
[ 3924.503139] [<ffffffff8110632b>] sys_ioctl+0x55/0x77
[ 3924.503142] [<ffffffff81002c02>] system_call_fastpath+0x16/0x1b
Anyone can help on this?
next reply other threads:[~2010-10-17 8:54 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-17 8:54 Dave Young [this message]
2010-10-17 8:56 ` [BUG] kvm: guest can not startup due to triple fault Dave Young
2010-10-17 9:34 ` Avi Kivity
2010-10-17 10:14 ` Dave Young
2010-10-17 12:15 ` Avi Kivity
2010-10-18 4:43 ` Dave Young
2010-10-18 7:14 ` Jan Kiszka
2010-10-18 8:55 ` Avi Kivity
2010-10-18 8:58 ` Avi Kivity
2010-10-18 12:26 ` Steven Rostedt
2010-10-18 12:27 ` Avi Kivity
2010-10-18 9:15 ` Avi Kivity
2010-10-18 12:58 ` Dave Young
2010-10-18 13:26 ` Avi Kivity
2010-10-18 13:45 ` Dave Young
2010-10-18 13:46 ` Avi Kivity
2010-10-18 13:50 ` Avi Kivity
2010-10-18 13:58 ` Dave Young
2010-10-18 14:06 ` Avi Kivity
2010-10-18 14:11 ` Dave Young
2010-10-18 14:13 ` Avi Kivity
2010-10-18 14:15 ` Dave Young
2010-10-18 14:17 ` Dave Young
2010-10-18 14:19 ` Avi Kivity
2010-10-18 14:25 ` Dave Young
2010-10-18 14:28 ` Avi Kivity
2010-10-18 18:47 ` H. Peter Anvin
2010-10-19 1:19 ` Dave Young
2010-10-19 2:59 ` H. Peter Anvin
2010-10-19 6:55 ` Dave Young
2010-10-19 8:57 ` Avi Kivity
2010-10-19 11:52 ` Dave Young
2010-10-19 14:56 ` H. Peter Anvin
2010-10-19 15:04 ` Avi Kivity
2010-10-19 15:31 ` H. Peter Anvin
2010-10-18 13:51 ` Dave Young
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=20101017085416.GA1758@darkstar \
--to=hidave.darkstar@gmail.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@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