Port details on branch 2023Q4 |
- virtualbox-ose-nox11 General-purpose full virtualizer for x86 hardware
- 6.1.48 emulators =0 Package not present on quarterly.This is expected early in the quarter (because the new packaage repo has not been built yet.). Otherwise, this missing version is most likely a FreshPorts error.
- Maintainer: vbox@FreeBSD.org
- Port Added: 2023-10-22 10:31:45
- Last Update: unknown
- License: GPLv2
- WWW:
- https://www.virtualbox.org/
- Description:
- Oracle VM VirtualBox is a hosted hypervisor for x86 virtualisation.
Supported guests include BSD, Haiku, Linux, OS/2, ReactOS, Solaris and
Windows.
Guest Additions are available from: emulators/virtualbox-ose-additions
For the Extension Pack: FreeBSD is not a supported host platform.
Installation of the Pack will not extend the feature set.
- ¦ ¦ ¦ ¦
- Manual pages:
- FreshPorts has no man page information for this port.
- pkg-plist: as obtained via:
make generate-plist - Dependency lines:
-
- virtualbox-ose-nox11>0:emulators/virtualbox-ose-nox11
- Conflicts:
- CONFLICTS_INSTALL:
- virtualbox-ose-additions-*
- virtualbox-ose-devel
- virtualbox-ose-legacy
- virtualbox-ose-lite
- virtualbox-ose
- To install the port:
- cd /usr/ports/emulators/virtualbox-ose-nox11/ && make install clean
- To add the package, run one of these commands:
- pkg install emulators/virtualbox-ose-nox11
- pkg install virtualbox-ose-nox11
NOTE: If this package has multiple flavors (see below), then use one of them instead of the name specified above.- PKGNAME: virtualbox-ose-nox11
- Flavors: there is no flavor information for this port.
- ONLY_FOR_ARCHS: amd64
- distinfo:
- TIMESTAMP = 1697733397
SHA256 (VirtualBox-6.1.48.tar.bz2) = 092505c28b8b8b88048d51c34f1e16c0275dc70612d4810d8f475879f0ff5317
SIZE (VirtualBox-6.1.48.tar.bz2) = 165960987
No package information for this port in our database- Sometimes this happens. Not all ports have packages. Perhaps there is a build error. Check the fallout link:
- Master port: emulators/virtualbox-ose
- Dependencies
- NOTE: FreshPorts displays only information on required and default dependencies. Optional dependencies are not covered.
- Build dependencies:
-
- gtar : archivers/gtar
- kmk : devel/kBuild
- libIDL-config-2 : devel/libIDL
- yasm : devel/yasm
- xsltproc : textproc/libxslt
- soapcpp2 : devel/gsoap
- pkgconf>=1.3.0_1 : devel/pkgconf
- python3.9 : lang/python39
- Runtime dependencies:
-
- vboxnet : emulators/virtualbox-ose-kmod
- Library dependencies:
-
- libpng.so : graphics/png
- libcurl.so : ftp/curl
- libvncserver.so : net/libvncserver
- libxml2.so : textproc/libxml2
- There are no ports dependent upon this port
Configuration Options:
- ===> The following configuration options are available for virtualbox-ose-nox11-6.1.48:
AIO=on: Enable Asyncronous IO support (check pkg-message)
PYTHON=off: Python bindings or support
UDPTUNNEL=on: Build with UDP tunnel support
VDE=off: Build with VDE support
VNC=on: Build with VNC support
WEBSERVICE=on: Build Webservice
===> Use 'make config' to modify these settings
- Options name:
- emulators_virtualbox-ose-nox11
- USES:
- compiler:c++14-lang cpe gnome iconv pkgconfig ssl tar:bzip2 python:build
- pkg-message:
- For install:
- VirtualBox was installed.
You need to load the vboxdrv kernel module via /boot/loader.conf:
vboxdrv_load="YES"
You also have to add all users to your vboxusers group in order to use vbox.
% pw groupmod vboxusers -m jerry
Reboot the machine to load the needed kernel modules.
Bridging Support:
=================
For bridged networking please add the following line to your /etc/rc.conf:
vboxnet_enable="YES"
USB Support:
============
For USB support your user needs to be in the operator group and needs read
and write permissions to the USB device.
% pw groupmod operator -m jerry
Add the following to /etc/devfs.rules (create if it doesn't exist):
[system=10]
add path 'usb/*' mode 0660 group operator
To load these new rule add the following to /etc/rc.conf:
devfs_system_ruleset="system"
Then restart devfs to load the new rules:
% /etc/rc.d/devfs restart
Troubleshooting:
================
Running VirtualBox as non-root user may fail with a fatal error
NS_ERROR_FACTORY_NOT_REGISTERED. In this case delete /tmp/.vbox-*-ipc file.
If you experience "Network: write Failed: Cannot allocate memory" errors
try to increase net.graph.maxdata in /boot/loader.conf
If you are using AIO, then increase these limits (https://bugs.freebsd.org/168298):
vfs.aio.max_buf_aio=8192
vfs.aio.max_aio_queue_per_proc=65536
vfs.aio.max_aio_per_proc=8192
vfs.aio.max_aio_queue=65536
To check if AIO is used use: kldstat -v | grep aio
If you are experiencing VMs freezes with an error in VBox.log such as:
"
00:01:29.590192 AssertLogRel /usr/ports/emulators/virtualbox-ose/work/VirtualBox-6.1.44
/src/VBox/VMM/VMMR3/PGMPhys.cpp(5148) int PGMR3PhysAllocateHandyPages(PVM): RT_SUCCESS(rc)
00:01:29.590221 87/128: idPage=0x3d400 HCPhysGCPhys=000000027eaed000 rc=VERR_NO_MEMORY
00:01:29.590247 Changing the VM state from 'RUNNING' to 'GURU_MEDITATION'
00:01:29.590261 Console: Machine state changed to 'GuruMeditation'
00:01:29.590695 !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
00:01:29.590696 !!
00:01:29.590697 !! VCPU0: Guru Meditation -8 (VERR_NO_MEMORY)
"
and see a lot of free RAM, then increase sysctl vm.max_user_wired
(https://bugs.freebsd.org/252227).
For dedicated VM servers, a good start is:
("RAM in GB" - max(1, "RAM in GB" / 32)) * 1024*1024*1024 / PAGE_SIZE
PAGE_SIZE on x86 is 4096.
Examples with different RAM sizes in GB:
16: ( 16-max(1, 16/32)*1024*1024*1024/4096 = 3932160 => 15GB
32: ( 32-max(1, 32/32)*1024*1024*1024/4096 = 8126464 => 31GB
48: ( 48-max(1, 48/32)*1024*1024*1024/4096 = 12189696 => 46.5GB
64: ( 64-max(1, 64/32)*1024*1024*1024/4096 = 16252928 => 62GB
128: (128-max(1,128/32)*1024*1024*1024/4096 = 32505856 => 124GB
256: (256-max(1,256/32)*1024*1024*1024/4096 = 65011712 => 248GB
When assigning IP addresses in host-only mode from ranges outside
of VirtualBox's defaults, the respective ranges need to be listed
in /usr/local/etc/vbox/networks.conf (https://bugs.freebsd.org/259399).
Check the wiki page for known issues and troubleshooting:
https://wiki.freebsd.org/VirtualBox
Please report any problems to emulation@. Thanks!
- If upgrading from < 6.1.22:
- The PULSEAUDIO option has been forcibly disabled since VirtualBox
version 6.1.24 due to a bug in it preventing virtual machines
configured to use it from starting.
When upgrading from a previous version please reconfigure any virtual
machines using the Pulseaudio host audio driver to use another
supported one.
- If upgrading from > 6.1.26 and < 6.1.32_1:
- To comply to hier(7) requirements, networks.conf's location changed
to /usr/local/etc/vbox/networks.conf.
In case /etc/vbox/networks.conf exists, it needs to be moved to
/usr/local/etc/vbox and /etc/vbox should be deleted.
- Master Sites:
|