From: Jan Kiszka <jan.kiszka@siemens.com>
To: Dietmar Maurer <dietmar@proxmox.com>
Cc: kvm <kvm@vger.kernel.org>
Subject: Re: [ANNOUNCE] kvm-kmod-2.6.31.5
Date: Wed, 28 Oct 2009 12:55:29 +0100 [thread overview]
Message-ID: <4AE83131.6020306@siemens.com> (raw)
In-Reply-To: <90D306BE6EBC8D428A824FBBA7A3113D012F07D55A@ronja.maurer-it.com>
Dietmar Maurer wrote:
>> This release has been tested on x86 down to host kernel 2.6.27 and
>> builds down to 2.6.24. Building against older kernels is expected to be
>> broken, but if anyone provides patches to fix it, I'm open to merge
>> them.
>
> I am still not able to build with our 2.6.24 kernel.
>
> ./sync -v kvm-kmod-2.6.31.5 -l /path/to/kernel/linux-2.6.24-openvz
> Traceback (most recent call last):
> File "./sync", line 247, in <module>
> header_sync(arch)
> File "./sync", line 219, in header_sync
> hack(T, arch, 'include/asm-%(arch)s/kvm.h' % { 'arch': arch })
> File "./sync", line 158, in hack
> _hack(T + '/' + file, arch)
> File "./sync", line 149, in _hack
> data = file(fname).read()
> IOError: [Errno 2] No such file or directory: 'header/include/asm-x86/kvm.h'
>
>
> The files required are simply not in the correct location. But it seem that make sync (after manually change paths and remove non-existing files) does not change a single file anyways for kernel 2.6.24?
>
> So I can simply skip 'make sync'?
The release tarball contains all required sources (as described, they
were obtained from 2.6.31.5). So you do have to sync, just run configure
&& make. And you definitely *must not* sync against 2.6.24 or any other
older kernel.
>
> But when I run make I get the following error:
>
> /home/dietmar/svn-devel/pve-kernel-2.6.24/kvm-kmod-2.6.31.5/x86/external-module-compat.h:93: error: redefinition of "native_read_tsc"
> include/asm/msr.h:230: error: previous definition of "native_read_tsc" was here
>
> if fact, it is defined in msr.h too:
>
> static inline unsigned long long native_read_tsc(void)
> {
> unsigned long long val;
>
> rdtsc_barrier();
> asm volatile("rdtsc" : "=A" (val));
> rdtsc_barrier();
>
> return val;
> }
>
> and in external-module-compat.h:
>
> static inline unsigned long long native_read_tsc(void)
> {
> unsigned long long val;
> asm volatile("rdtsc" : "=A" (val));
> return val;
> }
>
> And I compile on 64bit. So what is the correct version?
I'm running a 64-bit 2.6.24 kernel [1] against the stable branch, but I
may have missed some constellation. Please send me your .config
(provided you get this error with a clean kvm-kmod-2.6.31.5).
Jan
[1] http://buildbot.kiszka.org/kvm-kmod/waterfall?show=stable-2.6.31
--
Siemens AG, Corporate Technology, CT SE 2
Corporate Competence Center Embedded Linux
next prev parent reply other threads:[~2009-10-28 11:55 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-26 17:26 [ANNOUNCE] kvm-kmod-2.6.31.5 Jan Kiszka
2009-10-26 21:25 ` Alexander Graf
2009-10-27 8:25 ` Jan Kiszka
2009-10-27 10:39 ` Avi Kivity
2009-10-27 11:16 ` Jan Kiszka
2009-10-28 11:19 ` Dietmar Maurer
2009-10-28 11:55 ` Jan Kiszka [this message]
2009-10-28 12:15 ` Dietmar Maurer
2009-10-28 12:51 ` Jan Kiszka
2009-10-28 12:56 ` Dietmar Maurer
2009-10-28 17:24 ` Jan Kiszka
2009-10-29 8:11 ` Dietmar Maurer
2009-10-29 8:32 ` Jan Kiszka
[not found] ` <90D306BE6EBC8D428A824FBBA7A3113D012F07D55C@ronja.maurer-it.com>
2009-10-28 12:41 ` Jan Kiszka
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=4AE83131.6020306@siemens.com \
--to=jan.kiszka@siemens.com \
--cc=dietmar@proxmox.com \
--cc=kvm@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.