Recently I installed VirtualBox 6.1 on my MacBook Air and installed Windows 10 on it (https://developer.microsoft.com/en-us/microsoft-edge/tools/vms/), but somehow the sound on my guest Win10 is not working. I managed to dig for some info and found out that I need to install (https://www.realtek.com/en/component/zoo/category/pc-audio-codecs-ac-97-audio-codecs-software) but it does not work. Could anybody help me with this one?
EDIT: I get the error when I hover over the sound icon: "no audio output device is installed"
Fixing the sound on guest windows 10 where the host is Linux / Mac
Open the settings for your Windows 10 machine inside of virtualbox
Go to Audio > Host Audio Driver, change to "ALSA Audio Driver"
Go to Audio > Audio Controller, change to "ICH AC97"
Enable Test Mode on Windows 10 and reboot machine.
Download and install the Realtek driver for Vista/Win7 (32/64 bits) Driver only (ZIP file) from here and reboot your Windows 10 machine.
Disable test mode from the link in 4th step then reboot your Windows 10 machine.
In case you still have a crackling / popping sound
In the task bar, right click on the sound icon and choose playback devices
Double click on Speakers
Select the Advanced Tab
Set the Default Format to 16 bit, 44100 Hz (CD Quality)
In the Exclusive Mode, Uncheck the Allow applications... etc
Select the Enhancement Tab
Check the Disable all sound effects
Make sure you click apply then OK
The crackling sound would immediately disappear but you could reboot just to verify.
I tried the route in the most upvoted answer but couldn't get Win10 to install the AC97 driver. For me the solution was much simpler: select Audio Controller "Intel HD Audio" in the virtual machine settings (and leave Host Audio Driver to whatever the default was, in my case "Pulse Audio"). Enable Audio Output checked of course, and it should just work like the machine has a sound card.
Crackling is still there even with the stuff about turning off enhancements and exclusivity, but I think that's not going away since I'm trying to play 1080p video and I don't think the virtual machine has quite the kind of video hardware access (and memory allocation) that it needs to play this level of content perfectly smoothly.
Install Guest Additions if you haven't already. More info here for your specific case: https://www.virtualbox.org/manual/ch04.html#additions-windows
Host Linux Mint. Guest Win10. Had 'Guest Additions' installed, 'Host Audio Driver: Pulse Audio', 'Audio Controller: Intel HD Audio'. Sound in Win10-guest, but not in Commandos 2 or Patrician 3.
Installed Realtek drivers (https://realtek-download.com/wp-content/uploads/2014/07/6305_vista_win7_pg537.zip (thank you Wil)). Still no dice.
Win10 said: "No output devices found".
Changed Host Audio Driver to ALSA Audio Driver. And it worked! Thanks everybody.
With Fedora 36 host and Windows Server 22 Standard Desktop Evaluation as guest inside VirtualBox 6.1.34 it automagically worked after enabling sound at guest via:
Mouse Right Klick at (disabled) speakers symbol in Windows taskbar
Mouse Left Klick at "Sounds" (German)
-> See Screenshot
Accepting the prompt enabled sound with all default settings in VirtualBox VM Audio Settings:
Host Driver: ALSA Audio Driver
Controller: Intel HD Audio
VirtualBox 6.1.34 Oracle VM VirtualBox Extension Pack was also already installed here.
Sound tested successfully with Firefox 100 and https://fip.fr -> Rock
Related
I am trying to boot up a saved am using Macbook pro with M1 chip.
I tried the steps given at this answer. But was not able to boot up the VM. Can someone confirm this problem or already found out a solution to it?
I got the error "The virtual machine 'Ubuntu 20.04 64bit 1' has terminated unexpectedly during startup with exit code 1 (0x1)." below:
Had the same issue on Mac OS Big Sur 11.4 when I was trying to add my Ubuntu instance (on Intel tho), nothing suggested here and other topics helped.
Turned out you have to give access (Full Disc Access) to Virtual Box in Settings. Go to Settings -> Security & Privacy -> Privacy -> Full Disc Access -> plus sign (unlock it if needed) -> choose Virtual Box Application -> Open.
After that I was able to choose my Ubuntu image in Finder.
<New user, reputation too low to comment on David's post!>
As per David Leitko's answer, VirtualBox is an x86 (more specifically, AMD64/x86_64) virtualization hypervisor. However, it appears from various discussions I've seen on this topic that many users don't really understand what this really means.
So, it means not only that VirtualBox only runs on x86 CPUs, but also that it requires all the other elements of the x86 platform. These include system memory, various bus controllers (PCI, USB), hard disk controllers, sound cards, graphics, BIOS/UEFI, etc. None of these take the same form on the Apple Silicon platform - i.e. they don't use any of the standards built up in the PC ecosystem over the last 40 years.
So, not only will VirtualBox not work on Apple Silicon, it will never work on Apple Silicon. There will never be any way to run a VirtualBox image that ran on an Intel Mac on an Apple Silicon Mac. Ever.
The canonical discussion thread on the VirtualBox forums that covers this in more detail is here.
VirtualBox is an x86 virtualization hypervisor. It only runs on an x86 platform. See https://www.virtualbox.org
While Rosetta 2 will run many x86 apps very well on an M1 Mac, virtualization products are not supported per this Apple document
I just had the exact same problem after updating my VirtualBox app on MacOS Big Sur. What worked for me was to go to System Preferences - Security & Privacy - General, and then click the Allow button to allow extensions by Oracle (first click the lock symbol in the lower left of the screen and enter your password).
Actually, during installation I got this pop-up window telling me to do this, but I wasn't quite sure what exactly it wanted me to do. Only after getting this error I took the trouble of looking closer, ahem...
Hope this will fix your problem too!
My Macbook Pro mic was working normally but there is a system hang so I have to restore and install new OS Catalina.
However I find out that the mic is not working, when I check in setting, it is not showing signal as I speak.
I search around Google but there is no one have the same issue with me: there is no ‘Internal Microphone’ option in Sound setting.
Please refer to the below images:
Could you please give me some advice, thank you!
I bought a Variense VMU931 inertial measurement unit (IMU) for a robotics project at school, and I am struggling to get it to reliably communicate with my laptop in Ubuntu. I am using C++ with termios to connect to it using 8n1 no parity blah blah blah. I've tried EVERY permutation of settings I can think of, and I still cannot reliably send commands to the IMU.
I called Variense support and spoke to the engineer that wrote their software, and he said it is a known issue. Evidently it works perfectly in Windows (and the Windows demo software worked fine with my device), but neither of us is aware of a significant difference between the USB Serial emulation in Windows and in Linux.
The constructor at the top of this file shows how I am opening and configuring the port:
https://github.com/jsford/FFAST/blob/master/VMU931/src/vmu.cpp
Any help would be great. I've been tearing my hair out over this!
Thanks!
Use the cu utility for running tests with different parameters.
To debug the issue: run the USB packet capture with Wireshark on Linux directly and also on a Windows VM running in VirtualBox/VmWare. Compare the traffic.
Check which kernel module is chosen and loaded for that USB device. Use /sys/ filesystem for that: this virtual fs has information from kernel about what's used. Also, the lsmod-kind of commands show the kernel module usage. The driver choice for USB depends on something like <usb-manufacturer-id>:<usb-product-id>.
Put some printfs into the kernel module to see where is fails. Use the DKMS build system for rebuilding the kernel module. There is a config file somewhere in Linux to blacklist/whitelist the kernel modules - useful to make sure that the right one is loaded.
That's what I was doing to fix a driver of an USB-serial device.
I recently installed windows 7 on VirtualBox and installed battle.net.
When I start battle.net I get this error: http://i.imgur.com/006cpRC.png
I googled a lot but I was not able to find an anwser :/
Also tried to put Windows 7 on VMWare but that resulted in me getting the same error.
Before this I tried downloading the driver for the GPU I have but then I get this error, http://i.imgur.com/kMacwB8.png
Hope you guys can help me :)
You may need to enable 3D acceleration on VirtualBox. By default it is disabled.
The steps to enable:
Right click the Windows 7 VM in Virtual Box and click Settings.
Click the Display category.
Check Enable 3D Acceleration and increase Video Memory as needed.
Install drivers:
While the VM is running, click Devices menu and then Install Guest Additions
Click Run VBoxWindowsAdditions.exe in the popup and run through the installer.
See: http://www.howtogeek.com/124479/how-to-enable-3d-acceleration-and-use-windows-aero-in-virtualbox/ for extra information.
Note that the article states the 3D acceleration is experimental and should run older games, but possibly not newer games. The article was written in 2012, so I'm not sure what the current state is. You should be able to tell if it's enabled by whether or not the Aero interface is usable.
I am running windows 7. I have just finished downloading and converting (using vmware converter) the Windows XP Mode vmware image to a .vmx file for vmware player.
I can then play the Windows XP image fine in VMWare player. There is however and issue where the windows xp screen inside vmware does not take up the whole screen. In face it only takes up a very small area. I've read on some forums that this might be a compatibility issue between windows 7 and windows xp.
Does anyone know how to fix this please?
Install VMWare Tools on the guest XP machine and bounce it. It contains several virtualization drivers among them one for the virtual graphic card. This allows you to dynamically change the screen resolution of the guest, just by resizing the VMWare Player window.