Date: Mon, 20 Jun 2016 19:15:56 +0800 From: Julian Elischer <julian@freebsd.org> To: Kevin Oberman <rkoberman@gmail.com>, Guido Falsi <mad@madpilot.net> Cc: Rafael Rodrigues Nakano <mseqs@bsd.com.br>, FreeBSD Current <freebsd-current@freebsd.org> Subject: Re: Virtualbox kernel module on 11-CURRENT Message-ID: <0fdc268e-ab76-c589-f11f-69852ac7d57f@freebsd.org> In-Reply-To: <CAN6yY1tuTnbc8yxEH92q0B6=5755Q8cB=1-=dDE8m2aLw4LaeQ@mail.gmail.com> References: <CA%2B627Jrt6RTxgdm_14qbT_SQa9jjKH1NteV%2BxARJwazU0hgOzw@mail.gmail.com> <b39c2c66-c52b-1a2d-d3b5-eb961e9f54b9@madpilot.net> <CAN6yY1tuTnbc8yxEH92q0B6=5755Q8cB=1-=dDE8m2aLw4LaeQ@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 8/06/2016 5:13 AM, Kevin Oberman wrote: > On Tue, Jun 7, 2016 at 1:04 AM, Guido Falsi <mad@madpilot.net> wrote: > >> On 06/07/16 02:23, Rafael Rodrigues Nakano wrote: >>> Hello, >>> >>> I tried installing virtualbox from packages, building it from sources, >>> trying the GENERIC kernel but everytime I can't start the kernel module >>> 'vboxdrv', it says: >>> "KLD vboxdrv.ko: depends on kernel - not available or version mismatch. >>> linker_load_file: Unsupported file type" >>> >> The virtualbox module needs to be in full sync with the kernel. Most >> probably the sources being used by the cluster for building packages on >> head are a little different from yours, so the kernel module is not in >> sync. >> >> You will need to build the kernel module yourself to actually match your >> kernel sources. >> >> It's not really a problem or a bug, it's how it works. On head there is >> no warranty about the KBI. This cannot happen on releases and stable >> because the KBI is not going to change there. >> >> -- >> Guido Falsi <mad@madpilot.net> >> > I don't think this is true. While shareable libraries have fixed ABIs, I > believe the KBI can change even in STABLE branches. If a security fix > requires it, it might even change in a RELEASE. I my be wrong about this, > but I recall having to re-build the VB kmod port even withing a minor > version (i.e. STABLE). We try hard NOT to change the KBI within a single stable branch. we do things like add spare fields before we make a new stable branch to help with this. > In any case, I do strongly recommend the use of PORTS_MODULES in > /etc/src.conf to assure that the kernel modules always get re-built when > the kernel is re-built. so that the sources, the kernel, and the module are > in sync. The PORTS_MODULES are re-installed as a part of the "make > installkernel", so things are almost safe, but beware of "make > reinstallkernel" as it does not do the right thing. (See > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=201779) > -- > Kevin Oberman, Part time kid herder and retired Network Engineer > E-mail: rkoberman@gmail.com > PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683 > _______________________________________________ > freebsd-current@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?0fdc268e-ab76-c589-f11f-69852ac7d57f>