From: Glauber Costa <glommer@redhat.com>
To: Consul <void@aleksoft.net>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Re: [PATCH] remove pieces of source code
Date: Fri, 29 May 2009 15:49:15 -0300 [thread overview]
Message-ID: <20090529184915.GB8897@poweredge.glommer> (raw)
In-Reply-To: <gvovqf$ifq$1@ger.gmane.org>
On Fri, May 29, 2009 at 08:43:09AM -0700, Consul wrote:
> Glauber Costa wrote:
>> But traffic in the mailing list indicates that it is less and less the case.
>> And more importantly: As it bitrots, nobody fixes it. so...
>>
>>> o There is no alternative for non-Linux users and folks with non-VT/SVM
>>> hardware
>>
>> Sure, but I don't think kqemu is such an alternative. ;-)
>
> It is. Without kqemu I'll have no alternative, but switch to VBox or VMWare.
> And none of them work with qcow images.
I'm not saying that because of any kind of functionality. I'm saying it is
not an alternative, because nobody really maintains it. It's bitrotting,
and unless someone wants to step up, soon or later you won't be able to use it
anyway.
next prev parent reply other threads:[~2009-05-29 18:44 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-28 23:03 [Qemu-devel] [PATCH] remove pieces of source code Glauber Costa
2009-05-29 5:50 ` Anthony Liguori
2009-05-29 9:08 ` [Qemu-devel] " Jan Kiszka
2009-05-29 9:12 ` Anthony Liguori
2009-05-29 9:35 ` Stefan Weil
2009-06-02 20:09 ` Stuart Brady
2009-06-02 20:29 ` Avi Kivity
2009-05-29 10:00 ` Daniel P. Berrange
2009-05-29 10:20 ` Jan Kiszka
2009-05-29 11:35 ` Glauber Costa
2009-05-30 18:04 ` François Revol
2009-05-31 9:13 ` Jan Kiszka
2009-05-31 14:53 ` Jamie Lokier
2009-05-31 15:43 ` Jan Kiszka
2009-05-29 11:32 ` [Qemu-devel] " Glauber Costa
2009-05-29 11:42 ` Gerd Hoffmann
2009-05-29 15:43 ` [Qemu-devel] " Consul
2009-05-29 18:49 ` Glauber Costa [this message]
2009-05-30 10:26 ` Andreas Färber
2009-05-31 9:15 ` Jan Kiszka
2009-05-31 13:08 ` Andreas Färber
2009-05-31 13:40 ` Avi Kivity
2009-05-31 16:20 ` M. Warner Losh
2009-05-31 15:10 ` Jan Kiszka
2009-06-06 10:17 ` Andreas Färber
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=20090529184915.GB8897@poweredge.glommer \
--to=glommer@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=void@aleksoft.net \
/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).