All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gleb Natapov <gleb@redhat.com>
To: Adhyas Avasthi <adhyas@gmail.com>
Cc: kvm@vger.kernel.org
Subject: Re: Issue with 64-bit code execution with kvm enabled
Date: Sun, 14 Nov 2010 08:59:51 +0200	[thread overview]
Message-ID: <20101114065951.GC7948@redhat.com> (raw)
In-Reply-To: <AANLkTinzP6ro+RSQUizds8XEWk84HP-L=s0ocpr6CO6w@mail.gmail.com>

On Sat, Nov 13, 2010 at 03:37:14PM -0800, Adhyas Avasthi wrote:
> I am trying to boot a 64-bit GRUB2 based EFI Boot Loader on top of
> OVMF based EFI BIOS (also 64 bit) for x86_64. My host is Ubuntu 10.04
> x86_64 and I am running qemu-kvm-0.13.0 with self-built
> kvm-kmod-2.6.32.17 for my kernel version which is 2.6.32-24 (I used
> the default Ubuntu KVM and qemu versions with same issue earlier). My
> host PC is Lenovo T410 with Intel Core i5
> 
> GRUB2 is built with gcc and apparently, EFI has a different calling
> convention so GRUB2 has an assembly wrapper file that changes the
> parameter as per desired calling convention. The problem is that if I
> start the loader with kvm disabled, everything goes fine and their
> wrapper instructions do the right thing as well. If I enable kvm,
> however, I get an x64 exception (as below):
> 
> !!!! X64 Exception Type - 000000000000000D !!!!
> ExceptionData - 0000000000000000
> RIP - 000000001FFA95FA, RFL - 0000000000010202
Can you disassemble code around the RIP?
Also provide ftrace of kvm execution during the failure.

--
			Gleb.

      parent reply	other threads:[~2010-11-14  6:59 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-13 23:37 Issue with 64-bit code execution with kvm enabled Adhyas Avasthi
2010-11-14  6:22 ` Adhyas Avasthi
2010-11-14  6:41   ` Adhyas Avasthi
2010-11-14  6:59 ` Gleb Natapov [this message]

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=20101114065951.GC7948@redhat.com \
    --to=gleb@redhat.com \
    --cc=adhyas@gmail.com \
    --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.