Download REALTEK Sound Card drivers, firmware, bios, tools, utilities. Realtek Audio Driver 6.0.8945.1 for Windows 10 64-bit 106 downloads. Sound Card REALTEK. Windows 10 64 bit. Feb 2nd 2021, 08:55 GMT. Gigabyte B450 AORUS ELITE (rev.
- 1) Start Virtual Box. 2) Start your guest VM. 3) BEFORE attempting to play sound from the guest, start an application that engages the audio device on the Win 10 host (I use a youtube video) 4) While audio is playing on the host, attempt to play audio from the guest.
- Go to setting of the android virtual machine and select “Audio” and in audio setting select “SoundBlaster 16” as audio controller. The Android-x86 website says that only SoundBlaster 16 works as a VirtualBox soundcard for Android.
- Download Box apps on all your devices: Mac, Windows, iPhone, Android, for seamless collaboration and security that satisfies even the most regulated industries.
VirtualBox is cross-platform virtualization software that allows users to run guest operating systems inside a host operating system without having to reboot. Since 2010 VirtualBox software has been written and maintained by the Oracle Corporation.
Terminology
Term | Explanation |
---|---|
Host operating system | The host computer. Most likely the physical hardware present in the room. For Gentoo users the host operating system would be Gentoo Linux |
Guest operating system | The operating system to be installed or currently installed inside the VirtualBox emulation environment. Possible alternative operating systems include Microsoft Windows, Solaris, BSD, Debian, Ubuntu, etc. |
VirtualBox Guest Additions | Drivers for the guest operating system. These drivers provide smoother operation with the Host operating system compared to the standard drivers installed by the Guest operating system. |
Installation
The qt5
USE controls installation of the graphical user interface (GUI) which is enabled by default.
USE flags
VirtualBox
USE flags forapp-emulation/virtualboxFamily of powerful x86 virtualization products for enterprise and home use
alsa | Add support for media-libs/alsa-lib (Advanced Linux Sound Architecture) |
debug | Enable extra debug codepaths, like asserts and extra output. If you want to get meaningful backtraces see https://wiki.gentoo.org/wiki/Project:Quality_Assurance/Backtraces |
doc | Add extra documentation (API, Javadoc, etc). It is recommended to enable per package instead of globally |
dtrace | Install dtrace Extension Pack |
headless | Build without any graphic frontend |
java | Add support for Java |
libressl | Use dev-libs/libressl instead of dev-libs/openssl when applicable (see also the ssl useflag) |
lvm | Build VBoxVolInfo that needs devicemapper from sys-fs/lvm2. |
opengl | Add support for OpenGL (3D graphics) |
opus | Enable Opus audio codec support |
pam | Add support for PAM (Pluggable Authentication Modules)DANGEROUS to arbitrarily flip |
pax_kernel | Apply patch needed for pax enabled kernels. |
pulseaudio | Add support for PulseAudio sound server |
python | Add optional support/bindings for the Python language |
qt5 | Add support for the Qt 5 application and UI framework |
sdk | Enable building of SDK |
udev | Controls installation of special USB udev rules. |
vboxwebsrv | Build and install the VirtualBox webservice |
vnc | Enable VNC (remote desktop viewer) support |
Emerge
VirtualBox
Virtualbox requires some kernel configuration options.
Once the kernel is built and you've rebooted, install Virtualbox:
Windows guests
Emerge the app-emulation/virtualbox-additions package on the host system to get the Guest Additions ISO image that contains all necessary Windows guest drivers:
root #
emerge --ask app-emulation/virtualbox-additions
Gentoo guests
Kernel configuration
When running Gentoo as a guest system, enable the following kernel options on the guest system (either built-in or as modules) to get proper support for the hardware emulated by VirtualBox:
Guest Additions
To install the Guest Additions, invoke the following command on the Gentoo guest system:
root #
emerge --ask app-emulation/virtualbox-guest-additions
Make it persistently start across reboots:
root #
rc-update add virtualbox-guest-additions default
As well as the D-Bus service:
To enable the shared clipboard, display resizing, seamless mode, and drag and drop make sure the user running the X session (on the Gentoo guest system) belongs to the vboxguest group:
Changes will not take effect until the user signs out and then signs in again (re-logins).
To install other Linux distributions as guest operating systems please refer to the distribution's documentation on how to install the drivers needed by VirtualBox or consult the official VirtualBox documentation.
Resizing doesn't work
Due to the limitations of the VMSVGA described below, a daemon needs to be started in your X11 session for Guest resizing to work.
If the Guest Additions are installed correctly, the shared clipboard is working, etc., but the display can't be resized, open the VM's settings in the host-side VirtualBox Manager and look at Display → Graphics Controller. If it's set to VMSVGA, try changing it to VBoxSVGA while the guest is powered off. According to the VirtualBox docs, this works because auto-resizing in Linux guests is induced in part by changing the serial number of the simulated monitor, which can't be done under VMSVGA.[1]
GPU acceleration
Modern VirtualBox emulates VMWare SVGA by default for Linux machines. Select support in make.conf:
/etc/portage/make.conf
If the video choice is modified, then select the alternative option:
When making changes to the VIDEO_CARDS setting, it is a good idea to perform a full deep upgrade to apply the change.
VirtualBox shared folders in a Gentoo guest
VirtualBox shared folders can only be mounted after the virtualbox-guest-additions service has been started. Since this happens towards the end of the bootup sequence (OpenRC), a shared folder mount in /etc/fstab will fail. Either:
- Make the
noauto
mount option and add a mount/unmount pair of scripts in /etc/local.d - View /etc/rc.conf for information about adding extra dependencies for services.
If it is desired to let a user manually mount a shared folder, that user must be added to the vboxsf group
Advanced networking-related
According to the ebuild's message after VirtualBox is installed sys-apps/usermode-utilities and net-misc/bridge-utils can be installed for advanced network configuration. Install them only if advanced networking is required:
Configuration
Kernel modules
Users will not be able to run and use VirtualBox if they are not a member of the vboxusers group:
Changes will not take effect until the user re-login.
Load the required driver module into the kernel. This module is made available when app-emulation/virtualbox-modules has been emerged:
Optional modules:
root #
modprobe vboxnetflt
It is possible to automatically load the modules each time the system boots. Create a new file under the /etc/modules-load.d directory and list, separated by newlines, the kernel modules to load:
systemd
Modules can be loaded immediately on systemd systems by running:
Enable port forwarding to guest machines
When booting LiveCDs or other live media, it can be handy to enable port forwarding from the host machine to the guest machine. None of the additional network configuration modes are necessary for a simple port forwarding setup, so do not dig too deep into upstream docs. Port forwarding can be handy when running a web server, an SSH daemon, or any other service that runs on a specific port.
First, be sure the guest VM is shutdown, then from the command line issue:
user $
VBoxManage modifyvm 'VM name' --natpf1 'guestssh,tcp,2222,22'
Be sure to replace 'VM name'
with the proper name of the guest virtual machine. The first number (2222
) will be the port on the host machine. The second number (22
) will be the port on the guest machine. Adjust accordingly, then reboot the virtual machine. This can also be performed via the GUI by clicking Settings -> Network -> Advanced (drop down) -> Port Forwarding.
More details can be found in the upstream documentation.
Usage
There are many options which can influence behavior and performance of the virtual machines. If you don't know what these options are doing, leave them to their defaults. Virtual machines may become unbootable if the wrong options are set.
Here is a list of options that are safe to use:
- Host I/O cache can safely be enabled for all virtual storage controllers.
- If the host system's CPU supports hardware virtualization, enable the 'VT-x/AMD-V' option. It can drastically increase the performance of the virtual machines.
Troubleshooting
virtualbox fails to build
Sound Cards 7.1
When the app-emulation/virtualbox package fails to build because the javac command cannot be found (even with a Java JDK (Java Development Kit) and a Java JRE (Java Runtime Environment) installed), it is likely the JRE has been set as the default system-vm. JRE packages do not contain javac. Make sure the correct system-vm (JDK) has been selected using the java-config command and then try rebuilding virtualbox. More information can be found in the Installing a virtual machine section of the Java User Guide.
virtualbox-modules fails to build
Some users have issues with the app-emulation/virtualbox-modules package failing to build. This can be caused by an improper kernel/profile configuration. Verify the chosen kernel and the selected profile match each other. For example, if a hardened profile is set, a hardened kernel should be used. If a default AMD64 profile is set, then the default gentoo-sources should be used. Run the eselect command to view the list of profile options:
Then use the eselect command again to display which kernel is selected:
Looking at the output of these two commands, a user can determine if the system is setup properly (the profile matches the kernel) and should have no issues installing app-emulation/virtualbox-modules. Remember: Make sure the system profile and the selected kernel match!
virtualbox-modules permission denied errors
The following 'Permission denied' errors can be caused by a strict file mode creation mask (e.g. umask 077
):
The easiest solution would be to backup .config
, run make distclean
and use the default umask 022
.
Host key failing to operate in the virtual machine
If the host key (typically the right Ctrl key) is failing to operate within the virtual (guest) machine, be sure any desktop environment or window manager hooks to host key have been disabled from the host machine's desktop environment or window manager.
For example, the GNOME 3 desktop environment includes a 'Show location of the [mouse] pointer' option in the Keyboard and Mouse section of the Tweak Tool (gnome-extra/gnome-tweak-tool). This option will enable a ripple effect to be displayed around the mouse when either the right or left Ctrl key is pressed. This mouse locator handle conflicts with the virtual machine's handle on the right Ctrl key. Disabling this setting (via switching the rocker switch to Off in the Tweak Tool interface) should fix the problem by re-assigning the right Ctrl key as the handle for the host key within the virtual machine.
No audio after upgrade
If there is no sound after upgrading VirtualBox, increasing the VirtualBox ALSA buffer size may fix the issue[2].
user $
VBoxManage setextradata global VBoxInternal2/Audio/ALSAAudio/BufferSizeMs '100'
Performance problems
Microsoft Windows guests
- According to the documentation, the I/O APIC feature (VM -> Settings -> System -> Motherboard -> Enable I/O APIC), which is enabled by default, 'slightly increases the overhead of virtualization and therefore slows down the guest OS a little'. However, there have been reports that the performance impact may actually be quite severe on some host/guest system combinations (e.g. forum post). Be aware that disabling this feature might require additional steps on the guest system as described by this forum post.
- Using a SATA controller, it is necessary to choose the right driver version from Intel's SATA drivers. Using a wrong version will cause performance problems along with blue screen errors! Refer to this post for a list of working SATA drivers.
- Slow performance using SATA driver? Only use the SATA controller interface for the hard disk. Remove any CDROMs from the SATA controller and place them onto a IDE Controller.Note
This can also be a problem of using the wrong SATA-driver version. - When installing the VirtualBox Guest Additions into your Windows operating system, do not select to enable Direct3D (experimental) option as this will cause resizing problems and other anomalies. Also, you need to install the Guest Additions from Safe Mode.
- Do not use the ICH9 chipset with Windows. It is still considered experimental. Using it can cause temporary freezes of the whole VM when used with Windows 7. See this post for more informations.
- Slow read/write speed to the virtual disk? If the host system has sufficient RAM, try checking (enabling) the Use Host I/O Cache check box in the virtual machine's Storage frame. This will cache much of the guest machine's page file into the host's memory effectively limiting the amount of I/O guest machine will use the virtual disk image file. This is particularly helpful when running Windows guests because of the amount of paging Windows based operating systems regularly perform.
Linux guests
- When running Gentoo as a guest system make sure you start the virtualbox-guest-additions init script during bootup.
- Having the guest VDI images on a btrfs filesystem might slow down Linux guests up to the point where the guest kernel remounts its filesystems readonly and no longer performs any I/O. This can be fixed by disabling btrfs' copy on write for the VDI image files on the host.
Kernel driver not installed
This may occur after building a new kernel and causes an error message:
Solution: Rebuild the VirtualBox kernel modules via:
The system may need rebooted for changes to take effect.
Nonexistent host networking interface, named 'vboxnet0'
Newly created interface will now be shown as available, but not activated (down):
An IP will need to be assigned to it:
root #
VBoxManage hostonlyif ipconfig vboxnet0 --ip 192.168.56.101
Kernel Panic when suspending the HOST while Virtualbox is running
If you experience such behavior, try removing the vbox family of modules before suspending.If this solves the kernel panic, you can add the vbox modules to the list of permanently removed modulesbefore suspend, these modules are loaded automatically after suspend:
root #
echo 'SUSPEND_MODULES='vboxpci vboxnetflt vboxnetadp vboxdrv' >> /etc/pm/config.d/gentoo
See also
- PhpVirtualBox — a web-based administration utility for VirtualBox.
- QEMU — a generic, open source hardware emulator and virtualization suite.
- VMware - A popular closed source virtual machine emulator.
External resources
- vboxweb_rb - Web-based administration utility (Ruby)
- ↑https://www.virtualbox.org/wiki/Guest_resizing
- ↑Section_8. VirtualBox - No sound after update, Gentoo Forums, November 12th, 2019. Retrieved on September 14th, 2020.
When running on Linux hosts with a kernel version later than 2.6.31
, experimental host PCI devices passthrough is available.
The PCI passthrough module is shipped as an Oracle VM VirtualBox extension package, which must be installed separately. See Installing Oracle VM VirtualBox and Extension Packs.
This feature enables a guest to directly use physical PCI devices on the host, even if host does not have drivers for this particular device. Both, regular PCI and some PCI Express cards, are supported. AGP and certain PCI Express cards are not supported at the moment if they rely on Graphics Address Remapping Table (GART) unit programming for texture management as it does rather non-trivial operations with pages remapping interfering with IOMMU. This limitation may be lifted in future releases.
To be fully functional, PCI passthrough support in Oracle VM VirtualBox depends upon an IOMMU hardware unit. If the device uses bus mastering, for example it performs DMA to the OS memory on its own, then an IOMMU is required. Otherwise such DMA transactions may write to the wrong physical memory address as the device DMA engine is programmed using a device-specific protocol to perform memory transactions. The IOMMU functions as translation unit mapping physical memory access requests from the device using knowledge of the guest physical address to host physical addresses translation rules.
Intel's solution for IOMMU is called Intel Virtualization Technology for Directed I/O (VT-d), and AMD's solution is called AMD-Vi. Check your motherboard datasheet for the appropriate technology. Even if your hardware does not have a IOMMU, certain PCI cards may work, such as serial PCI adapters, but the guest will show a warning on boot and the VM execution will terminate if the guest driver will attempt to enable card bus mastering.
It is very common that the BIOS or the host OS disables the IOMMU by default. So before any attempt to use it please make sure that the following apply:
Vbox Communication Sound Cards Free
Your motherboard has an IOMMU unit.
Your CPU supports the IOMMU.
The IOMMU is enabled in the BIOS.
The VM must run with VT-x/AMD-V and nested paging enabled.
Your Linux kernel was compiled with IOMMU support, including DMA remapping. See the
CONFIG_DMAR
kernel compilation option. The PCI stub driver (CONFIG_PCI_STUB
) is required as well.Your Linux kernel recognizes and uses the IOMMU unit. The
intel_iommu=on
boot option could be needed. Search for DMAR and PCI-DMA in kernel boot log.
Once you made sure that the host kernel supports the IOMMU, the next step is to select the PCI card and attach it to the guest. To figure out the list of available PCI devices, use the lspci command. The output will look as follows:
The first column is a PCI address, in the format
. This address could be used to identify the device for further operations. For example, to attach a PCI network controller on the system listed above to the second PCI bus in the guest, as device 5, function 0, use the following command: bus
:device
.function
To detach the same device, use:
Please note that both host and guest could freely assign a different PCI address to the card attached during runtime, so those addresses only apply to the address of the card at the moment of attachment on the host, and during BIOS PCI init on the guest.
Vbox Communication Sound Cards Online
If the virtual machine has a PCI device attached, certain limitations apply:
Only PCI cards with non-shared interrupts, such as those using MSI on the host, are supported at the moment.
No guest state can be reliably saved or restored. The internal state of the PCI card cannot be retrieved.
Teleportation, also called live migration, does not work. The internal state of the PCI card cannot be retrieved.
No lazy physical memory allocation. The host will preallocate the whole RAM required for the VM on startup, as we cannot catch physical hardware accesses to the physical memory.
Copyright © 2004, 2020 Oracle and/or its affiliates. All rights reserved. Legal Notices