Dietmar Maurer wrote: > >> -----Original Message----- >> From: kvm-owner@xxxxxxxxxxxxxxx [mailto:kvm-owner@xxxxxxxxxxxxxxx] On >> Behalf Of Wolfgang Mauerer >> Sent: Mittwoch, 21. Oktober 2009 16:21 >> To: Dietmar Maurer >> Cc: kvm@xxxxxxxxxxxxxxx; 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 -- To unsubscribe from this list: send the line "unsubscribe kvm" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html