public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Paolo Bonzini <pbonzini@redhat.com>
To: duy.nguyen@dektech.com.au
Cc: kvm@vger.kernel.org
Subject: Re: Emulation failure
Date: Mon, 19 Aug 2013 11:27:57 +0200	[thread overview]
Message-ID: <5211E51D.8080009@redhat.com> (raw)
In-Reply-To: <1376874854.25492.10.camel@localhost>

Il 19/08/2013 03:14, Duy Nguyen TN ha scritto:
> 
> I got this error with qem-kvm-0.15.1 on kernel 3.1.0-1.2-desktop
> (OpenSUSE 12.1). I know I should rerun it with latest kernel/qemu but I
> hope maybe this rings a bell or something, because it'll take some time
> for me to prepare new kernel.
> 
> KVM internal error. Suberror: 1
> emulation failure
> RAX=00007ffff7ff9000 RBX=00007ffff7e93608 RCX=00007ffff5d4d81a
> RDX=0000000000000001
> RSI=0000000000001000 RDI=0000000000000000 RBP=0000000069a07700
> RSP=00007ffff7e934b0
> R8 =0000000000000008 R9 =0000000000000000 R10=0000000000000002
> R11=0000000000000246
> R12=0000000069a07700 R13=00007ffff7e937d8 R14=0000003000704c04
> R15=0000003000704c04
> RIP=0000000000b1dd44 RFL=00010202 [-------] CPL=3 II=0 A20=1 SMM=0 HLT=0
> ES =0000 0000000000000000 ffffffff 00000000
> CS =0033 0000000000000000 ffffffff 00a0fb00 DPL=3 CS64 [-RA]
> SS =002b 0000000000000000 ffffffff 00c0f300 DPL=3 DS   [-WA]
> DS =0000 0000000000000000 ffffffff 00000000
> FS =0000 00007ffff7e94700 ffffffff 00000000
> GS =0000 0000000000000000 ffffffff 00000000
> LDT=0000 0000000000000000 ffffffff 00000000
> TR =0040 ffff88003aa0df80 00002087 00008b00 DPL=0 TSS64-busy
> GDT=     ffff88003aa04000 0000007f
> IDT=     ffffffff816ad000 00000fff
> CR0=80050033 CR2=00007ffff5a68180 CR3=00000000289ad000 CR4=000006f0
> DR0=0000000000000000 DR1=0000000000000000 DR2=0000000000000000
> DR3=0000000000000000
> DR6=00000000ffff0ff0 DR7=0000000000000400
> EFER=0000000000000d01
> Code=00 85 c0 75 5d 48 8b 05 5c f5 e1 00 48 83 b8 f0 00 00 00 00 <df> a8
> f0 00 00 00 0f 88 a0 00 00 00 8b 05 4a f5 e1 00 48 89 44 24 80 df 6c 24
> 80 de c9 d8
> 
> The disassembled code is
> 
>    0x1dd10:    push   %rbx
>    0x1dd11:    mov    $0x6e,%eax
>    0x1dd16:    mov    %rdi,%rbx
>    0x1dd19:    sub    $0x20,%rsp
>    0x1dd1d:    test   %rdi,%rdi
>    0x1dd20:    je     0xb1dd92
>    0x1dd22:    mov    0x4bf1e0(%rip),%eax
>    0x1dd28:    cmp    $0xffffffff,%eax
>    0x1dd2b:    je     0xb1ddd0
>    0x1dd31:    test   %eax,%eax
>    0x1dd33:    jne    0xb1dd92
>    0x1dd35:    mov    0xe1f55c(%rip),%rax
>    0x1dd3c:    cmpq   $0x0,0xf0(%rax)
>    0x1dd44:    fildll 0xf0(%rax)
>    0x1dd4a:    js     0xb1ddf0
>    0x1dd50:    mov    0xe1f54a(%rip),%eax
>    0x1dd56:    mov    %rax,-0x80(%rsp)
>    0x1dd5b:    fildll -0x80(%rsp)
>    0x1dd5f:    fmulp  %st,%st(1)
> 
> Not sure if it helps but rax after 0xb1dd35 contains the pointer to
> mmap'd memory of /dev/hpet

I think this wouldn't work even with the latest kernel.  Emulation of
x87 instructions is not supported yet.

Paolo

  reply	other threads:[~2013-08-19  9:28 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-19  1:14 Emulation failure Duy Nguyen TN
2013-08-19  9:27 ` Paolo Bonzini [this message]
2013-08-20  1:26   ` Duy Nguyen TN
2013-08-20  8:16     ` Paolo Bonzini

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=5211E51D.8080009@redhat.com \
    --to=pbonzini@redhat.com \
    --cc=duy.nguyen@dektech.com.au \
    --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