From: Jan Kiszka <jan.kiszka@web.de>
To: Blue Swirl <blauwirbel@gmail.com>
Cc: "Andreas Färber" <andreas.faerber@web.de>,
"Avi Kivity" <avi@redhat.com>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>
Subject: [Qemu-devel] Re: POLL: Why do you use kqemu?
Date: Sat, 06 Jun 2009 19:32:25 +0200 [thread overview]
Message-ID: <4A2AA829.9000907@web.de> (raw)
In-Reply-To: <f43fc5580906061025p759404f4ma9326f0227636527@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2247 bytes --]
Blue Swirl wrote:
> On 6/6/09, Jan Kiszka <jan.kiszka@web.de> wrote:
>> Blue Swirl wrote:
>> > On 6/6/09, Avi Kivity <avi@redhat.com> wrote:
>> >> Andreas Färber 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 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 down
>> to reasonable kernel versions, I would prefer to keep upstream clean
>> from old workarounds. They should only be needed for issues found very
>> recently (KVM_CAP_JOIN_MEMORY_REGIONS_WORKS) or that might be found in
>> the future.
>
> 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.
>
> 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 point.
Jan
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 257 bytes --]
next prev parent reply other threads:[~2009-06-06 17:32 UTC|newest]
Thread overview: 57+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-03 21:57 [Qemu-devel] POLL: Why do you use kqemu? Anthony Liguori
2009-06-04 16:55 ` Anton D Kachalov
2009-06-05 0:44 ` Johannes Schindelin
2009-06-05 7:45 ` Gerd Hoffmann
2009-06-05 8:40 ` Tomasz Chmielewski
2009-06-05 9:08 ` Anton D Kachalov
2009-06-05 9:15 ` Gerd Hoffmann
2009-06-05 20:14 ` Lennart Sorensen
2009-06-05 23:23 ` Johannes Schindelin
2009-06-08 0:13 ` Jamie Lokier
2009-06-08 5:59 ` Avi Kivity
2009-06-08 11:57 ` Jamie Lokier
2009-06-08 12:03 ` Avi Kivity
2009-06-08 12:16 ` Jamie Lokier
2009-06-08 12:28 ` Avi Kivity
2009-06-08 12:44 ` [Qemu-devel] " Jan Kiszka
2009-06-08 13:06 ` Avi Kivity
2009-06-08 13:18 ` Jan Kiszka
2009-06-08 13:24 ` Avi Kivity
2009-06-08 13:44 ` Jan Kiszka
2009-06-08 14:03 ` Avi Kivity
2009-06-08 12:36 ` Jan Kiszka
2009-06-08 18:25 ` [Qemu-devel] " Lennart Sorensen
2009-06-06 13:27 ` Andreas Färber
2009-06-06 16:02 ` Avi Kivity
2009-06-06 16:29 ` Blue Swirl
2009-06-06 17:02 ` [Qemu-devel] " Jan Kiszka
2009-06-06 17:25 ` Blue Swirl
2009-06-06 17:32 ` Jan Kiszka [this message]
2009-06-06 19:15 ` Andreas Färber
2009-06-07 5:43 ` Avi Kivity
2009-06-07 5:01 ` Avi Kivity
2009-06-07 7:35 ` Jan Kiszka
2009-06-07 7:46 ` Avi Kivity
2009-06-07 8:33 ` Blue Swirl
2009-06-07 8:50 ` Jan Kiszka
2009-06-07 9:01 ` Blue Swirl
2009-06-07 9:25 ` Jan Kiszka
2009-06-07 9:37 ` Avi Kivity
2009-06-07 9:47 ` Jan Kiszka
2009-06-07 9:52 ` Avi Kivity
2009-06-07 9:56 ` Jan Kiszka
2009-06-07 10:06 ` Avi Kivity
2009-06-07 11:13 ` Blue Swirl
2009-06-07 11:23 ` Gleb Natapov
2009-06-07 11:26 ` Blue Swirl
2009-06-07 11:29 ` Gleb Natapov
2009-06-07 11:39 ` Avi Kivity
2009-06-07 12:40 ` Blue Swirl
2009-06-07 12:43 ` Avi Kivity
2009-06-07 12:52 ` Gleb Natapov
2009-06-07 12:56 ` Avi Kivity
2009-06-07 13:18 ` Blue Swirl
2009-06-07 13:35 ` Jan Kiszka
2009-06-07 13:35 ` Avi Kivity
2009-06-07 18:37 ` Anthony Liguori
2009-06-07 18:40 ` Blue Swirl
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=4A2AA829.9000907@web.de \
--to=jan.kiszka@web.de \
--cc=andreas.faerber@web.de \
--cc=avi@redhat.com \
--cc=blauwirbel@gmail.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).