spectre-meltdown-checker VS vm-bhyve

I tried the latest SMC from https://github.com/speed47/spectre-meltdown-checker and all were in green. :-)

How is this project different spectre-meltdown-checker?

OpenBSD will disable all but the first thread on any Intel processor by default. I'm assuming that these models are too old to have microcode updates addressing the Spectre exploits (Meltdown, Foreshadow, Fallout, Zombieload, RIDL etc.), and disabling SMT/HT might be the most secure thing to do by default.

This script produces a good assessment of Spectre problems for a wide variety of CPUs. I know that they are difficult to exploit, and the mitigations are disabled by many because of their performance impact.

https://github.com/speed47/spectre-meltdown-checker

You can confirm the status of the mitigations using InSpectre for Windows, or Spectre & Meltdown Checker if you're on a unix based system.

You can run https://github.com/speed47/spectre-meltdown-checker

He's probably referring to the class of vulnerabilities checked by this script: https://github.com/speed47/spectre-meltdown-checker. It's not just Intel CPUs that were affected, AMD and ARM also have some vulnerabilities (I just ran it on an ARM v7 to see) although maybe not as many.

utilise microcode updates (should be by default, check)

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