From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1MCymP-0006n7-Fc for qemu-devel@nongnu.org; Sat, 06 Jun 2009 12:30:01 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1MCymK-0006mb-Oc for qemu-devel@nongnu.org; Sat, 06 Jun 2009 12:30:00 -0400 Received: from [199.232.76.173] (port=43341 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1MCymK-0006mY-Hi for qemu-devel@nongnu.org; Sat, 06 Jun 2009 12:29:56 -0400 Received: from mail-fx0-f219.google.com ([209.85.220.219]:52822) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1MCymK-0000Ma-8Q for qemu-devel@nongnu.org; Sat, 06 Jun 2009 12:29:56 -0400 Received: by fxm19 with SMTP id 19so1876828fxm.34 for ; Sat, 06 Jun 2009 09:29:55 -0700 (PDT) MIME-Version: 1.0 In-Reply-To: <4A2A92FE.2010700@redhat.com> References: <4A26F1E3.1040509@codemonkey.ws> <4A2A92FE.2010700@redhat.com> Date: Sat, 6 Jun 2009 19:29:55 +0300 Message-ID: Subject: Re: [Qemu-devel] POLL: Why do you use kqemu? From: Blue Swirl Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Avi Kivity Cc: =?UTF-8?Q?Andreas_F=C3=A4rber?= , "qemu-devel@nongnu.org" On 6/6/09, Avi Kivity wrote: > Andreas F=C3=A4rber wrote: > > > Or as another example, I've been unable to try KVM with svn/git QEMU > because new capability defines keep being added that block compiling QEMU > with KVM from any mainstream distribution. With nobody here being able to > recommend a working distribution, that makes KVM a moot alternative, > especially on systems you can't install your own kernel modules on. I jus= t > hope that Fedora 11 will let me try it. > > > > Try qemu-kvm.git, that should compile and run on almost anything (and is= a > lot faster and more featureful than kvm support in qemu.git). Maybe the backwards compatibility features should be ported to QEMU? For example, is there a workaround for #error Missing KVM capability KVM_CAP_DESTROY_MEMORY_REGION_WORKS ?