From owner-freebsd-current@freebsd.org Sun Jun 5 19:35:41 2016 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id A97D9B6B76E; Sun, 5 Jun 2016 19:35:41 +0000 (UTC) (envelope-from truckman@FreeBSD.org) Received: from gw.catspoiler.org (unknown [IPv6:2602:304:b010:ef20::f2]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "gw.catspoiler.org", Issuer "gw.catspoiler.org" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 87D5C1F6F; Sun, 5 Jun 2016 19:35:41 +0000 (UTC) (envelope-from truckman@FreeBSD.org) Received: from FreeBSD.org (mousie.catspoiler.org [192.168.101.2]) by gw.catspoiler.org (8.15.2/8.15.2) with ESMTP id u55JZTkV051689; Sun, 5 Jun 2016 12:35:33 -0700 (PDT) (envelope-from truckman@FreeBSD.org) Message-Id: <201606051935.u55JZTkV051689@gw.catspoiler.org> Date: Sun, 5 Jun 2016 12:35:29 -0700 (PDT) From: Don Lewis Subject: Re: VirtualBox network connectivity broken on recent -CURRENT To: mmacy@nextbsd.org, kib@FreeBSD.org cc: rwestlun@gmail.com, freebsd-current@FreeBSD.org, freebsd-emulation@FreeBSD.org In-Reply-To: <201606050629.u556SvjR049729@gw.catspoiler.org> MIME-Version: 1.0 Content-Type: TEXT/plain; charset=us-ascii X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 05 Jun 2016 19:35:41 -0000 On 4 Jun, To: mmacy@nextbsd.org wrote: > On 4 Jun, Matthew Macy wrote: >> >> >> >> ---- On Sat, 04 Jun 2016 19:04:42 -0700 Randy Westlund >> wrote ---- >> > On Fri, Jun 03, 2016 at 05:11:24PM -0700, Don Lewis wrote: >> > > It looks like something changed in -CURRENT to break network >> > > connectivity to VirtualBox guests. This was last known to work >> > > with r299139 (May 6th) and is definitely broken with r301229. >> > >> > I've been having VirtualBox networking problems as well. I can't >> > get my VMs on the network recently, but I don't recall when it >> > last worked. Everything looks right from the guest (the arp cache >> > shows the VirtualBox NAT router), but tcpdump on the host shows no >> > traffic. I haven't had time to investigate further :/ >> > >> >> The odds of it being fixed will increase greatly if someone would do a >> bisect and test. > > I started bisecting a bit earlier today. So far all I know is r300184 > is also broken. The culprit turned out to be r300043. There seems to be some sort of ABI compatiblity issue that was resolved when I rebuilt and reinstalled virtualbox-ose-kmod. There should probably be note in src/UPDATING if so. The .kmod files that I had been running were probably built with r299139. I used to have PORTS_MODULES=emulators/virtualbox-ose-kmod in /etc/make.conf, but took it out because pkg would also try to intall/upgrade it from my local pkg repo. What is strange is that the kmods would successfully load even on very recent kernels, but when I did a "pkg install -f virtualbox-ose-kmod" to fetch a recently rebuilt version (just a few days old), it would not load with a r300043 kernel. Is there a check to prevent a module with a newer version from loading on an older kernel, but not the reverse?