VirtualBox

Custom Query (16363 matches)

Filters
 
Or
 
  
 
Columns

Show under each result:


Results (1801 - 1803 of 16363)

Ticket Resolution Summary Owner Reporter
#16701 duplicate Virtualbox Linux 5.1.20 (Ubuntu 16.04) missing Host ALSA Audio Driver Mine
Description

I upgraded to 5.1.20 FROM 5.1.18, applied the correct extension pack and reinstalled the guest tools in my Windows 10 VM.

Everytime I boot the guest I get a warning that the Host Audio ALSA Driver (that I have selected in the VM settings) is missing and that it is defaulting to the NULL Audio Driver. I'm using the ICH AC97 controller too.

I can shut the guest down and switch to the Pulse Audio Driver and I get sound again in the guest but it cracks a little in the audio.

I uninstalled 5.1.20 and went back to 5.1.18, downgraded the extension pack and reinstalled the guest tools and switched back to ALSA audio and BOOM ... audio is back and sounding correct.

#16700 duplicate Virtualbox Linux 5.1.20 (Ubuntu 16.04) missing Host ALSA Audio Driver Mine
Description

I upgraded to 5.1.20 FROM 5.1.18, applied the correct extension pack and reinstalled the guest tools in my Windows 10 VM.

Everytime I boot the guest I get a warning that the Host Audio ALSA Driver (that I have selected in the VM settings) is missing and that it is defaulting to the NULL Audio Driver. I'm using the ICH AC97 controller too.

I Can shut the guest down and switch to the Pulse Hot Audio Driver and I get sound again in the guest but it cracks a little in the audio.

I uninstalled 5.1.20 and went back to 5.1.18, downgraded the extension pack and reinstalled the guest tools and switched back to ALSA audio and BOOM ... audio is back and sounding correct.

#16698 invalid Stderr: VBoxManage: error: The host network interface named 'vboxnet3' could not be found Lucky27
Description

Hi,

I'm trying to run virtualbox and vagrant inside a docker redhat 7 container, I'm using image similar to this https://hub.docker.com/r/blacklabelops/virtualbox/. Using 5.1.20 of virtualbox and vagrant 1.9.3.

I'm getting below error when I try to run vagrant inside container with this setting in Vagrantfile config.vm.network "private_network", ip: "10.0.10.21".

There was an error while executing VBoxManage, a CLI used by Vagrant for controlling VirtualBox. The command and stderr is shown below.

Command:

["hostonlyif", "ipconfig", "vboxnet3", "--ip", "10.0.10.1", "--netmask", "255.255.255.0"]

Stderr:

VBoxManage: error: The host network interface named 'vboxnet3' could not be found
VBoxManage: error: Details: code NS_ERROR_INVALID_ARG (0x80070057), component HostWrap, interface IHost, callee nsISupports
VBoxManage: error: Context: "FindHostNetworkInterfaceByName(Bstr(pszName).raw(), hif.asOutParam())" at line 231 of file VBoxManageHostonly.cpp'''

It works If I remove above setting from vagrantfile..I'm mounting /dev/vboxdrv and /dev/vboxnetctl from host to the container..Could you pls let me know If I need to mount any other files or need to update the container?

Batch Modify
Note: See TracBatchModify for help on using batch modify.
Note: See TracQuery for help on using queries.

© 2024 Oracle Support Privacy / Do Not Sell My Info Terms of Use Trademark Policy