From: lsorense@csclub.uwaterloo.ca (Lennart Sorensen)
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Luvalley-2 released: enable Qemu to utilize hardware virtualization extensions on arbitrary operating system
Date: Thu, 16 Apr 2009 09:59:25 -0400 [thread overview]
Message-ID: <20090416135925.GU3795@csclub.uwaterloo.ca> (raw)
In-Reply-To: <3b0605b30904151911q75f40283pd8225bb20b9be11@mail.gmail.com>
On Thu, Apr 16, 2009 at 10:11:51AM +0800, Xiaodong Yi wrote:
> Luvalley is a Virtual Machine Monitor (VMM) with the architecture
> somewhat like Xen. It runs below the operating system, and depends on
> Qemu to run multiple virtualized operating systems. Luvalley has the
> following distinguished features:
>
> * In theory, any operating system, e.g., Linux, Windows, BSD, etc.,
> could run on top of Luvalley to serve as its scheduler, memory
> manager and physical device driver provider. Luvalley needs no
> modification on such OS. Moreover, Luvalley takes over no hardware and
> device other than CPU and MMU. So it has rather good hardware
> compatibility.
>
> * Excellent cooperation with Qemu. Luvalley and Qemu could benefit
> each other. Qemu provides Luvalley an excellent virtual IO device
> emulator to run multiple virtualized operating systems simultaneously.
> And Luvalley enables Qemu to utilize hardware virtualization
> extensions on arbitrary operating system.
>
> If you are interested in Luvalley project, you may download Luvalley's
> source codes from
> http://sourceforge.net/projects/luvalley/
>
> This release (i.e., luvalley-2) updated Qemu in both Linux and
> Windows. So the limitations of the previous release (i.e., luvalley-1)
> have been partially eliminated. For example, the Qemu in Windows
> allows to create disk images and install gueest operating systems.
>
> This release has 4 tarballs:
>
> * luvalley-2.tgz: this is the source codes of the kernel part of
> Luvalley, which should be compiled in Linux. It is running below any
> operating system to provide virtualization extension for Intel's
> X86/32 computers. See the README file of the tarball for how to
> compile and run Luvalley.
>
> * qemu-linux.tgz: this is the source codes of the modified Qemu for
> running virtualized guest OSs in Linux. It is derived from Qemu of
> KVM-83. See the README file of the tarball for how to compile and run.
>
> * qemu-windows.tgz: this is the source codes of the modified Qemu for
> running virtualized guest OSs in Windows. It is derived from
> Qemu-0.10.2. See the README file of the tarball for how to build and
> run.
>
> * WindowsXP-Bins.rar: this is the pre-compiled binaries for running
> in Windows XP. It should be uncompressed in Windows XP operating
> system with WinRAR or other programs that supports .rar format. See
> the README file of the package for how to install and run in Windows
> XP.
You really should put some kind of version or date into your filenames.
It is very annoying later to try and figure out which version of a file
you have when the name is always the same.
--
Len Sorensen
next prev parent reply other threads:[~2009-04-16 13:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-16 2:11 [Qemu-devel] Luvalley-2 released: enable Qemu to utilize hardware virtualization extensions on arbitrary operating system Xiaodong Yi
2009-04-16 13:59 ` Lennart Sorensen [this message]
[not found] ` <20090416132654.GC24284@fries.net>
2009-04-17 8:40 ` Xiaodong Yi
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=20090416135925.GU3795@csclub.uwaterloo.ca \
--to=lsorense@csclub.uwaterloo.ca \
--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).