From: Paul Brook <paul@codesourcery.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Re: Cutting a new QEMU release
Date: Thu, 5 Feb 2009 16:27:21 +0000 [thread overview]
Message-ID: <200902051627.21972.paul@codesourcery.com> (raw)
In-Reply-To: <200902050936.49909.rickv@hobi.com>
On Thursday 05 February 2009, Rick Vernam wrote:
> On Thursday 05 February 2009 8:26:04 am Anthony Liguori wrote:
> > kqemu is unsupported and unmaintained.
>
> Interesting. When did it fall into that status?
IMHO It's pretty much always been that way.
> The Maintainers file shows Fabrice as the maintainer of kqemu. I suppose
> that needs to be updated?
>
> I see Fabrice released 1.4.0pre1 on May 30th, 2008, although I never did
> see anything declaring it unsupported (I'm not suggesting it was never
> declared, just that I never saw any such declaration).
>
> Are there any plans to support it in the future? This really is quite a
> shock to me, actually. I know qemu has a wide range of uses - but for me
> and surely others, virtualization is a primary use. To the best of my
> knowledge, kvm requires hardware support - where does this leave the class
> of users who need virtualization & don't have hardware virtualization
> support? Are we no longer the a target audience of qemu? If not, fine,
> but apparently a statement needs to be made...
You have the source, you're free to fork and maintain it yourself.
In practice Fabice is pretty much the only person who's ever done significant
work on kqemu (except maybe some fairly minor host OS porting bits). There's
never been a public source repository, so you get to use whatever random
tarballs Fabrice leaves lying around. If those don't work, noone really
cares.
Paul
next prev parent reply other threads:[~2009-02-05 16:27 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 [this message]
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
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=200902051627.21972.paul@codesourcery.com \
--to=paul@codesourcery.com \
--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).