From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from [140.186.70.92] (port=60760 helo=eggs.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1OHzr8-0001sp-JJ for qemu-devel@nongnu.org; Fri, 28 May 2010 09:44:16 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.69) (envelope-from ) id 1OHzr6-0001jw-3F for qemu-devel@nongnu.org; Fri, 28 May 2010 09:44:09 -0400 Received: from va3ehsobe004.messaging.microsoft.com ([216.32.180.14]:22482 helo=VA3EHSOBE004.bigfish.com) by eggs.gnu.org with esmtp (Exim 4.69) (envelope-from ) id 1OHzr5-0001jj-Tw for qemu-devel@nongnu.org; Fri, 28 May 2010 09:44:08 -0400 Date: Fri, 28 May 2010 15:32:53 +0200 From: "Roedel, Joerg" Subject: Re: [Qemu-devel] Re: SVM emulation: EVENTINJ marked valid when a pagefault happens while issuing a software interrupt Message-ID: <20100528133252.GA22539@amd.com> References: <4BFE8F13.2000009@cs.vu.nl> <4BFEBF9E.90600@web.de> <4BFECCC3.2000806@cs.vu.nl> <4BFEF010.50300@web.de> <4BFF510B.9050508@cs.vu.nl> <4BFF5E73.70508@web.de> <20100528073531.GD3266@amd.com> <20100528132031.GG31920@shareable.org> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Disposition: inline In-Reply-To: <20100528132031.GG31920@shareable.org> List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Jamie Lokier Cc: Erik van der Kouwe , Jan Kiszka , "qemu-devel@nongnu.org" , Gleb Natapov 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