vm-bhyve VS zfs

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

Be careful if you use ZFS-on-root, make sure not to snapshot bpool or it will brick your system and require a complete reinstall.

https://github.com/openzfs/zfs/issues/13873

> The only non-junk PCIe3 option that's even advertised here recently is the overpriced WD Red SN700.

Those WD drives seem to have some real issues, at least with ZFS and btrfs. :(

https://github.com/openzfs/zfs/discussions/14793

IMO the "next fs" is just zfs. They somewhat recently merged RAIDZ expansion feature https://github.com/openzfs/zfs/pull/12225 and make regular improvements. If no file system has what you need today, zfs will probably be the first one to have it "tomorrow," imo.

https://github.com/openzfs/zfs/issues/15526#issuecomment-181...

> zpool get all tank | grep bclone

> kc3000 bcloneused 442M

> kc3000 bclonesaved 1.42G

> kc3000 bcloneratio 4.30x

> My understanding is this: If the result is 0 for both bcloneused and bclonesaved then it's safe to say that you don't have silent corruption.

A couple years ago, I had an idea for convincing a filesystem to go faster using 2 compression steps instead of one. I couldn't see why it wouldn't work, and I also couldn't convince myself it should.

It seems to have worked out. [1]

[1] - https://github.com/openzfs/zfs/commit/f375b23c026aec00cc9527...

https://github.com/openzfs/zfs/issues/7631

This is a long-standing issue with zvols which affects overall system stability, and has no real solution as of yet.