From: Jan Kiszka <jan.kiszka@siemens.com>
To: Dietmar Maurer <dietmar@proxmox.com>
Cc: "Mauerer, Wolfgang Ludwig" <wolfgang.mauerer@siemens.com>,
"kvm@vger.kernel.org" <kvm@vger.kernel.org>
Subject: Re: [PATCH 2/2] kvm-kmod: Document the build process
Date: Fri, 23 Oct 2009 09:50:11 +0200 [thread overview]
Message-ID: <4AE16033.5080906@siemens.com> (raw)
In-Reply-To: <90D306BE6EBC8D428A824FBBA7A3113D012F07D524@ronja.maurer-it.com>
Dietmar Maurer wrote:
>
>> -----Original Message-----
>> From: kvm-owner@vger.kernel.org [mailto:kvm-owner@vger.kernel.org] On
>> Behalf Of Wolfgang Mauerer
>> Sent: Mittwoch, 21. Oktober 2009 16:21
>> To: Dietmar Maurer
>> Cc: kvm@vger.kernel.org; Kiszka, Jan
>> Subject: Re: [PATCH 2/2] kvm-kmod: Document the build process
>>
>> Hio,
>>
>> Dietmar Maurer wrote:
>>>> + Before the kvm module can be built, the linux submodule must be
>>>> initialised
>>>> + and populated. The required sequence of commands is
>>>> +
>>>> + git submodule init
>>>> + git submodule update
>>>> + ./configure
>>>> + make sync
>>>> + make
>>>> +
>>>> + Notice that you can also specify an existing Linux tree for the
>>>> + synchronisation stage by using
>>>> +
>>>> + make sync LINUX=/path/to/tree
>>> I always get errors when i try to sync (with our Linux-2.6.24 tree)
>>>
>>> ./configure --kerneldir=${TOP}/linux-2.6.24-openvz
>>> make sync LINUX=${TOP}/linux-2.6.24-openvz
>>>
>>> make[1]: Entering directory `/a/dir/kvm-kmod-2.6.30.1'
>>> ./sync kvm-kmod-2.6.30.1
>>> Traceback (most recent call last):
>>> File "./sync", line 210, in <module>
>>> header_sync(arch)
>>> File "./sync", line 181, in header_sync
>>> hack(T, 'x86', 'include/linux/kvm.h')
>>> File "./sync", line 127, in hack
>>> _hack(T + '/' + file, arch)
>>> File "./sync", line 118, in _hack
>>> data = file(fname).read()
>>> IOError: [Errno 2] No such file or directory:
>> 'header/include/linux/kvm.h'
>>> make[1]: *** [sync] Error 1
>>>
>>> Any idea whats wrong?
>> Do you have a checked out Linux tree in linux-2.6/?
>
> Sorry, seem I am confused. You wrote
>
>>> + make sync LINUX=/path/to/tree
>
> So why do I need another linux tree? Can't we fix the 'sync' script?
There is nothing to fix. The sync script takes the KVM kernel module
sources from a recent kernel A and patch them so that kvm-kmod can build
them for an ancient kernel B.
Now you have two options where this kernel A could be located on sync:
by default (LINUX unset), it is in kvm-kmod/linux-2.6 (that git
submodule). Or you define a different local tree via
LINUX=/path/to/kernel/A - like above.
Jan
--
Siemens AG, Corporate Technology, CT SE 2
Corporate Competence Center Embedded Linux
next prev parent reply other threads:[~2009-10-23 7:50 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-20 12:11 [PATCH 1/2] kvm-kmod: Use the main development tree of kvm as Linux submodule wolfgang.mauerer
2009-10-20 12:11 ` [PATCH 2/2] kvm-kmod: Document the build process wolfgang.mauerer
2009-10-21 10:43 ` Dietmar Maurer
2009-10-21 14:20 ` Wolfgang Mauerer
2009-10-22 20:54 ` Dietmar Maurer
2009-10-23 7:50 ` Jan Kiszka [this message]
2009-11-12 17:35 ` [PATCH] kvm-kmod: Document the build process (take 2) Wolfgang Mauerer
2009-11-14 9:08 ` Jan Kiszka
2009-10-22 15:15 ` [PATCH 1/2] kvm-kmod: Use the main development tree of kvm as Linux submodule Avi Kivity
2009-10-22 16:13 ` Wolfgang Mauerer
2009-10-22 16:17 ` Avi Kivity
2009-10-22 16:25 ` Wolfgang Mauerer
2009-10-22 16:35 ` Avi Kivity
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=4AE16033.5080906@siemens.com \
--to=jan.kiszka@siemens.com \
--cc=dietmar@proxmox.com \
--cc=kvm@vger.kernel.org \
--cc=wolfgang.mauerer@siemens.com \
/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