vm-bhyve VS runj

https://github.com/churchers/vm-bhyve/wiki/UEFI-Graphics-(VN...

Other than that, I use bhyve on my laptop daily since around 2015-2016. It was somewhat painful at first. I had to bake a CD key into Windows ISO for headless install but now VNC support exists and it's easy to output any graphical installer via VNC.

bhyve doesn't offer API and has not the most user-friendly interface (vm-bhyve[1] for the rescue!) but overall, I couldn't be happier with its - typical for FreeBSD - _set-and-forget_ stability.

[1] https://github.com/churchers/vm-bhyve

I am using FreeBSD in the workstation, I have both intel and realtek, and the main network uses the LAN interface, but I need the VLAN 20 to assign IPs from that range to some VMs (https://github.com/churchers/vm-bhyve/wiki/Virtual-Switches)

I want to assign IPs from VLAN 20 172.16.1.0/24 to VMs (https://github.com/churchers/vm-bhyve/wiki/Virtual-Switches) running on a host where main IP 192.168.1.10 is on the LAN network (no VLAN 20) this is the setup:

Sample config: https://github.com/churchers/vm-bhyve/blob/master/sample-tem...

I use Jails to run applications like Postgres, Redis, Python api in an isolated environment. Jails is native FreeBSD, but isolated.

Of what is properly supported, works beautifully and I have to say vm-bhyve is a joy to use. Everything is very cohesive and solid as a whole; I recommend it for servers but for GPU passthrough, only if you like a challenge.

I recommend to look into some third-party tooling to manage VMs. I prefer vm-bhyve, https://github.com/churchers/vm-bhyve

I was thinking opnsense + https://github.com/churchers/vm-bhyve to run a debian instance, which can then run everything in docker containers. It's inception but better utilization of all the services.

Perhaps it would! But the userbase is definitely what finally got me into FreeBSD. The fact that hobbyists were contributing such excellent cli tools as `iocage` [0] and `vm-bhyve` [1] really is what got me over my fears.

[0] https://iocage.io/

[1] https://github.com/churchers/vm-bhyve

a couple projects underway for containers, still wip but promising.

https://hackmd.io/7BIT_khIRQyPAe4EdiigHg

https://github.com/samuelkarp/runj

> it's a shame that docker is built around linux

There is some interesting work happening to get an OCI-compatible runtime working

https://github.com/samuelkarp/runj

So somebody else created runj (runj is an experimental, proof-of-concept OCI-compatible runtime for FreeBSD jails.) https://github.com/samuelkarp/runj

Shout out to https://github.com/samuelkarp/runj which aims to provide OCI compatible runtime for FreeBSD jails. We are working on a Jails based sandbox implementation for running OCaml builds on FreeBSD, https://github.com/ocurrent/obuilder. If runj gets more support then it would be a good alternative to the various iocage/ezjail/etc solutions or the raw Jails implementation we have right now.

If you want to get a little more bleeding edge, follow along with samuelkarp/runj project which attempts to get docker images running via runj/containerd

containerd only runs on FreeBSD with the help of a shim to use [runj](https://github.com/samuelkarp/runj) as a backend for running the actual jails containers.

> VM's disk is a zfs filesystem on the host, it makes snapshotting (edit- ok maybe not, see below) and managing it super easy!

I think you mean that it's a ZFS volume? Although it should be possible to export a filesystem to a guest over NFS (or I guess 9p), but I haven't run into a lot of discussion or gotten around to testing it myself...

> It would be really cool if there were tools that brought them in line with docker, in terms of easy deployment and provisioning of new jails/vms. If I didn't have so many damn project ideas already...

My dream would be to see https://github.com/samuelkarp/runj polished and docker+containerd+runj made to work as the way to run the docker frontend with jails as the backend.

https://github.com/samuelkarp/runj is a proof of concept.

Pull up your sleeves and start committing

Experimental FreeBSD on FreeBSD OCI containers with runj