From: Xiaodong Yi <xdong.yi@gmail.com>
To: Alexander Graf <agraf@suse.de>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Luvalley-5 has been released (with whitepaper!): enables arbitrary OS to run VMs without any modification
Date: Sat, 23 Jan 2010 20:07:51 +0800 [thread overview]
Message-ID: <3b0605b31001230407j73a9086cm2ba2893449b39c1d@mail.gmail.com> (raw)
In-Reply-To: <F5CFC5A8-F541-4BC7-9F20-7E35F028613F@suse.de>
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 <agraf@suse.de>:
>
> 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
>> http://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 KVM snapshots are rather deprecated FWIW.
>
> Is the code to leverage Luvally vastly different from the accessors for KVM? Maybe it'd be enough to have a wrapper for kvm_ioctl() that sends ioctls off to Luvally instead of KVM to make the existing infrastructure work. That way upstream support should be a no-brainer and you get all the upstream qemu work for free.
>
> Also, this would finally make the windows builds more useful again.
>
> Alex
next prev parent reply other threads:[~2010-01-23 12:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-21 14:19 [Qemu-devel] Luvalley-5 has been released (with whitepaper!): enables arbitrary OS to run VMs without any modification Xiaodong Yi
2010-01-21 15:06 ` Alexander Graf
2010-01-23 12:07 ` Xiaodong Yi [this message]
2010-01-23 12:21 ` Alexander Graf
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=3b0605b31001230407j73a9086cm2ba2893449b39c1d@mail.gmail.com \
--to=xdong.yi@gmail.com \
--cc=agraf@suse.de \
--cc=qemu-devel@nongnu.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).