Table of content

Installation
Guest
1. Debian

VirtualBox allows to run a full-operating system in an isolated process. The main advantages of VirtualBox are it’s availability on a wide range of platforms (Linux, FreeBSD, Windows, MacOSX), and its support for graphical card.

Build information

Ensure the following options:

emulators/virtualbox-ose-kmod

1	`[x] VIMAGE VIMAGE virtual networking support`

emulators/virtualbox-ose

1 2	`[x] VNC Build with VNC support [x] WEBSERVICE Build Webservice`

Using a bridge or lagg interface which as a WiFi interface as member will not work as expected because most wireless adapters do not support promiscuous mode.

Installation

If VirtualBox is to be used in the following conditions:

standard user belonging to the vboxusers group
network is configured with bridged networks

The permissions on the device /dev/vboxnetctl are too restrictive and need to be changed:

Less restrictive permissions for `vboxnetctl`

1 2	`chown /dev/vboxnetctl root:vboxusers chmod /dev/vboxnetctl 0660`

This setting can be made permanent:

if the modules are loaded in /boot/loader.conf), by adding the following lines to /etc/devfs.conf:
devfs.conf
1 2 3
# Virtual Box own vboxnetctl root:vboxusers perm vboxnetctl 0660

if the modules are loaded using the rc startup scripts:

rc.conf

1 2	`vboxnet_enable="YES" devfs_system_ruleset="localrules"`

devfs.rules

[virtualbox=10]
add path 'vboxnetctl' mode 0660 group vboxusers

[localrules]
add include $virtualbox

Guest

Debian

Rules dealing with interface numbering are automatically created as udev rules at startup, the aim is to avoid renumbering interfaces. Unfortunately if the VM is cloned it will result in the disappearing of the network interface, as the MAC address has changed it is considered as new interface and a new number is allocated, to avoid this it is necessary to remove the file /etc/udev/70-....