Freebsd 14.3

[simmerskool]

I installed & configured FreeBSD 14.3 in VMware & updated to P9 and installation / config was somewhat tedious, but once up & running it is smooth fast light. I am liking it much more than I thought I would. ChatGPT 5.4 Thinking was helpful or I might have given up and now glad that I pushed thru. ChatGPT says install goes better with VirtualBox.

 

[Bot]

I installed & configured FreeBSD 14.3 in VMware & updated to P9 and installation / config was somewhat tedious, but once up & running it is smooth fast light. I am liking it much more than I thought I would. ChatGPT 5.4 Thinking was helpful or I might have given up and now glad that I pushed thru. ChatGPT says install goes better with VirtualBox.

Nice outcome. FreeBSD can feel a bit “hands-on” during install/config (especially around networking, partitions, and guest integration), but once it’s set up it tends to be very stable and efficient—so what you’re seeing is consistent with how many people experience it.

VMware vs VirtualBox: why one can feel “easier”

It’s hard to state universally that FreeBSD “installs better” on one hypervisor than the other, but there are a few practical reasons people sometimes report a smoother first run on VirtualBox:

• Guest additions and defaults: VirtualBox often presents “safe” legacy-style virtual hardware by default (e1000 NIC, AHCI storage, etc.), which FreeBSD supports well out of the box.
• VMware device choices matter more: On VMware, choosing the right virtual NIC/storage controller can make the difference between “works instantly” and “needs a bit of driver/loader tuning.”
• Documentation/community recipes: There are lots of copy/paste “known good” VirtualBox recipes for FreeBSD, so it can feel more straightforward even when VMware would work equally well once configured.

If your FreeBSD 14.3 VM is already “smooth fast light” on VMware, that’s a good sign your virtual hardware choices are fine.

Tips to keep VMware FreeBSD guests stable and performant

• Prefer paravirtualized devices when supported: If your VMware version offers them reliably for FreeBSD, VirtIO-style devices (where available) can improve performance. If switching controllers/NICs, do it carefully to avoid boot/network surprises.
• Timekeeping and tools: If you see clock drift or odd input/console behavior, installing the appropriate VMware guest utilities (where available for FreeBSD) can help. Some setups run perfectly fine without them, but tools can improve integration.
• Snapshots and updates: Before major FreeBSD updates or bootloader changes, take a snapshot. It’s the quickest rollback if a config tweak goes sideways.

Security note for new FreeBSD installs

Even in a VM, it’s worth doing a quick hardening pass after you’re “happy with it”:

• Apply base updates (which you’ve done via patchlevel updates) and keep pkg packages updated.
• Disable services you don’t use and confirm only expected ports are listening.
• If the VM will touch untrusted content, consider using snapshots and keeping shared folders/clipboard integration to the minimum you need.

Bottom line: VirtualBox can feel easier largely due to default virtual hardware choices and common recipes, but VMware can run FreeBSD extremely well once dialed in—your current experience suggests you’ve already crossed the hard part.

 

[simmerskool]

Nice outcome. FreeBSD can feel a bit “hands-on” during install/config

Security note for new FreeBSD installs

nice reply thanks, @Bot can you do a comparison of FreeBSD with OpenBSD both installation experience in VMware and then when up and running

 

[Bot]

nice reply thanks, @Bot can you do a comparison of FreeBSD with OpenBSD both installation experience in VMware and then when up and running

FreeBSD and OpenBSD can both run well in VMware, but they feel different both during install and in day-to-day use because their priorities differ (FreeBSD: performance/features; OpenBSD: secure-by-default correctness and simplicity).

Installation experience in VMware (practical differences)

FreeBSD (14.x)

• More “choices that matter”: Storage/NIC controller selection in VMware can influence how smooth the install feels. If you pick a device model FreeBSD supports well, it’s straightforward; if not, you may spend time adjusting the VM hardware or loader/module settings.
• More post-install integration work is common: Display resizing, copy/paste, and other “desktop-ish” conveniences can require additional packages/services depending on your setup (console vs X11/Wayland).
• ZFS option adds power (and complexity): Installing with ZFS is a big advantage for snapshots/rollback/administration, but it can make the install feel more “serious sysadmin” compared to a minimal UFS setup.

OpenBSD

• Typically very consistent installer flow: The OpenBSD installer is famously straightforward and opinionated, with fewer branches/choices. In a VM that usually translates to “less fiddling” during the OS install itself.
• Driver coverage is deliberate: OpenBSD supports a lot of common hardware, but it is conservative about what it enables and how. In VMware, using well-supported virtual devices (often the more “generic” ones) tends to make it painless.
• Post-install is usually “ready to secure” quickly: The default configuration is already security-focused, so there’s often less temptation/need to tweak core settings immediately after install.

What usually makes VMware installs go smoother for both

• Use mainstream emulated hardware (for example, an Intel e1000-style NIC is often the least surprising choice across OSes).
• Avoid exotic controllers unless you know the guest OS supports them well.
• Prefer a simple BIOS/UEFI setup and keep it consistent (switching BIOS/UEFI midstream can complicate boot).
• Take a VMware snapshot before major updates or boot-related changes.

When up and running: how they tend to feel in a VMware VM

Performance and “light/fast” feel

• FreeBSD: Often feels very fast once tuned, and scales well with multiple vCPUs and heavier workloads. Strong networking stack, solid VM server use cases, and ZFS is a major differentiator (great for snapshots and recovery workflows).
• OpenBSD: Usually feels lean and predictable. It may not chase maximum throughput in the same way FreeBSD does, but it emphasizes correctness and safe defaults. For many typical admin/security tasks, it feels clean and stable rather than “tuned for peak speed.”

Security posture by default

• OpenBSD: Security-first defaults are a core selling point. The base system is tightly integrated, with a strong emphasis on reducing attack surface and “secure-by-default” behavior.
• FreeBSD: Very capable and can be hardened well, but it’s more of a “choose your profile” OS. You’ll often decide which services/features to enable, which hardening steps to apply, and how far to go based on role (desktop, server, lab VM, etc.).

Ecosystem and features that matter in VMs

• FreeBSD advantages: ZFS ecosystem, jails (excellent lightweight isolation), broad server tooling, and a large ports/packages collection with many deployment patterns.
• OpenBSD advantages: Very cohesive base system, excellent documentation style, strong built-in networking/security tooling (notably PF), and a culture of minimalism that reduces complexity.

Bottom line

In VMware, OpenBSD often “feels simpler” during the OS install because it’s more opinionated and conservative, while FreeBSD can feel more tedious up front because there are more viable paths (UFS vs ZFS, different service choices, more integration options). Once running, FreeBSD typically wins on feature breadth and performance headroom, while OpenBSD typically wins on secure-by-default coherence and operational simplicity.

Sources

• 
  [] https://docs.freebsd.org/en/
  [] OpenBSD FAQ: Installation Guide
  [] OpenBSD FAQ: System Management

 

[Zero Knowledge]

FreeBSD!!!! OpenBSD!!! OMG brings back so many memories. How is development these days? Haven't used in 15 years.

 

[simmerskool]

FreeBSD!!!! OpenBSD!!! OMG brings back so many memories. How is development these days? Haven't used in 15 years.

I just installed FreeBSD 14.3 p9 in VMware and now that it is installed, I'm liking it the first 24 hours for what I do, fast. OpenBSD, I'll install it tomorrow or over the weekend and see. I want to compare those 2 BSD.