From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1MCzkx-0007mi-UL for qemu-devel@nongnu.org; Sat, 06 Jun 2009 13:32:35 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1MCzkr-0007mR-TI for qemu-devel@nongnu.org; Sat, 06 Jun 2009 13:32:34 -0400 Received: from [199.232.76.173] (port=56882 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1MCzkr-0007mO-R9 for qemu-devel@nongnu.org; Sat, 06 Jun 2009 13:32:29 -0400 Received: from fmmailgate02.web.de ([217.72.192.227]:58172) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1MCzkr-0004ki-74 for qemu-devel@nongnu.org; Sat, 06 Jun 2009 13:32:29 -0400 Message-ID: <4A2AA829.9000907@web.de> Date: Sat, 06 Jun 2009 19:32:25 +0200 From: Jan Kiszka MIME-Version: 1.0 References: <4A26F1E3.1040509@codemonkey.ws> <4A2A92FE.2010700@redhat.com> <4A2AA10B.6060401@web.de> In-Reply-To: Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enig20EDBB74F976B878D2196F46" Sender: jan.kiszka@web.de Subject: [Qemu-devel] Re: POLL: Why do you use kqemu? List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Blue Swirl Cc: =?UTF-8?B?QW5kcmVhcyBGw6RyYmVy?= , Avi Kivity , "qemu-devel@nongnu.org" This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enig20EDBB74F976B878D2196F46 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Blue Swirl wrote: > On 6/6/09, Jan Kiszka wrote: >> Blue Swirl wrote: >> > 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 Q= EMU >> >> because new capability defines keep being added that block compili= ng QEMU >> >> with KVM from any mainstream distribution. With nobody here being = able to >> >> recommend a working distribution, that makes KVM a moot alternativ= e, >> >> especially on systems you can't install your own kernel modules on= =2E I just >> >> 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 >> > ? >> >> >> Given that we have always-up-to-date kvm-kmod packages with support do= wn >> to reasonable kernel versions, I would prefer to keep upstream clean >> from old workarounds. They should only be needed for issues found ver= y >> recently (KVM_CAP_JOIN_MEMORY_REGIONS_WORKS) or that might be found i= n >> the future. >=20 > But then I (and from Andreas' message I gather that many others) can't > test KVM support on QEMU without building, installing and maintaining > (updating, rebuilding, reinstalling etc) my own kernel instead of the > distro build. You don't have to, it builds against the distro kernel's devel package (I'm doing most KVM development on boring distro kernels). No black magic involved. Really. >=20 > Does this also mean that KVM stuff in QEMU releases will not be usable > for anyone (except those building their own kernels) until distros > upgrade to a compatible kernel version a few years later? In a year from now, you won't need any of todays workarounds on a then up-to-date distro kernel. And given that not only bug fixes come with kvm-kmod but also feature enhancements, updating the in-kernel kvm modules that way will likely remain a valid use case even after that poin= t. Jan --------------enig20EDBB74F976B878D2196F46 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org iEYEARECAAYFAkoqqCkACgkQniDOoMHTA+mwjwCfZonNmuOd2GwZvYq3YOb0q/uU Z2MAnRFeGquRCs9v7nkfJCGOYbPwr7B8 =Q4HG -----END PGP SIGNATURE----- --------------enig20EDBB74F976B878D2196F46--