On 29/08/10 16:48, JD wrote:
> If I am currently booted in kernel version 2.6.33.X and I have
> multiple kernel
> versions installed.
>
> Running
> /etc/init.d/vboxdrv setup
> will build the modules for the current kernel.
>
> But what if I want to have it build the modules for 2.6.33.Z ?
>
> Is there a way to do that without having to boot kernel 2.6.33.Z ?
>
> I do have the source tree of 2.6.33.Z.
>
> Thanx!
>
>
> ------------------------------------------------------------------------------
> Sell apps to millions through the Intel(R) Atom(Tm) Developer Program
> Be part of this innovative community and reach millions of netbook users
> worldwide. Take advantage of special opportunities to increase revenue and
> speed time-to-market. Join now, and jumpstart your future.
> http://p.sf.net/sfu/intel-atom-d2d
> _______________________________________________
> VBox-users-community mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/vbox-users-community
>
>
JD,
Never tried it myself, but give it a go:
All info needed is available in scripts: /etc/init.d/vboxdrv; and a set
of scripts
you'll (probably) find as
/usr/share/virtualbox/src/vboxdrv/build_in_tmp
/usr/share/virtualbox/src/vboxnetflt/build_in_tmp
/usr/share/virtualbox/src/vboxnetadp/build_in_tmp
The scripts use constructs like `uname -r` in the command lines, so as to
adapt to the currently booted kernel; which then will result in commands
like :
make KBUILD_VERBOSE=1 -C /lib/modules/2.6.32-5-amd64/build
SUBDIRS=/tmp/vbox.0 SRCROOT=/tmp/vbox.0 modules
make -C /usr/src/linux-headers-2.6.32-5-amd64 \
KBUILD_SRC=/usr/src/linux-headers-2.6.32-5-common \
KBUILD_EXTMOD="/tmp/vbox.0" -f
/usr/src/linux-headers-2.6.32-5-common/Makefile \
modules.
I suggest you run following scripts (without changes yet, in the booted
kernel):
sh -x /usr/share/virtualbox/src/vboxdrv/build_in_tmp
sh -x /usr/share/virtualbox/src/vboxnetflt/build_in_tmp
sh -x /usr/share/virtualbox/src/vboxnetadp/build_in_tmp
Familiarise yourself with the outputs; then copy the scrips, as well as
vboxdrv
to a working directory, adapt the scripts to use variables pointing to
the source
tree (or at least, kernel headers) for a given target, and the correct
/lib/modules/<version>. Then rerun the process.
It might just work this way (though likely you'll need several tries
before it is
OK). And I suggest to run this on a system where no vbox guests are running
at the time.
Not a step-by-step recipe, but I think it is doable.
Hope this helps.
May be let us know how it went, if you'd decide to go this way?
------------------------------------------------------------------------------
This SF.net Dev2Dev email is sponsored by:
Show off your parallel programming skills.
Enter the Intel(R) Threading Challenge 2010.
http://p.sf.net/sfu/intel-thread-sfd
_______________________________________________
VBox-users-community mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/vbox-users-community
