From 0 to Bhyve on FreeBSD 13.1

FreeBSD has its own high-performance hypervisor called “bhyve”. Much like the Linux kernel’s KVM hypervisor, bhyve enables the creation and maintenance of virtual machines—aka “guests”—which run at near-native speed alongside the host operating system. Although bhyve got a later start than Linux KVM, in most ways it has caught up with its primary rival—and in some ways surpassed it.

Using Netgraph for FreeBSD’s Bhyve Networking

networking virtualization

FreeBSD 13 adds new support for a netgraph backend for virtual network devices under bhyve. Netgraph is a modular networking framework that allows for arbitrary stacking of protocols and transports, along with filtering, tunneling, redirection, inspection, injection and more—fast and feature-rich, netgraph is to networking what the geom layer is to disks and storage. This article provides a basic recipe to demonstrate some common netgraph syntax and use-cases.Why might you want to run CURRENT? If you have a large modified code base, or are building a product based on FreeBSD, CURRENT gives you a look into the future of FreeBSD. Running CURRENT will help you understand changes that are happening in the FreeBSD Operating System and it gives you an opportunity to see how your stack performs with new features.
In this article we will show how to build a CURRENT system with the debugging features disabled, and perform some benchmarks to test the impact debugging features have on performance.

Evaluating FreeBSD CURRENT for Production Use

The FreeBSD Operating System introduces new features in CURRENT, its main development branch. Snapshots of CURRENT are made available as installer images weekly.
Why might you want to run CURRENT? If you have a large modified code base, or are building a product based on FreeBSD, CURRENT gives you a look into the future of FreeBSD. Running CURRENT will help you understand changes that are happening in the FreeBSD Operating System and it gives you an opportunity to see how your stack performs with new features.
In this article we will show how to build a CURRENT system with the debugging features disabled, and perform some benchmarks to test the impact debugging features have on performance.

Interacting with FreeBSD – Learning the Fundamentals of the FreeBSD Shell

The time of the CLI might seem over given the plethora of UIs these days, however, any experienced sysadmin knows just how necessary a powerful CLI like the FreeBSD shell can be. In FreeBSD 14, the default root shell is changing, and in this article we talk about the background and motivations for this change and what implications and advantages this change brings.

Controlling Resource Limits with rctl in FreeBSD

As an administrator, you may often need to limit the amount of system resources an individual uses. FreeBSD provides several methods to do just that. The rctl command can be used to provide an effective method for controlling resource limits or it can be used to set resource constraints on processes and jails. Find out how to configure and enforce your limits.

The FreeBSD Boot Process

Let’s talk about the FreeBSD boot process. It is very robust and complex, as it is well-thought. Find out what are the differences when you boot from UEFI or legacy BIOS, or from GPT and MBR partitioning schemes. Learn what happens when you use ZFS or UFS filesystem.

Using FreeBSD’s pkg audit to Investigate Known Security Issues

Keeping systems secure and free of any vulnerabilities is an important task in any sysadmin’s or developer’s book. Fortunately, FreeBSD systems come with several tools to accomplish that task for both its Base System and installed 3rd party packages.
In this article, we will take a look at how these tools can help us efficiently manage security vulnerabilities in our FreeBSD systems

Explaining top(1) on FreeBSD

We all know and have at least once used the top(1) command on FreeBSD to track information about our cpu and processes, but how many of you know what each field means? By default, top(1) displays the ‘top’ processes on each system and periodically updates this information every 2.0 seconds using the raw cpu use percentage to rank the processes in the list.
This article will give you some insight on how to better understand top (1).