From: Avi Kivity <avi@redhat.com>
To: Ross Boylan <ross@biostat.ucsf.edu>
Cc: kvm-devel <kvm@vger.kernel.org>
Subject: Re: kvm or qemu-kvm?
Date: Thu, 01 Oct 2009 19:02:28 +0200 [thread overview]
Message-ID: <4AC4E0A4.9090102@redhat.com> (raw)
In-Reply-To: <1254415862.15462.30.camel@corn.betterworld.us>
On 10/01/2009 06:51 PM, Ross Boylan wrote:
>>> So which file should I start from?
>>>
>>>
>> qemu-kvm is the userspace component, kvm-kmod is the kernel component as
>> an external module. 'kvm' is a package containing both.
>>
> That helps a lot; maybe that info could go up on the bugs or faq page.
> I couldn't find it (that is, there is info that there are kernel and
> user space components, but not how these relate to the tar files).
>
Yes, I plan on writing something up.
>> In general the best place to start is with the distro provided packages.
>>
>>
> My distro (Debian) is only at 85, even in unstable. Since it wasn't
> current, and also the dependencies will have wide effects on my system
> (which I'm trying to keep at the stable release Lenny), I figured
> getting the current source and building it myself would be the best
> move. For other reasons I'm already running a 2.6.30 kernel from
> Debian, which includes kernel side kvm. So I figure I only need to mess
> with user space.
>
Right, stick with your kernel's kvm.ko, qemu-kvm-0.11.0 should make a
good fit.
--
Do not meddle in the internals of kernels, for they are subtle and quick to panic.
next prev parent reply other threads:[~2009-10-01 17:03 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-30 2:21 kvm or qemu-kvm? Ross Boylan
2009-10-01 1:51 ` Charles Duffy
2009-10-01 15:56 ` Ross Boylan
2009-10-01 16:42 ` Avi Kivity
2009-10-01 16:51 ` Ross Boylan
2009-10-01 17:02 ` Avi Kivity [this message]
2009-10-10 16:28 ` René Pfeiffer
2009-10-10 17:03 ` Michael Tokarev
2009-10-01 18:06 ` Jim Paris
2009-10-01 18:35 ` Avi Kivity
2009-10-01 18:53 ` Jim Paris
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=4AC4E0A4.9090102@redhat.com \
--to=avi@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=ross@biostat.ucsf.edu \
/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).