From: "Roedel, Joerg" <Joerg.Roedel@amd.com>
To: Jamie Lokier <jamie@shareable.org>
Cc: Erik van der Kouwe <vdkouwe@cs.vu.nl>,
Jan Kiszka <jan.kiszka@web.de>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
Gleb Natapov <gleb@redhat.com>
Subject: Re: [Qemu-devel] Re: SVM emulation: EVENTINJ marked valid when a pagefault happens while issuing a software interrupt
Date: Fri, 28 May 2010 15:32:53 +0200 [thread overview]
Message-ID: <20100528133252.GA22539@amd.com> (raw)
In-Reply-To: <20100528132031.GG31920@shareable.org>
On Fri, May 28, 2010 at 09:20:31AM -0400, Jamie Lokier wrote:
> Roedel, Joerg wrote:
> > On Fri, May 28, 2010 at 02:10:59AM -0400, Jan Kiszka wrote:
> > > Erik van der Kouwe wrote:
> >
> > > > In my experience, if I provide the -enable-kvm switch then the guest VMM
> > > > never detects the presence of virtualization support. Does this only
> > > > work on AMD hardware? Or do I need to supply some additional parameter
> > > > to make it work?
> > >
> > > Yes, forgot to mention: -enable-nesting, and you need qemu-kvm. This
> > > feature hasn't been merged upstream yet.
> >
> > And the svm-emulation is only available on AMD hardware.
>
> I assume you mean nested SVM emulation in a KVM guest is only
> available on real AMD hardware?
Right.
> Is this due to something inherent, or just a limitation of the KVM
> code not handling all the necessary traps in kvm-intel?
The SVM and VMX extensions are architecturally very different in many
details. This makes it very hard to emulate VMX on SVM or vice verca. I
am not even sure if it is possible at all to emulate one extension in an
architectural complete way using the other extension.
Joerg
next prev parent reply other threads:[~2010-05-28 13:44 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-27 15:26 [Qemu-devel] SVM emulation: EVENTINJ marked valid when a pagefault happens while issuing a software interrupt Erik van der Kouwe
2010-05-27 18:53 ` [Qemu-devel] " Jan Kiszka
2010-05-27 19:49 ` Erik van der Kouwe
2010-05-27 22:20 ` Jan Kiszka
2010-05-28 5:13 ` Erik van der Kouwe
2010-05-28 6:10 ` Jan Kiszka
2010-05-28 7:35 ` Roedel, Joerg
2010-05-28 13:20 ` Jamie Lokier
2010-05-28 13:30 ` Erik van der Kouwe
2010-05-28 13:44 ` Roedel, Joerg
2010-05-28 13:52 ` Erik van der Kouwe
2010-05-28 13:32 ` Roedel, Joerg [this message]
2010-05-28 7:33 ` Roedel, Joerg
2010-05-28 7:47 ` Jan Kiszka
2010-05-28 7:24 ` Roedel, Joerg
2010-05-28 7:45 ` Erik van der Kouwe
2010-05-28 9:12 ` Roedel, Joerg
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=20100528133252.GA22539@amd.com \
--to=joerg.roedel@amd.com \
--cc=gleb@redhat.com \
--cc=jamie@shareable.org \
--cc=jan.kiszka@web.de \
--cc=qemu-devel@nongnu.org \
--cc=vdkouwe@cs.vu.nl \
/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.