From: bugzilla-daemon@bugzilla.kernel.org
To: kvm@vger.kernel.org
Subject: [Bug 100661] kernel panic in vmx_vcpu_run
Date: Mon, 29 Jun 2015 13:21:08 +0000 [thread overview]
Message-ID: <bug-100661-28872-A9yaFlBR17@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-100661-28872@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=100661
--- Comment #2 from Lidong Chen <jemmy858585@gmail.com> ---
i think the stack is broken.
so the rsi value is error.
vcpu->arch.regs_avail = ~((1 << VCPU_REGS_RIP) | (1 << VCPU_REGS_RSP)
bf8d: 48 8b 75 98 mov -0x68(%rbp),%rsi
static __always_inline unsigned long vmcs_readl(unsigned long field)
{
unsigned long value;
asm volatile (__ex_clear(ASM_VMX_VMREAD_RDX_RAX, "%0")
bf91: ba 08 44 00 00 mov $0x4408,%edx
*/
loadsegment(ds, __USER_DS);
loadsegment(es, __USER_DS);
#endif
vcpu->arch.regs_avail = ~((1 << VCPU_REGS_RIP) | (1 << VCPU_REGS_RSP)
bf96: c7 86 48 02 00 00 ef movl $0xffe0ffef,0x248(%rsi)
--
You are receiving this mail because:
You are watching the assignee of the bug.
next prev parent reply other threads:[~2015-06-29 13:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-29 13:15 [Bug 100661] New: kernel panic in vmx_vcpu_run bugzilla-daemon
2015-06-29 13:17 ` [Bug 100661] " bugzilla-daemon
2015-06-29 13:21 ` bugzilla-daemon [this message]
2017-03-06 20:07 ` bugzilla-daemon
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=bug-100661-28872-A9yaFlBR17@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.kernel.org \
--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