From owner-freebsd-virtualization@FreeBSD.ORG  Tue Nov  4 23:09:54 2014
Return-Path: <owner-freebsd-virtualization@FreeBSD.ORG>
Delivered-To: freebsd-virtualization@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by hub.freebsd.org (Postfix) with ESMTPS id 3CAE4602;
 Tue,  4 Nov 2014 23:09:54 +0000 (UTC)
Received: from mout.gmx.net (mout.gmx.net [212.227.15.15])
 (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (Client CN "mout.gmx.net", Issuer "TeleSec ServerPass DE-1" (verified OK))
 by mx1.freebsd.org (Postfix) with ESMTPS id CCECAE82;
 Tue,  4 Nov 2014 23:09:53 +0000 (UTC)
Received: from portis.head.local ([109.193.229.18]) by mail.gmx.com (mrgmx002)
 with ESMTPSA (Nemesis) id 0MSMKx-1Xb1rm2cKB-00TRH3;
 Wed, 05 Nov 2014 00:09:45 +0100
Message-ID: <54595CB9.1050907@gmx.com>
Date: Wed, 05 Nov 2014 00:09:45 +0100
From: Nikos Vassiliadis <nvass@gmx.com>
User-Agent: Mozilla/5.0 (X11; FreeBSD amd64;
 rv:31.0) Gecko/20100101 Thunderbird/31.2.0
MIME-Version: 1.0
To: Allan Jude <allanjude@freebsd.org>, 
 freebsd-virtualization@freebsd.org
Subject: Re: VIMAGE and VirtualBox networking question
References: <5458F7ED.4030205@gmx.com> <54590971.9080800@freebsd.org>
In-Reply-To: <54590971.9080800@freebsd.org>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
X-Provags-ID: V03:K0:HTzXKAk5lSYpvC1hf/mSrOCovu3p72yM5Qic53/mPSJAhZmjXeT
 JRcenXqV8YNejdJUFSPesHP6gtM/MU9LYDp8/jtN5//UTxwaJG0dO3AEjHP9ydqM8HTr9bA
 pvmjby+OY1d3jY5WEWIGo6k9HztZcIWdSCnSXFHgybWihr2HQUGpPBXNggeTjXRfvzOK5nf
 shg0JZMqcohgvfURFHfOQ==
X-UI-Out-Filterresults: notjunk:1;
X-BeenThere: freebsd-virtualization@freebsd.org
X-Mailman-Version: 2.1.18-1
Precedence: list
List-Id: "Discussion of various virtualization techniques FreeBSD supports."
 <freebsd-virtualization.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-virtualization>, 
 <mailto:freebsd-virtualization-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-virtualization/>
List-Post: <mailto:freebsd-virtualization@freebsd.org>
List-Help: <mailto:freebsd-virtualization-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization>, 
 <mailto:freebsd-virtualization-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 04 Nov 2014 23:09:54 -0000

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?