From owner-freebsd-virtualization@FreeBSD.ORG  Wed Dec  3 15:11:00 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 7C0E6B36
 for <freebsd-virtualization@freebsd.org>; Wed,  3 Dec 2014 15:11:00 +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 3DA816CF
 for <freebsd-virtualization@freebsd.org>; Wed,  3 Dec 2014 15:11:00 +0000 (UTC)
Received: from john by potato.growveg.org with local (Exim 4.84 (FreeBSD))
 (envelope-from <john@potato.growveg.org>) id 1XwB0I-0005cn-Jv
 for freebsd-virtualization@freebsd.org; Wed, 03 Dec 2014 14:34:06 +0000
Date: Wed, 3 Dec 2014 14:34:06 +0000
From: John <freebsd-lists@potato.growveg.org>
To: freebsd-virtualization@freebsd.org
Subject: odd bhyve <-> ubuntu 14.04 problem
Message-ID: <20141203143406.GA29037@potato.growveg.org>
Reply-To: freebsd-lists@potato.growveg.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: Wed, 03 Dec 2014 15:11:00 -0000

Hello list,

I upgraded the host from freebsd-10-RC3 to 10.1-R and after that 
upgraded bhyve to grub2-bhyve-0.30 today and since then I've found that 
when booting ubuntu 14.04.1 LTS guests, the ethernet interface (ethN 
where N is a number) is now variable. This is an issue because if I stop 
a VM and say reboot the host, I have to hack about with the VM instead 
of just booting it.

Previously the VM always saw the virtual network interface as eth0. Now, 
it's anything but that. bhyve has been upgraded, the VM hasn't. How can 
I control this behaviour? I want eth0 to remain as eth0. These are all 
VMs that were eth0 before the bhyve upgrade. It doesn't appear to matter 
what tap interface is used. I don't have this issue with freebsd guests 
on the freebsd host, just ubuntu 14.04.1 LTS.

I define the bridge and 9 tap interfaces at boot, in case this is 
relevant. Please can anyone shed some light?

thanks,

-- 
John