From owner-freebsd-virtualization@freebsd.org  Mon Oct 15 16:06:07 2018
Return-Path: <owner-freebsd-virtualization@freebsd.org>
Delivered-To: freebsd-virtualization@mailman.ysv.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1])
 by mailman.ysv.freebsd.org (Postfix) with ESMTP id 4B96B10B767B
 for <freebsd-virtualization@mailman.ysv.freebsd.org>;
 Mon, 15 Oct 2018 16:06:07 +0000 (UTC)
 (envelope-from bzeeb-lists@lists.zabbadoz.net)
Received: from mx1.sbone.de (mx1.sbone.de [IPv6:2a01:4f8:13b:39f::9f:25])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (Client CN "mx1.sbone.de", Issuer "SBone.DE" (not verified))
 by mx1.freebsd.org (Postfix) with ESMTPS id DE43A79FBD
 for <freebsd-virtualization@freebsd.org>; Mon, 15 Oct 2018 16:06:06 +0000 (UTC)
 (envelope-from bzeeb-lists@lists.zabbadoz.net)
Received: from mail.sbone.de (mail.sbone.de [IPv6:fde9:577b:c1a9:31::2013:587])
 (using TLSv1 with cipher ADH-CAMELLIA256-SHA (256/256 bits))
 (No client certificate requested)
 by mx1.sbone.de (Postfix) with ESMTPS id B7FEA8D4A213
 for <freebsd-virtualization@freebsd.org>; Mon, 15 Oct 2018 16:05:57 +0000 (UTC)
Received: from content-filter.sbone.de (content-filter.sbone.de
 [IPv6:fde9:577b:c1a9:31::2013:2742])
 (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by mail.sbone.de (Postfix) with ESMTPS id C22AFD1F855
 for <freebsd-virtualization@freebsd.org>; Mon, 15 Oct 2018 16:05:56 +0000 (UTC)
X-Virus-Scanned: amavisd-new at sbone.de
Received: from mail.sbone.de ([IPv6:fde9:577b:c1a9:31::2013:587])
 by content-filter.sbone.de (content-filter.sbone.de
 [fde9:577b:c1a9:31::2013:2742]) (amavisd-new, port 10024)
 with ESMTP id hEe1a4z8MAVj for <freebsd-virtualization@freebsd.org>;
 Mon, 15 Oct 2018 16:05:55 +0000 (UTC)
Received: from [10.248.98.63] (fresh-ayiya.sbone.de
 [IPv6:fde9:577b:c1a9:f001::2])
 (using TLSv1 with cipher AES256-SHA (256/256 bits))
 (No client certificate requested)
 by mail.sbone.de (Postfix) with ESMTPSA id 7C3B3D1F84E
 for <freebsd-virtualization@freebsd.org>; Mon, 15 Oct 2018 16:05:55 +0000 (UTC)
From: "Bjoern A. Zeeb" <bzeeb-lists@lists.zabbadoz.net>
To: "FreeBSD virtualization mailing list" <freebsd-virtualization@freebsd.org>
Subject: bhyve on reboot loses tap(4) configuration
Date: Mon, 15 Oct 2018 16:05:54 +0000
X-Mailer: MailMate (2.0BETAr6123)
Message-ID: <02210D52-A45B-4E54-BCEE-EC61026B70C0@lists.zabbadoz.net>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
X-BeenThere: freebsd-virtualization@freebsd.org
X-Mailman-Version: 2.1.27
Precedence: list
List-Id: "Discussion of various virtualization techniques FreeBSD supports."
 <freebsd-virtualization.freebsd.org>
List-Unsubscribe: <https://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: <https://lists.freebsd.org/mailman/listinfo/freebsd-virtualization>, 
 <mailto:freebsd-virtualization-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 15 Oct 2018 16:06:07 -0000

Hi,

I tried to use bhyve with the tap(4)/vtnet(4) solution as documented in 
the handbook (tap needs autoopen).
However, I am using no bridge(4) interface but a “point-to-point” 
configuration.

Example:
guest configures vtnet0 to 192.0.2.2/24
host configures tap0 to 192.0.2.1/24

When rebooting the guest inside the bhyve, it seems bhyve loses the 
outside tap0 configuration.  I assume that is because the tap0 interface 
is closed and re-opened on the “warm restart”.

Apart from using devd and possibly tracking tap interfaces to come up 
and track things there, is there are better solution for not having to 
reconfigure the host interface on every guest reboot?


/bz