From: Stefan Weil <weil@mail.berlios.de>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Re: Cutting a new QEMU release
Date: Sat, 07 Feb 2009 13:01:59 +0100 [thread overview]
Message-ID: <498D7837.1090803@mail.berlios.de> (raw)
In-Reply-To: <498AF6FC.90803@codemonkey.ws>
Anthony Liguori schrieb:
>
> kqemu is unsupported and unmaintained.
>
> Regards,
>
> Anthony Liguori
>
The kvm kernel module could be a good replacement for kqemu
for those running linux on new cpus.
It does not play this role in current linux distributions because
you will need newer versions of kvm which are sometimes
difficult to compile.
It will never play this role for those running "old" cpus.
And it will never play this role on Windows (or is there a kvm
for Windows?). I am surprised that nobody mentions this part
in the discussion.
So even if kqemu is unmaintained, the Qemu developers
should at least maintain the interface.
I'd prefer to have a svn tree with kqemu beside qemu.
Then patches could be sent, and maybe some day there could
be a maintainer, too.
Integration of code from virtualbox could be a way to replace
kqemu, but I don't see this coming in the near future.
Regards
Stefan Weil
next prev parent reply other threads:[~2009-02-07 12:02 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-05 9:13 [Qemu-devel] Re: Cutting a new QEMU release Steve Fosdick
2009-02-05 14:26 ` Anthony Liguori
2009-02-05 15:36 ` Rick Vernam
2009-02-05 16:27 ` Paul Brook
2009-02-05 17:15 ` René Rebe
2009-02-05 17:36 ` Paul Brook
2009-02-05 17:51 ` Daniel P. Berrange
2009-02-05 17:51 ` Ben Taylor
2009-02-05 18:39 ` René Rebe
2009-02-05 19:03 ` Anthony Liguori
2009-02-06 10:54 ` Steve Fosdick
2009-02-06 15:57 ` René Rebe
2009-02-06 17:12 ` Anthony Liguori
2009-02-06 21:47 ` René Rebe
2009-02-07 16:49 ` Jamie Lokier
2009-02-07 17:06 ` Laurent Desnogues
2009-02-07 23:46 ` Anthony Liguori
2009-02-06 21:53 ` René Rebe
2009-02-07 16:39 ` Jamie Lokier
[not found] ` <92CAE88C-36FF-4566-BD1D-ACA58C98CB0F@hotmail.com>
2009-02-09 5:01 ` C.W. Betts
[not found] ` <784D2534-F9CD-4EA5-BBEE-67E9DE196598@hotmail.com>
2009-02-09 5:42 ` C.W. Betts
2009-02-09 10:29 ` René Rebe
2009-02-15 15:25 ` Andreas Färber
2009-02-15 15:44 ` Jamie Lokier
2009-02-15 19:14 ` Andreas Färber
2009-02-15 18:17 ` Anthony Liguori
2009-02-15 20:31 ` Andreas Färber
2009-02-05 15:55 ` René Rebe
2009-02-07 12:01 ` Stefan Weil [this message]
2009-02-07 15:08 ` Anthony Liguori
2009-02-07 15:36 ` Jamie Lokier
2009-02-07 16:45 ` Jan Kiszka
2009-02-05 14:55 ` Rick Vernam
-- strict thread matches above, loose matches on Subject: below --
2009-02-03 20:48 [Qemu-devel] " Anthony Liguori
2009-02-04 14:50 ` Aurelien Jarno
2009-02-04 15:23 ` Tristan Gingold
2009-02-04 15:43 ` Lennart Sorensen
2009-02-04 16:01 ` Tristan Gingold
2009-02-04 18:17 ` [Qemu-devel] " Consul
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=498D7837.1090803@mail.berlios.de \
--to=weil@mail.berlios.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).