From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1NYemW-0002NU-4e for qemu-devel@nongnu.org; Sat, 23 Jan 2010 07:08:00 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1NYemR-0002M5-Kc for qemu-devel@nongnu.org; Sat, 23 Jan 2010 07:07:59 -0500 Received: from [199.232.76.173] (port=47368 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1NYemR-0002M1-HW for qemu-devel@nongnu.org; Sat, 23 Jan 2010 07:07:55 -0500 Received: from mail-ew0-f227.google.com ([209.85.219.227]:35575) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1NYemQ-00043C-KE for qemu-devel@nongnu.org; Sat, 23 Jan 2010 07:07:55 -0500 Received: by ewy27 with SMTP id 27so2547991ewy.16 for ; Sat, 23 Jan 2010 04:07:51 -0800 (PST) MIME-Version: 1.0 In-Reply-To: References: <3b0605b31001210619v21c3ea0cvb6790addcfaf27a7@mail.gmail.com> Date: Sat, 23 Jan 2010 20:07:51 +0800 Message-ID: <3b0605b31001230407j73a9086cm2ba2893449b39c1d@mail.gmail.com> Subject: Re: [Qemu-devel] Luvalley-5 has been released (with whitepaper!): enables arbitrary OS to run VMs without any modification From: Xiaodong Yi Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Alexander Graf Cc: qemu-devel@nongnu.org Thanks for your advice. I'm now preparing to update the Qemu for Windows (not started yet). I originally though it should be better to use Qemu-KVM in Linux because, for example, Qemu-KVM supports SMP guests. I will review the newest Qemu version before updating Qemu for Linux. Regards, Xiaodong 2010/1/21 Alexander Graf : > > On 21.01.2010, at 15:19, Xiaodong Yi wrote: > >> Luvalley is a lightweight type-1 Virtual Machine Monitor (VMM). >> Its part of source codes are derived from KVM to virtualize >> CPU instructions and memory management unit (MMU). However, its >> overall architecture is completely different from KVM, but somewhat >> like Xen. Luvalley runs outside of Linux, just like Xen's architecture. >> Any operating system, including Linux, could be used as >> Luvalley's scheduler, memory manager, physical device driver provider >> and virtual IO device >> emulator. Currently, Luvalley supports Linux and Windows. That is to >> say, one may run Luvalley to boot a Linux or Windows, and then run >> multiple virtualized operating systems on such Linux or Windows. >> >> From the point of view of Qemu, Luvalley enables Qemu to utilize the >> Intel's VT extension to gain much better performance. >> >> If you are interested in Luvalley project, you may download the source >> codes as well as the whitepaper from >> =A0http://sourceforge.net/projects/luvalley/ >> >> The main changes of this release (Luvalley-5) are: >> >> * The code derived is updated from KVM-83 to KVM-88 > > It might be a better idea to use upstream kernel sources as basis. The KV= M snapshots are rather deprecated FWIW. > > Is the code to leverage Luvally vastly different from the accessors for K= VM? Maybe it'd be enough to have a wrapper for kvm_ioctl() that sends ioctl= s off to Luvally instead of KVM to make the existing infrastructure work. T= hat way upstream support should be a no-brainer and you get all the upstrea= m qemu work for free. > > Also, this would finally make the windows builds more useful again. > > Alex