From owner-freebsd-virtualization@FreeBSD.ORG  Sun Oct 12 13:57:11 2014
Return-Path: <owner-freebsd-virtualization@FreeBSD.ORG>
Delivered-To: freebsd-virtualization@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115])
 (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by hub.freebsd.org (Postfix) with ESMTPS id 47CEE356
 for <freebsd-virtualization@freebsd.org>; Sun, 12 Oct 2014 13:57:11 +0000 (UTC)
Received: from potato.growveg.org (potato.growveg.org [62.49.247.163])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (Client did not present a certificate)
 by mx1.freebsd.org (Postfix) with ESMTPS id 059C0AE3
 for <freebsd-virtualization@freebsd.org>; Sun, 12 Oct 2014 13:57:10 +0000 (UTC)
Received: from john by potato.growveg.org with local (Exim 4.84 (FreeBSD))
 (envelope-from <john@potato.growveg.org>) id 1XdJM3-000AJr-ST
 for freebsd-virtualization@freebsd.org; Sun, 12 Oct 2014 14:38:35 +0100
Date: Sun, 12 Oct 2014 14:38:35 +0100
From: John <freebsd-lists@potato.growveg.org>
To: freebsd-virtualization@freebsd.org
Subject: no routing from new bhyve install
Message-ID: <20141012133835.GA39447@potato.growveg.org>
Reply-To: freebsd-virtualization@freebsd.org
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.5.23 (2014-03-12)
Sender: John <john@potato.growveg.org>
X-SA-Exim-Connect-IP: <locally generated>
X-SA-Exim-Mail-From: john@potato.growveg.org
X-SA-Exim-Scanned: No (on potato.growveg.org); SAEximRunCond expanded to false
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: Sun, 12 Oct 2014 13:57:11 -0000

Hello list,

I have a machine that runs virtualbox guests currently. I have read elsewhere 
that vbox and bhyve don't play well together, but that was a while ago, and 
it seemed only on some chipsets. Is this still the case?

The problem I'm having is, when trying bhyve, the installed instance boots 
etc and I can log into it from the host but I have no outside connectivity
from the guest. Ping 8.8.8.8 gives 'no route to host' yet route add default
(my_router_ip) shows my default gateway in the routing table. I have 
followed the steps here: https://www.freebsd.org/doc/handbook/virtualization-host-bhyve.html
setting up the host and the guest.

Is the problem because of virtualbox? If it is, will unloading the
vbox modules with kldunload fix this? If it has nothing to do with
vbox, what else can I check?

The host runs 10.1-RC2 #0 r272898 and the guest is 10.1-RC1 #0 r272463

thanks,
-- 
John