From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1DgslI-0004Qf-A3 for qemu-devel@nongnu.org; Fri, 10 Jun 2005 19:18:04 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1DgslE-0004OO-Ts for qemu-devel@nongnu.org; Fri, 10 Jun 2005 19:18:01 -0400 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1DgslE-0004Li-HR for qemu-devel@nongnu.org; Fri, 10 Jun 2005 19:18:00 -0400 Received: from [64.5.53.22] (helo=www.cryptography.com) by monty-python.gnu.org with esmtp (TLS-1.0:DHE_RSA_3DES_EDE_CBC_SHA:24) (Exim 4.34) id 1Dgshm-0005NG-N4 for qemu-devel@nongnu.org; Fri, 10 Jun 2005 19:14:26 -0400 Message-ID: <42AA1DE7.6030400@root.org> Date: Fri, 10 Jun 2005 16:10:31 -0700 From: Nate Lawson MIME-Version: 1.0 References: <20050609173734.GA23989@intel.com> In-Reply-To: <20050609173734.GA23989@intel.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: [Qemu-devel] Re: Intel VMX support? Reply-To: qemu-devel@nongnu.org List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Arun Sharma Cc: qemu-devel@nongnu.org Arun Sharma wrote: > Nate Lawson wrote: > >>Have you considered adding support for this instruction set? >>http://cache-www.intel.com/cd/00/00/19/76/197666_197666.pdf > > It's not clear if you're trying to execute instructions such as VMREAD > inside qemu or use qemu's device models + VT-x (used to be called VMX) > for executing instructions. > > If it's the latter, the code is in xen-unstable now. Can boot Linux, > FreeBSD, MSDOS etc. > > We took a 0.6.1 snapshot and were able to run with very few modifications > to the "hw" directory. > > There were some discussions on where qemu should run on xen-devel (Look > for the thread "Device model architecture") > > The main changes we did were: > > - accelerate i8254 by moving parts into the hypervisor > - We had some hacks to run without the BIOS, but now that we have BIOS > support, these can go away. > > In general, we do have a desire to keep the tools/ioemu/hw directory in > Xen insync with the upstream qemu development. > > Comments/suggestions? No, just that I thought qemu could handle this on its own, separate from Xen. -- Nate