When is a switch not a switch?

[Jason Tubnor]

On Fri, 23 Oct 2020 at 01:03, D'Arcy Cain <darcy at druid.net> 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 <existing bridge name> <what vm-bhyve should know it as>

Then for the guest:

vm add -d network -s <what vm-bhyve should know it as> <guest name>

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 <guestname>
>
> 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.