From: Sheng Yang <sheng@linux.intel.com>
To: kvm@vger.kernel.org, linuxram@us.ibm.com
Cc: Anthony Liguori <aliguori@us.ibm.com>
Subject: Re: kvm: emulation failure
Date: Mon, 22 Jun 2009 13:12:36 +0800 [thread overview]
Message-ID: <200906221312.36795.sheng@linux.intel.com> (raw)
In-Reply-To: <1245439420.6262.349.camel@localhost>
On Saturday 20 June 2009 03:23:40 Ram Pai wrote:
> I see this problem with a x86 sles10 guest running on x86_64 intel host.
> If the guest is reset abruptly and rebooted, some where
> before grub sequence it hangs and the following message is seen in the
> logs
>
> emulation failed (pagetable) rip 7ed5 66 60 ac 20.
>
> I located this instruction sequence in isolinux.bin on the iso ;if that
> is relevant.
>
>
> I did some analysis and find that there is an ept violation, which is
> handled and then the next instruction '66 60' is attempted to decode
> and emulate. But decode fails. kvm continues loops in the kernel
> in __vcpu_run().
>
> the code path is
>
> kvm_run() -> __vcpu_run() -> vcpu_enter_guest() -> kvm_handle_exit() ->
> handle_ept_violation() -> kvm_mmu_page_fault() -> emulate_instruction() ->
> x86_decode_insn()
>
Hi Ram
Seems KVM failed to emulate a unknown instruction.
00000000 6660 pushad
00000002 AC lodsb
And PUSHAD have not implemented in x86_emulate.c.
But I am a little curious about why this code path was only triggered when
reset. Maybe other issue exists.
--
regards
Yang, Sheng
>
> Any insights here on how to fix the problem is appreciated. And if a fix
> already exists even better :)
>
> thanks,
> RP
>
> --
> To unsubscribe from this list: send the line "unsubscribe kvm" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2009-06-22 5:13 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-19 19:23 kvm: emulation failure Ram Pai
2009-06-22 5:12 ` Sheng Yang [this message]
2009-06-22 6:55 ` Ram Pai
2009-06-22 7:11 ` Sheng Yang
2009-06-22 8:26 ` Avi Kivity
2009-06-22 18:20 ` Ram Pai
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=200906221312.36795.sheng@linux.intel.com \
--to=sheng@linux.intel.com \
--cc=aliguori@us.ibm.com \
--cc=kvm@vger.kernel.org \
--cc=linuxram@us.ibm.com \
/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