From: Avi Kivity <avi-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
To: Cam Macdonell <cam-edFDblaTWIyXbbII50Afww@public.gmane.org>
Cc: kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: kvm for Ubuntu 7.04 (was Re: a (bad) kvm story from a plain user)
Date: Thu, 16 Aug 2007 21:04:10 +0300 [thread overview]
Message-ID: <46C4919A.5050401@qumranet.com> (raw)
In-Reply-To: <46C46F98.9050406-edFDblaTWIyXbbII50Afww@public.gmane.org>
Cam Macdonell wrote:
> Avi Kivity wrote:
>> Jorge Lucángeli Obes wrote:
>>>> Thanks for the help, that compiled the userspace part. I need the
>>>> new
>>>> kernel module (kvm-intel.ko), can I take it from the kernel tree some
>>>> way or do I have to use the whole KVM kernel?
>>>>
>>> You should be able to compile it without having to compile the whole
>>> kernel. That's what one does with release versions, so it has to be
>>> possible. However, I've been working with the userspace part, so I've
>>> not yet tried it. Maybe someone else can comment? It's probably just
>>> Makefile dark magic.
>>>
>>>
>>
>> make -C kernel sync LINUX=/path/to/your/linux/repo
>>
> Hi Avi,
>
> If I run that in the userspace repo it moves some files but doesn't
> actually compile anything. Sorry to be dense about this, but are
> there any other steps?
>
./configure
make
--
Do not meddle in the internals of kernels, for they are subtle and quick to panic.
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
next prev parent reply other threads:[~2007-08-16 18:04 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-15 8:59 kvm for Ubuntu 7.04 (was Re: a (bad) kvm story from a plain user) Slohm Gadaburi
[not found] ` <f95a91fd0708150159kc74ddf3re7883f5d3e221d6b-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2007-08-15 9:12 ` Koen de Jonge (ProcoliX)
[not found] ` <46C2C392.1020104-OoqVcbiag8BWk0Htik3J/w@public.gmane.org>
2007-08-15 22:05 ` Cam Macdonell
[not found] ` <46C378C5.4040502-edFDblaTWIyXbbII50Afww@public.gmane.org>
2007-08-15 22:12 ` Jorge Lucángeli Obes
[not found] ` <59abf66e0708151512h7ae91c1ep85e859abc8160d33-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2007-08-15 22:30 ` Cam Macdonell
[not found] ` <46C37E7E.1090103-edFDblaTWIyXbbII50Afww@public.gmane.org>
2007-08-15 22:45 ` Jorge Lucángeli Obes
[not found] ` <59abf66e0708151545u148b9e96kf63ddeaaac578bfd-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2007-08-16 5:18 ` Avi Kivity
[not found] ` <46C3DE2F.4050805-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-08-16 15:39 ` Cam Macdonell
[not found] ` <46C46F98.9050406-edFDblaTWIyXbbII50Afww@public.gmane.org>
2007-08-16 18:04 ` Avi Kivity [this message]
2007-08-15 22:52 ` Luca
2007-08-16 6:13 ` Slohm Gadaburi
[not found] ` <f95a91fd0708152313w7a2fe56cha3b3f6cfe0798b94-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2007-08-16 6:27 ` Jorge Lucángeli Obes
[not found] ` <59abf66e0708152327x57b1b22fwfd259def52ea5463-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2007-08-16 6:42 ` Avi Kivity
2007-08-16 7:35 ` Koen de Jonge
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=46C4919A.5050401@qumranet.com \
--to=avi-atkuwr5tajbwk0htik3j/w@public.gmane.org \
--cc=cam-edFDblaTWIyXbbII50Afww@public.gmane.org \
--cc=kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.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