From owner-freebsd-virtualization@FreeBSD.ORG Mon Feb 28 11:07:10 2011 Return-Path: Delivered-To: freebsd-virtualization@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B7CD910656DE for ; Mon, 28 Feb 2011 11:07:10 +0000 (UTC) (envelope-from owner-bugmaster@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id A4F248FC14 for ; Mon, 28 Feb 2011 11:07:10 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.4/8.14.4) with ESMTP id p1SB7Af4012132 for ; Mon, 28 Feb 2011 11:07:10 GMT (envelope-from owner-bugmaster@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.4/8.14.4/Submit) id p1SB7AWu012130 for freebsd-virtualization@FreeBSD.org; Mon, 28 Feb 2011 11:07:10 GMT (envelope-from owner-bugmaster@FreeBSD.org) Date: Mon, 28 Feb 2011 11:07:10 GMT Message-Id: <201102281107.p1SB7AWu012130@freefall.freebsd.org> X-Authentication-Warning: freefall.freebsd.org: gnats set sender to owner-bugmaster@FreeBSD.org using -f From: FreeBSD bugmaster To: freebsd-virtualization@FreeBSD.org Cc: Subject: Current problem reports assigned to freebsd-virtualization@FreeBSD.org X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Discussion of various virtualization techniques FreeBSD supports." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 28 Feb 2011 11:07:10 -0000 Note: to view an individual PR, use: http://www.freebsd.org/cgi/query-pr.cgi?pr=(number). The following is a listing of current problems submitted by FreeBSD users. These represent problem reports covering all versions including experimental development code and obsolete releases. S Tracker Resp. Description -------------------------------------------------------------------------------- a kern/152047 virtualization[vimage] [panic] TUN\TAP under jail with vimage crashe o kern/148155 virtualization[vimage] Kernel panic with PF/IPFilter + VIMAGE kernel a kern/147950 virtualization[vimage] [carp] VIMAGE + CARP = kernel crash s kern/143808 virtualization[pf] pf does not work inside jail a kern/141696 virtualization[rum] [panic] rum(4)+ vimage = kernel panic 5 problems total. From owner-freebsd-virtualization@FreeBSD.ORG Wed Mar 2 14:30:05 2011 Return-Path: Delivered-To: freebsd-virtualization@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 7ABC61065675; Wed, 2 Mar 2011 14:30:05 +0000 (UTC) (envelope-from jamesbrandongooch@gmail.com) Received: from mail-ww0-f50.google.com (mail-ww0-f50.google.com [74.125.82.50]) by mx1.freebsd.org (Postfix) with ESMTP id 7F2B38FC16; Wed, 2 Mar 2011 14:30:04 +0000 (UTC) Received: by wwb31 with SMTP id 31so29841wwb.31 for ; Wed, 02 Mar 2011 06:30:03 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=R6pLLF7I0TPlUtPWOge85d2mVPvAaLuFjl6qQY2IeqM=; b=Avlh5dt+PnKWxybdw4fj82qf79/+IpmHeAKsY9WO6LYCUVcd4H6mDyybWsZbDc2BhH 6M7THA1iWyvPc40KB2UPJhOt6LKSHPU4JuaaCUUzhATcAhqc/3jBcf7uVUVCadqkULj/ g4ZMMCdZiRvmuJWA38fYkXhn6Lvwu4Lz5N6Jc= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=sSi/+++a7NFhpPE9K2CxtBMSd/HZKE64FkCPcAxlFOgO0o3lM5KSeGCZSoXcXXsTRR urrJt50rwZH6Xr/Foki0TVnzfvKcGaUCOp5sicP4pJ4wF3DlZAIMIBmSEbODcbzPNSdK rpsU0PF2nyi56UKB0/eUmiz8/djXSOpCb/sG0= MIME-Version: 1.0 Received: by 10.216.158.21 with SMTP id p21mr684509wek.99.1299076202069; Wed, 02 Mar 2011 06:30:02 -0800 (PST) Received: by 10.216.25.72 with HTTP; Wed, 2 Mar 2011 06:30:01 -0800 (PST) In-Reply-To: References: <86oc77heqk.fsf@kopusha.home.net> <4D3D2DE9.2060004@freebsd.org> <86tygwy9p0.fsf@kopusha.home.net> <4D3F8357.2070005@freebsd.org> <62fcd16074e526547c3417a8f259174e@bluelife.at> <8662tbkahz.fsf@zhuzha.ua1> Date: Wed, 2 Mar 2011 08:30:01 -0600 Message-ID: From: Brandon Gooch To: Bernhard Froehlich Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: freebsd-emulation@freebsd.org, freebsd-virtualization@freebsd.org Subject: Re: VirtualBox + VIMAGE X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Discussion of various virtualization techniques FreeBSD supports." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 02 Mar 2011 14:30:05 -0000 On Wed, Jan 26, 2011 at 5:19 PM, Bernhard Froehlich wro= te: > On Wed, 26 Jan 2011 16:25:28 +0200, Mikolaj Golub wrote: >> On Wed, 26 Jan 2011 10:22:40 +0100 Bernhard Froehlich wrote: >> >> =A0BF> Sounds like it's my turn now. Which FreeBSD version is required t= o be >> =A0BF> able to use it? >> >> As Bjoern noted it is for __FreeBSD_version >=3D 800500. >> >> =A0BF> Is VIMAGE enabled per default and what happens if VIMAGE is disab= led - >> =A0BF> does it at least build fine with that patch? >> >> We have VIMAGE disabled by default. >> >> I have added to src/VBox/HostDrivers/VBoxNetFlt/freebsd/Makefile: >> >> .if defined(VIMAGE) >> =A0CFLAGS +=3D -DVIMAGE >> .endif >> >> So to build the driver for VIMAGE enabled kernel one should run >> >> VIMAGE=3D1 make >> >> If VIMAGE variable is not defined the module for VIMAGE disabled kernel = will >> be built. > > http://home.bluelife.at/patches/virtualbox-ose-kmod-devel-VIMAGE.diff > > I've integrated it a bit better into the VirtualBox build system, added > the ports stuff and updated the patch for VirtualBox 4.0.2. > > It is currently unclear to me why you add VIMAGE to CFLAGS but nowhere > check for VIMAGE in VBoxNetFlt-freebsd.c. Shouldn't we add a check for > VIMAGE in the #if defined line or is this already done somewhere deep in > the included headers? > > -- > Bernhard Froehlich > http://www.bluelife.at/ I managed to completely miss your patch posted this thread, so I just gave it a try on bluelife's virtualbox-ose-kmod svn r1239; it's working well. I've started each of my guests with bridged networking to be sure, and I see no panic (or any other anomaly) during boot or normal operation. Do you have plans on merging the patch soon? -Brandon From owner-freebsd-virtualization@FreeBSD.ORG Wed Mar 2 21:09:24 2011 Return-Path: Delivered-To: freebsd-virtualization@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 48B2E106566B; Wed, 2 Mar 2011 21:09:24 +0000 (UTC) (envelope-from jamesbrandongooch@gmail.com) Received: from mail-ww0-f50.google.com (mail-ww0-f50.google.com [74.125.82.50]) by mx1.freebsd.org (Postfix) with ESMTP id 8272E8FC0A; Wed, 2 Mar 2011 21:09:22 +0000 (UTC) Received: by wwb31 with SMTP id 31so582561wwb.31 for ; Wed, 02 Mar 2011 13:09:21 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=AOyttBJmy1w14LwlLMCPJfLgeMSdf9leztBQqbiokwg=; b=NUs12SANucMefDHc4O2TLeYgf4o2xHb+gtAqFzNsaSNFhCJL8cODdeqRK50YVhG4Wi GTlG6AQM/RBjopTJOsaC7XJXV7ua9BkbHXtu4MIMUViyKhQMbEJ1TIT59tYkSkKKdFmy lKadkZ31hu5FplZBL0Z+c4nmPvBFP5EA0Ou98= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=VuK2mXwV/DcaIOnNpTX9OAWKVJM/Q6+FP/bFg4mLQ+JUiyiN/v8iG0JdZ14LrLYzs5 O4BuZtQr1tktaWOiDwWeS51o/YFZQefvIrHXjnPoox01RfoKywcH9aOWceKj89/KdwYi mevpvBc7QGoXJjR9EnkEpR+u2diyKqrOfe1bc= MIME-Version: 1.0 Received: by 10.216.158.21 with SMTP id p21mr1071734wek.99.1299100161622; Wed, 02 Mar 2011 13:09:21 -0800 (PST) Received: by 10.216.25.72 with HTTP; Wed, 2 Mar 2011 13:09:21 -0800 (PST) In-Reply-To: <8b39481bb24314e2d543b7544f12a447@bluelife.at> References: <86oc77heqk.fsf@kopusha.home.net> <4D3D2DE9.2060004@freebsd.org> <86tygwy9p0.fsf@kopusha.home.net> <4D3F8357.2070005@freebsd.org> <62fcd16074e526547c3417a8f259174e@bluelife.at> <8662tbkahz.fsf@zhuzha.ua1> <4c9ee35c7798936a1e35259d72af781c@bluelife.at> <8b39481bb24314e2d543b7544f12a447@bluelife.at> Date: Wed, 2 Mar 2011 15:09:21 -0600 Message-ID: From: Brandon Gooch To: Bernhard Froehlich Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: freebsd-emulation@freebsd.org, freebsd-virtualization@freebsd.org Subject: Re: VirtualBox + VIMAGE X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Discussion of various virtualization techniques FreeBSD supports." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 02 Mar 2011 21:09:24 -0000 On Wed, Mar 2, 2011 at 2:52 PM, Bernhard Froehlich wrot= e: > On Wed, 02 Mar 2011 21:31:45 +0100, Bernhard Froehlich wrote: >> On Wed, 2 Mar 2011 08:30:01 -0600, Brandon Gooch wrote: >>> On Wed, Jan 26, 2011 at 5:19 PM, Bernhard Froehlich >>> wrote: >>>> On Wed, 26 Jan 2011 16:25:28 +0200, Mikolaj Golub wrote: >>>>> On Wed, 26 Jan 2011 10:22:40 +0100 Bernhard Froehlich wrote: >>>>> >>>>> =A0BF> Sounds like it's my turn now. Which FreeBSD version is require= d to be >>>>> =A0BF> able to use it? >>>>> >>>>> As Bjoern noted it is for __FreeBSD_version >=3D 800500. >>>>> >>>>> =A0BF> Is VIMAGE enabled per default and what happens if VIMAGE is di= sabled - >>>>> =A0BF> does it at least build fine with that patch? >>>>> >>>>> We have VIMAGE disabled by default. >>>>> >>>>> I have added to src/VBox/HostDrivers/VBoxNetFlt/freebsd/Makefile: >>>>> >>>>> .if defined(VIMAGE) >>>>> =A0CFLAGS +=3D -DVIMAGE >>>>> .endif >>>>> >>>>> So to build the driver for VIMAGE enabled kernel one should run >>>>> >>>>> VIMAGE=3D1 make >>>>> >>>>> If VIMAGE variable is not defined the module for VIMAGE disabled kern= el will >>>>> be built. >>>> >>>> http://home.bluelife.at/patches/virtualbox-ose-kmod-devel-VIMAGE.diff >>>> >>>> I've integrated it a bit better into the VirtualBox build system, adde= d >>>> the ports stuff and updated the patch for VirtualBox 4.0.2. >>>> >>>> It is currently unclear to me why you add VIMAGE to CFLAGS but nowhere >>>> check for VIMAGE in VBoxNetFlt-freebsd.c. Shouldn't we add a check for >>>> VIMAGE in the #if defined line or is this already done somewhere deep = in >>>> the included headers? >>>> >>>> -- >>>> Bernhard Froehlich >>>> http://www.bluelife.at/ >>> >>> I managed to completely miss your patch posted this thread, so I just >>> gave it a try on bluelife's virtualbox-ose-kmod svn r1239; it's >>> working well. I've started each of my guests with bridged networking >>> to be sure, and I see no panic (or any other anomaly) during boot or >>> normal operation. >>> >>> Do you have plans on merging the patch soon? >> >> It's not committed because it doesn't work. What i have tested so far >> is with stock 8.2-REL so without VIMAGE. >> >> enabled VIMAGE option on stock 8.2-REL: bridging works fine >> disabled VIMAGE option on stock 8.2-REL: crashes vm with an assert >> >> Expression: !pPatchToGuestRec >> Location =A0: >> /usr/home/decke/blueports/emulators/virtualbox-ose/work/VirtualBox-4.0.4= _OSE/src/VBox/VMM/VMMR3/PATM.cpp(116 >> 6) void patmr3AddP2GLookupRecord(VM*, _PATCHINFO*, uint8_t*, RTRCPTR, >> PATM_LOOKUP_TYPE, bool) > > It looks like that assert is not related to the VIMAGE patch. Works > fine now since half an hour. > >> Could someone with an VIMAGE kernel please test the patch? Just >> configure a VM with bridging and let it transfer a few bytes. Once with >> the option enabled and once disabled. I've had a machine running a linux guest for almost a day, bridging with a VIMAGE kernel, while capturing traffic on the virtual interface (and performing a few other tasks) -- so far, so good. No panics, and no anomalies. I surely don't know what the above mentioned assert is about; I haven't seen such a panic myself. -Brandon From owner-freebsd-virtualization@FreeBSD.ORG Wed Mar 2 20:46:53 2011 Return-Path: Delivered-To: freebsd-virtualization@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 6D81B106564A; Wed, 2 Mar 2011 20:46:53 +0000 (UTC) (envelope-from decke@bluelife.at) Received: from groupware.itac.at (groupware.itac.at [91.205.172.99]) by mx1.freebsd.org (Postfix) with ESMTP id 001A08FC0C; Wed, 2 Mar 2011 20:46:52 +0000 (UTC) Received: from home.bluelife.at (93.104.210.95) by groupware.itac.at (Axigen) with (AES256-SHA encrypted) ESMTPSA id 27CD35; Wed, 2 Mar 2011 21:33:01 +0100 MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Date: Wed, 02 Mar 2011 21:31:45 +0100 From: Bernhard Froehlich To: Brandon Gooch In-Reply-To: References: "<86oc77heqk.fsf@kopusha.home.net>" <4D3D2DE9.2060004@freebsd.org> "<86tygwy9p0.fsf@kopusha.home.net>" <4D3F8357.2070005@freebsd.org> "<62fcd16074e526547c3417a8f259174e@bluelife.at>" <8662tbkahz.fsf@zhuzha.ua1> Message-ID: <4c9ee35c7798936a1e35259d72af781c@bluelife.at> X-Sender: decke@bluelife.at User-Agent: Roundcube Webmail/0.5.1 X-AxigenSpam-Level: 1 X-CTCH-RefID: str=0001.0A0B0207.4D6EA931.0032,ss=1,fgs=0 X-CTCH-VOD: Unknown X-CTCH-Spam: Unknown X-Mailman-Approved-At: Wed, 02 Mar 2011 21:30:00 +0000 Cc: freebsd-emulation@freebsd.org, freebsd-virtualization@freebsd.org Subject: Re: VirtualBox + VIMAGE X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Discussion of various virtualization techniques FreeBSD supports." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 02 Mar 2011 20:46:53 -0000 On Wed, 2 Mar 2011 08:30:01 -0600, Brandon Gooch wrote: > On Wed, Jan 26, 2011 at 5:19 PM, Bernhard Froehlich > wrote: >> On Wed, 26 Jan 2011 16:25:28 +0200, Mikolaj Golub wrote: >>> On Wed, 26 Jan 2011 10:22:40 +0100 Bernhard Froehlich wrote: >>> >>>  BF> Sounds like it's my turn now. Which FreeBSD version is required to be >>>  BF> able to use it? >>> >>> As Bjoern noted it is for __FreeBSD_version >= 800500. >>> >>>  BF> Is VIMAGE enabled per default and what happens if VIMAGE is disabled - >>>  BF> does it at least build fine with that patch? >>> >>> We have VIMAGE disabled by default. >>> >>> I have added to src/VBox/HostDrivers/VBoxNetFlt/freebsd/Makefile: >>> >>> .if defined(VIMAGE) >>>  CFLAGS += -DVIMAGE >>> .endif >>> >>> So to build the driver for VIMAGE enabled kernel one should run >>> >>> VIMAGE=1 make >>> >>> If VIMAGE variable is not defined the module for VIMAGE disabled kernel will >>> be built. >> >> http://home.bluelife.at/patches/virtualbox-ose-kmod-devel-VIMAGE.diff >> >> I've integrated it a bit better into the VirtualBox build system, added >> the ports stuff and updated the patch for VirtualBox 4.0.2. >> >> It is currently unclear to me why you add VIMAGE to CFLAGS but nowhere >> check for VIMAGE in VBoxNetFlt-freebsd.c. Shouldn't we add a check for >> VIMAGE in the #if defined line or is this already done somewhere deep in >> the included headers? >> >> -- >> Bernhard Froehlich >> http://www.bluelife.at/ > > I managed to completely miss your patch posted this thread, so I just > gave it a try on bluelife's virtualbox-ose-kmod svn r1239; it's > working well. I've started each of my guests with bridged networking > to be sure, and I see no panic (or any other anomaly) during boot or > normal operation. > > Do you have plans on merging the patch soon? It's not committed because it doesn't work. What i have tested so far is with stock 8.2-REL so without VIMAGE. enabled VIMAGE option on stock 8.2-REL: bridging works fine disabled VIMAGE option on stock 8.2-REL: crashes vm with an assert Expression: !pPatchToGuestRec Location : /usr/home/decke/blueports/emulators/virtualbox-ose/work/VirtualBox-4.0.4_OSE/src/VBox/VMM/VMMR3/PATM.cpp(116 6) void patmr3AddP2GLookupRecord(VM*, _PATCHINFO*, uint8_t*, RTRCPTR, PATM_LOOKUP_TYPE, bool) Could someone with an VIMAGE kernel please test the patch? Just configure a VM with bridging and let it transfer a few bytes. Once with the option enabled and once disabled. -- Bernhard Fröhlich http://www.bluelife.at/ From owner-freebsd-virtualization@FreeBSD.ORG Wed Mar 2 20:52:14 2011 Return-Path: Delivered-To: freebsd-virtualization@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id CDE631065672; Wed, 2 Mar 2011 20:52:14 +0000 (UTC) (envelope-from decke@bluelife.at) Received: from groupware.itac.at (groupware.itac.at [91.205.172.99]) by mx1.freebsd.org (Postfix) with ESMTP id 5EEDE8FC1D; Wed, 2 Mar 2011 20:52:13 +0000 (UTC) Received: from home.bluelife.at (93.104.210.95) by groupware.itac.at (Axigen) with (AES256-SHA encrypted) ESMTPSA id 1AA1D3; Wed, 2 Mar 2011 21:53:29 +0100 MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Date: Wed, 02 Mar 2011 21:52:13 +0100 From: Bernhard Froehlich To: Bernhard Froehlich In-Reply-To: <4c9ee35c7798936a1e35259d72af781c@bluelife.at> References: "<86oc77heqk.fsf@kopusha.home.net>" <4D3D2DE9.2060004@freebsd.org> "<86tygwy9p0.fsf@kopusha.home.net>" <4D3F8357.2070005@freebsd.org> "<62fcd16074e526547c3417a8f259174e@bluelife.at>" <8662tbkahz.fsf@zhuzha.ua1> <4c9ee35c7798936a1e35259d72af781c@bluelife.at> Message-ID: <8b39481bb24314e2d543b7544f12a447@bluelife.at> X-Sender: decke@bluelife.at User-Agent: Roundcube Webmail/0.5.1 X-AxigenSpam-Level: 1 X-CTCH-RefID: str=0001.0A0B0203.4D6EADFD.0007,ss=1,fgs=0 X-CTCH-VOD: Unknown X-CTCH-Spam: Unknown X-Mailman-Approved-At: Wed, 02 Mar 2011 21:30:00 +0000 Cc: freebsd-emulation@freebsd.org, freebsd-virtualization@freebsd.org Subject: Re: VirtualBox + VIMAGE X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Discussion of various virtualization techniques FreeBSD supports." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 02 Mar 2011 20:52:15 -0000 On Wed, 02 Mar 2011 21:31:45 +0100, Bernhard Froehlich wrote: > On Wed, 2 Mar 2011 08:30:01 -0600, Brandon Gooch wrote: >> On Wed, Jan 26, 2011 at 5:19 PM, Bernhard Froehlich >> wrote: >>> On Wed, 26 Jan 2011 16:25:28 +0200, Mikolaj Golub wrote: >>>> On Wed, 26 Jan 2011 10:22:40 +0100 Bernhard Froehlich wrote: >>>> >>>>  BF> Sounds like it's my turn now. Which FreeBSD version is required to be >>>>  BF> able to use it? >>>> >>>> As Bjoern noted it is for __FreeBSD_version >= 800500. >>>> >>>>  BF> Is VIMAGE enabled per default and what happens if VIMAGE is disabled - >>>>  BF> does it at least build fine with that patch? >>>> >>>> We have VIMAGE disabled by default. >>>> >>>> I have added to src/VBox/HostDrivers/VBoxNetFlt/freebsd/Makefile: >>>> >>>> .if defined(VIMAGE) >>>>  CFLAGS += -DVIMAGE >>>> .endif >>>> >>>> So to build the driver for VIMAGE enabled kernel one should run >>>> >>>> VIMAGE=1 make >>>> >>>> If VIMAGE variable is not defined the module for VIMAGE disabled kernel will >>>> be built. >>> >>> http://home.bluelife.at/patches/virtualbox-ose-kmod-devel-VIMAGE.diff >>> >>> I've integrated it a bit better into the VirtualBox build system, added >>> the ports stuff and updated the patch for VirtualBox 4.0.2. >>> >>> It is currently unclear to me why you add VIMAGE to CFLAGS but nowhere >>> check for VIMAGE in VBoxNetFlt-freebsd.c. Shouldn't we add a check for >>> VIMAGE in the #if defined line or is this already done somewhere deep in >>> the included headers? >>> >>> -- >>> Bernhard Froehlich >>> http://www.bluelife.at/ >> >> I managed to completely miss your patch posted this thread, so I just >> gave it a try on bluelife's virtualbox-ose-kmod svn r1239; it's >> working well. I've started each of my guests with bridged networking >> to be sure, and I see no panic (or any other anomaly) during boot or >> normal operation. >> >> Do you have plans on merging the patch soon? > > It's not committed because it doesn't work. What i have tested so far > is with stock 8.2-REL so without VIMAGE. > > enabled VIMAGE option on stock 8.2-REL: bridging works fine > disabled VIMAGE option on stock 8.2-REL: crashes vm with an assert > > Expression: !pPatchToGuestRec > Location : > /usr/home/decke/blueports/emulators/virtualbox-ose/work/VirtualBox-4.0.4_OSE/src/VBox/VMM/VMMR3/PATM.cpp(116 > 6) void patmr3AddP2GLookupRecord(VM*, _PATCHINFO*, uint8_t*, RTRCPTR, > PATM_LOOKUP_TYPE, bool) It looks like that assert is not related to the VIMAGE patch. Works fine now since half an hour. > Could someone with an VIMAGE kernel please test the patch? Just > configure a VM with bridging and let it transfer a few bytes. Once with > the option enabled and once disabled. -- Bernhard Fröhlich http://www.bluelife.at/