# External source for online doc

docversion="13.x"

##############################################

# Set PATH

set -e

. ${distdir}/cbsd.conf

exit 1

[ -z "${EFI}" ] && EFI=1

if [ ! -f "${CHROOT}/boot/loader.efi" -a ${EFI} -eq 1 ]; then

Using **CBSD**, you can combine in one tool management for both jail containers and virtual machines on the bhyve hypervisor, using this or that approach in different tasks

When ready, you will see a dialog-based menu for creating a virtual machine:

The options **vm\_os\_profile**, **jname**, and **imgsize** \- are mandatory for manual input

A number of parameters (bhyve arguments) are available in the submenu **bhyve\_options**:

and **vnc\_options**:

Please note that when you enter the **imgsize** parameter, you specify the amount of the first (boot) virtual hard disk.

Attention! Note the presence of a menu for selecting the bhyve IP address in the bconstruct-tui menu. Keep in mind that without auxiliary scripts inside the distribution or virtual machine, you can not manage the settings in the virtual machine itself from the outside.

This menu item saves the IP address in the CBSD database so that you can configure third-party methods (for example via DHCP) to automatically configure the OS without having to put your own scripts inside. As an example,

- \- **mode**: (required) action relative to the environment: create (create checkpoint), list (list of checkpoints created), destroyall (destroy all checkpoints)

- \- **name**: (optional) specify an alternate checkpoint name, by default: checkpoint

- \- **poweroff**: (optional). When poweroff=1, **CBSD** will automatically shut down the virtual machine instantly

Each virtual machine **CBSD** stores the settings in the SQLite3 database. To change the settings of a VM can serve command **cbsd bconfig**, TUI launches menu for changing the basic settings.

The functionality of execution custom scripts and the availability of variables in environments can play a big role in the integration of **CBSD** and external applications, such as **Consul**

As such, the configuration of the virtual machine topology does not affect the speed of the virtual machine itself:

The configuration data becomes important, in conjunction with the settings for binding the virtual machine cores to a particular group of physical server cores (set\_affinity, cpu-pinning), as will be discussed separately. The aim of this article is to consider

bhyve possibilities and work with its configuration through **CBSD**.

If the virtual machine is bound to a particular core of the physical machine, you will see its name opposite the given kernel of a specific socket. If there are no bindings/pinning, all virtual environments will be opposite each core - since they do not have restrictions on

the use of certain kernels and they can migrate than are required by the OS OS master:

A socket is directly a physical processor (package) on your motherboard. If the processor supports hyper-threading (and it is enabled), the virtual cores will be marked as _THR_

You can create any number of profiles for the topology. You can view their list using vm-cpu-topology:

You can delete or add new ones through the TUI command interface vm-cpu-topology-tui

Profile names must be unique and the application of this or that topology is performed through the command bset, bconfig. And also, the choice of topologies will be available when creating a virtual machine in bconstruct-tui:

The same menu is available to create a jail when configuring **CBSD** via bsdconfig

If **bconstruct-tui** worked correctly, at the end you will be asked to create a virtual machine. In the case of positive response, **bcreate** will be made to the new configuration automatically. Otherwise, script displays the path to the configuration file (in _$workdir/tmp_), on which you can create a VM.

Guest OS type:

Choosing profile for Linux type guest:

Choosing VM name:

Choosing bhyve UEFI boot method:

Choosing bhyve VNC params:

Choosing bhyve params: