From owner-freebsd-virtualization@freebsd.org Fri Oct 23 04:11:52 2020 Return-Path: Delivered-To: freebsd-virtualization@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 2917E43C16E for ; Fri, 23 Oct 2020 04:11:52 +0000 (UTC) (envelope-from jtubnor@gmail.com) Received: from mail-wm1-f48.google.com (mail-wm1-f48.google.com [209.85.128.48]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1O1" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4CHW5M1hxBz4r0b for ; Fri, 23 Oct 2020 04:11:50 +0000 (UTC) (envelope-from jtubnor@gmail.com) Received: by mail-wm1-f48.google.com with SMTP id c77so8474wmd.4 for ; Thu, 22 Oct 2020 21:11:50 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=xTblUZ9E2SdQxy4nLuGg3GCS6EyACA5vU6UwS4URmWI=; b=KYYsTqCNJ0kVaG5hCsvuw6+96h02WvqXnc5axFvvUkuXGYG33R23yhAT+k2EecVq0g JH53rf5YiK2m02lx2R/3msKfKelg0CI2dAIselTdRAAw1BEBcOCSYlsVy8b+0fzzRkxR fZdVh+oqqC22av1ZGZnPahq8x/8WhJkkD3z9zxEZDmvNDcFYgDl5CgWQouSV58Fv8puj bIkcpJHPxj6N9Xadz5YNTh5LHThBq+s9xt4QL5brlLWoeWXDzgrGpNAS17WanRqC7EdJ Z+9KEJRfV1XbzY0PKShwW5VxH2THT13Kr521SmmNbtOA6q71eD7SY9UaIgT16MpRXYwb Xb7g== X-Gm-Message-State: AOAM5322je+hBfX5HzaogZjuqSBHRVLz1nd00VZdsyjyhuJRTwzjfDen s6QvoremI32Ac4Nbkrk2DApon2xvj3dTah/SReE= X-Google-Smtp-Source: ABdhPJy5kog5JH8idrtJ56yavtJtVXv+kbkgMwicHkJgxvzTKO5g/gfqtgIwkTmMYfhvONyrk3XfJ1nR90ib/tv+fkU= X-Received: by 2002:a1c:417:: with SMTP id 23mr233905wme.1.1603426309451; Thu, 22 Oct 2020 21:11:49 -0700 (PDT) MIME-Version: 1.0 References: <57c32e6d-5572-3d3b-1a57-f3064bee7dc2@druid.net> <20201020065630.GE8272@funkthat.com> <3ed627e2-d99a-107e-4135-8aef1ad4ec71@druid.net> <30A67F82-312E-4651-A5E7-2E2AD926FF24@punkt.de> <973b1b56-817f-6976-e5d3-34cfbc373b13@druid.net> <723CA318-80E9-4A6B-91ED-E791A40CC2C0@punkt.de> <6267599d-bc0c-6d63-bb19-1fc695e53997@druid.net> In-Reply-To: From: Jason Tubnor Date: Fri, 23 Oct 2020 15:11:39 +1100 Message-ID: Subject: Re: When is a switch not a switch? To: "D'Arcy Cain" Cc: "Patrick M. Hausen" , "freebsd-virtualization@freebsd.org" X-Rspamd-Queue-Id: 4CHW5M1hxBz4r0b X-Spamd-Bar: / Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=pass (mx1.freebsd.org: domain of jtubnor@gmail.com designates 209.85.128.48 as permitted sender) smtp.mailfrom=jtubnor@gmail.com X-Spamd-Result: default: False [-1.00 / 15.00]; ARC_NA(0.00)[]; TO_DN_EQ_ADDR_SOME(0.00)[]; RCVD_COUNT_TWO(0.00)[2]; RCVD_TLS_ALL(0.00)[]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_THREE(0.00)[3]; R_SPF_ALLOW(-0.20)[+ip4:209.85.128.0/17:c]; NEURAL_HAM_LONG(-0.97)[-0.967]; MIME_GOOD(-0.10)[multipart/alternative,text/plain]; PREVIOUSLY_DELIVERED(0.00)[freebsd-virtualization@freebsd.org]; DMARC_NA(0.00)[tubnor.net]; TO_DN_SOME(0.00)[]; SUBJECT_ENDS_QUESTION(1.00)[]; TO_MATCH_ENVRCPT_SOME(0.00)[]; NEURAL_HAM_SHORT(-0.09)[-0.086]; RCVD_IN_DNSWL_NONE(0.00)[209.85.128.48:from]; NEURAL_HAM_MEDIUM(-0.94)[-0.944]; FORGED_SENDER(0.30)[jason@tubnor.net,jtubnor@gmail.com]; RWL_MAILSPIKE_POSSIBLE(0.00)[209.85.128.48:from]; R_DKIM_NA(0.00)[]; FREEMAIL_ENVFROM(0.00)[gmail.com]; ASN(0.00)[asn:15169, ipnet:209.85.128.0/17, country:US]; MIME_TRACE(0.00)[0:+,1:+,2:~]; FROM_NEQ_ENVFROM(0.00)[jason@tubnor.net,jtubnor@gmail.com]; MAILMAN_DEST(0.00)[freebsd-virtualization] Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.33 X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.33 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, 23 Oct 2020 04:11:52 -0000 On Fri, 23 Oct 2020 at 01:03, D'Arcy Cain wrote: > > > > > > > tap0 is not a member of public so has no way to get to eth0 or public. > > Odd. I thought that vm-bhyve did that when the VM came up. > > Hmm. It looks like tap0 gets attached to vm-public if it is configured to > attach to public. Perhaps I just need to name the bridge that way. > If you create the virtual switch (bridge) for vm-bhyve using: vm switch create -b Then for the guest: vm add -d network -s When you start your guest up, it will attach to the existing bridge you defined in rc.conf, each time. > > > vm add -d network -s public > > Hard to automate when VM can migrate to another host. > > If both your hosts are configured using the same naming conventions for bridges and vm-bhyve switches, migration should be pretty simple and painless. Cheers, Jason.