Date: Wed, 05 Nov 2014 00:09:45 +0100 From: Nikos Vassiliadis <nvass@gmx.com> To: Allan Jude <allanjude@freebsd.org>, freebsd-virtualization@freebsd.org Subject: Re: VIMAGE and VirtualBox networking question Message-ID: <54595CB9.1050907@gmx.com> In-Reply-To: <54590971.9080800@freebsd.org> References: <5458F7ED.4030205@gmx.com> <54590971.9080800@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On 11/04/14 18:14, Allan Jude wrote: > The problem is likely that the virtualbox kernel modules needs to be > exactly in sync with your kernel. The official pkgs build against the > oldest version of the supported branch (10.0), so the module will > probably not work on 10.1. Since you are compiling a custom kernel, you > should probably build VirtualBox from source to get an exactly matched > kernel module, and see if that solves your issues. > > I just tried with GENERIC and everything works. I don't know why I expected a normal module to work with a VIMAGE kernel since VIMAGE modules are erm... virtualized:) What I really wonder now is whether I could somehow avoid having to install the ports tree for a single port. Something like, a package that contains the source of the VirtualBox module which one could build. Or virtualbox-ose-kmod-vnet package:) Thoughts?
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?54595CB9.1050907>