From owner-freebsd-virtualization@FreeBSD.ORG Fri Jun 20 01:11:41 2014 Return-Path: Delivered-To: freebsd-virtualization@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 12ECA77F for ; Fri, 20 Jun 2014 01:11:41 +0000 (UTC) Received: from mailer.gewt.net (mailer.gewt.net [198.52.200.40]) (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 E6DCA2E3A for ; Fri, 20 Jun 2014 01:11:40 +0000 (UTC) Received: from adsl-75-49-4-163.dsl.wotnoh.sbcglobal.net ([75.49.4.163] helo=melanie.gimme-sympathy.org) by mailer.gewt.net with esmtpsa (TLSv1.2:DHE-RSA-AES256-GCM-SHA384:256) (Exim 4.82 (FreeBSD)) (envelope-from ) id 1WxqpX-000NQH-FY for freebsd-virtualization@freebsd.org; Fri, 20 Jun 2014 00:53:39 -0400 Date: Thu, 19 Jun 2014 20:51:01 -0400 (EDT) From: Cory Smelosky X-X-Sender: b4@melanie To: freebsd-virtualization@freebsd.org Subject: bhyve: vde2/openvswitch Message-ID: User-Agent: Alpine 2.10 (DEB 1266 2009-07-14) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; format=flowed; charset=US-ASCII Sender: b4@mailer.gewt.net X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.18 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: Fri, 20 Jun 2014 01:11:41 -0000 Hey all, Is there any current support for vde2 aside from using vde2_plug2tap? (Does that even work? I believe vde2 likes to open the tap interface exclusively. I need to bring up a bhyve test environment to check fully.) How exactly does the bhyve network stack work through bridging? I'm imaging it's tying in to bridging APIs? I'm assuming bhyve-to-bhyve network communication is also possible? I can't imagine it'd be too hard to implement vde2 support for networking...it'd give me more control over my VMs and give easier integration with SIMH VMs. OpenVSwitch I know less about...but I'm aware it is another virtual switch and it works on FreeBSD...not sure if it has a kernel module or if it's in userspace. With vde2 I know for sure it can be attached to a tap interface and therefore a bridge. A virtual switch for bhyve would be a useful feature if there aren't any plans for one. Get up there and have it in base. ;) Unrelated: any plans for a special bhyve-to-bhyve communication bus? Not too useful of a feature...I can't think of any use for it off-hand aside from dedicating a VM to administrating VMs without exposing much to the host beyond configurations. -- Cory Smelosky http://gewt.net Personal stuff