pkg info

Check which packages are installed. Needed are:

vm-bhyve — Management system for bhyve virtual machines

bhyve-firmware — Collection of Firmware for bhyve

kldstat

Kernel modules

vmm.ko — virtualzation driver

zfs.ko — for the file system

sysrc vm_enable="YES"

enable vm

sysrc vm_dir="zfs:vmzfs/vm"

set root directory for the vm; after the reboot the templates will show up; alternatively vm init

vm init

set templates and config files in the vm_dir directory

vm switch create public

create the public bridge which is used by the virtual machine for the taptun virtual divices. the bridge is called vm-public but in the config files of the virtual machines the name is only public

vm switch add public em0

add a physical intervace em0 that is used by the bridge to access he internet. Note that if you have multiple physical devices you have to add the device that has internet access. For example em1 may be the device that has access to the internet in which case you have to change the above command accordingly. You can check that the bridge has the correct information by issuing ifconfig vm-public or just ifconfig if the bridge name is not vm-public and check under members to see which interfaces are in the bridge. The correct emX should be listed

vi /path/to/vm_dir/.config/system.conf

if there are two physical ethernet devices say em0 and em1 the ports_public="emX" lists which the interface the switch public is used. Note also in this file there is switch_list="public" which is used in the config files in each virtual machine

This the the management system with which we will start, stop update and maintain the guests

vm start jupyter

start a virtual machine with name jupyter

vm list

list all virtual machine

vm info

Check information about running virtual machines (guests)

vm stop jupyter

stop gracefully the virtual machine with name jupyter

vm poweroff jupyter

stop forcefully the virtual machine with name jupyter

vm console jupyter

connect to the virtual machine console and log on

exit

It is a good idea to logoff the host before exiting the vm console

Press ~ (tilde) then ^D (Ctrl+D) to terminate the console

you may need to press Shift to enter the tilde character; only the righthand shift works, pressing left shift with tilde simply supplies tilde to the guest (console)

vm snapshot jupyter@snapshotname

create a snapshot of a virtual machine. It is (should be) stopped at the time of taking the snapshot

vm info jupyter

will give information about the virtual machine include the list of available snapshots of that machine

• Virtualization with bhyve
• vm with freebsd
• freebsd hypervisors
• freebsd bhyve
• freebsd hosting with bhyve
• zfs for virtual machines
• exiting vm console

vm iso

see available iso and img files for installation

/path/to/vmdir/.templates where files are stored

vm iso https://path.to.location/file

download installation media

vi /path/to/vm/.templates/freebsd.conf

edit the config file

loader="bhyveload"
cpu=2
cpu_cores=2
cpu_sockets=1
memory=8G
network0_mac="E4:3E:7E:E3:E4:84"
network0_type="virtio-net"
network0_switch="public"
disk0_name="FreeBSD"
disk0_type="virtio-blk"
disk0_dev="sparse-vol"
zfs_zvol_opts="volblocksize=8k compress=on"
graphics="no"
			

Change the name of the disk0_name to something suitable

vm create -t freebsd -s 8G FreeBSD

create the virtual machine

vm install FreeBSD FreeBSD-LATEST-RELEASE.iso

start the installation of FreeBSD operating system with whichever iso file you decided to use

vm console FreeBSD

get to the console and follow installation instructions

the above config file sets a zfs volume, one of the questions asked during installing is which filesystem you want: ufs or zfs. With ufs after installation there was kernel panic, with zfs no such issues were encountered

after installation powerdown the system

vm start FreeBSD

start the virtual machine

vm console FreeBSD

get to the console and install necessary tools

pkg install socat

first installs the pkg system if not already installed

installs socat

Get a machine

Get a ready made virtual machine image

Run the machine

following change the bios part

qemu-system-x86_64 -m 4096 -smp 4 -serial mon:stdio -nographic -drive file=FreeBSD-14.0-RELEASE-amd64.qcow2 -enable-kvm

Close the machine from within freebsd

poweroff

Download say FreeBSD-15.0-RELEASE-amd64-BASIC-CLOUDINIT-ufs.qcow2.xz

Get a machine

cp FreeBSD-15.0-RELEASE-amd64-BASIC-CLOUDINIT-ufs.qcow2.xz vm00.qcow2.xz

Make a copy of the file to avoid future downloads

uzxz vm00.qcow2.zx

Expand the image

qemu-img resize vm00.qcow2 +4G

Resize the hard disk of the work copy to a desired size in our case increase by 4G

 /usr/bin/qemu-system-x86_64 \
	-enable-kvm -m 8192  -cpu host -smp 4 \
	-drive file=./vm00.qcow2 \
	-monitor unix:/run/vm00.sock,server,nowait \
	-nic tap,mac=b4:e1:ad:2b:d3:00 \
	-serial mon:stdio  -nographic \
	-pidfile /run/user/1001/vm00.pid \
	-name vm00,process=vm00

run the machine with access to serial console. For this FreeBSD image some scripts will be run for you on the virtual machine. Subsequently the virtual machine will reboot and you will be greeted with a login for a root user. Just type root to access FreeBSD are root. From within the root console of the virtual machine get some things ready, such as remote access

passwd

set a root password and reboot the virtual machine

vi /etc/rc.config

set the hostname to a meaningful name

vi /etc/ssh/sshd_config

modify sshd to allow root login

reboot

after setting up a root password reboot the machine. Send your public key file to the guest with ssh-copy-id root@192.168.1.XXX or ssh-copy-id root@guest_hostname where guest_hostname resolves to the ip address of the guest. You should be able to log in the guest with ssh root@192.168.1.XXX or ssh root@guest_hostname. Log in with your new root password either from the serial console or remotely.

vi /etc/ssh/sshd_config

modify sshd to allow root login but only with public key authentication.

service sshd restart

make sure the sshd daemon uses the new configuration - there are alternative ways to do it of course

perform any tasks you want on your virtual machine that runs FreeBSD. One good idea would be to add a new user with wheel privileges instead of using root login. Install any software that you need

pkg update

It is a good idea to add the various ports for easier installation of software. Be where of pkg update issue

After creating the guest virtual machine at one point your drive may be full in which case you may need to increase the drive space (Ram and the like are changes to qemu-system-x86_64) options. From the host do

echo system_powerdown | socat - unix-connect:/path/to/work.sock

stop the virtual machine

qemu-img resize work.qcow2 +4G

expand the drive with the desired amount

qemu-system-x86_64 -drive file=work.qcow2

start the virtual machine. Include all options that you regularly use

ssh root@work

access the root console in the guest

gpart show

see the names of the dist as viewed by gpart. In my case ada0

gpart recover ada0

if there is a corruption fix it (possible after expanding the disk with qemu-img

gpart resize -i 5 ada0

here -i 5 points to (the last) partition of the disk where the root partition is stored

df -h

Check where root partition is mounted on /dev mine was different from /dev/ada0p5. It was on /dev/gpt/rootfs

growfs /dev/gpt/rootfs

grow the partition (this is assuming you used ufs type filesystem)

reboot

reboot and log on again to verify the changes