1) Try to increase the virtual video memory to 1024mb (or set to max, can't remember the maximum allowed size) and lower the virtual RAM memory accordingly.
2) Some users have had similar problems:
http://forums.linuxmint.com/viewtopic.php?f=49&t=119695
I had same problem running Min13 64 on a windows xp x64. The problem
was related to chipset and audio controller used during virtual
machine creation. Now using PIIX3 and ICH AC97 and after reinstalling
Mint, both video and audio works smoothly
I had the same problem with xfce version. It turned out to be a simple mistake - I've chosen Ubuntu as OS option while creating VirtualBox machine. Once I recreated it with Ubuntu64 and reinstalled Mint, everything became fast and nice (2G on 1 CPU). No need to install additions either as they appear to be included with the distro.
3) There's a tutorial to make firefox faster: http://community.linuxmint.com/tutorial/view/338
Before making any changes, please make a backup of .mozilla/firefox/--------.default/prefs.js for your own safety. prefs.js is a file that stores all of your history and bookmarks from Firefox.
First open Firefox.
Type "about:config" (without quotes) in the Firefox address bar and then click "Enter". This command opens a configuration page that allows the user to change advanced system settings in Firefox.
Speed up page loading/rendering time in Firefox. Right-click anywhere in the "about:config" window, click on "New" and then select "String". Name the string "nglayout.initialpaint.delay" (without quotes). Enter a value of "0" and then click "OK". This tweak decreases the amount of time Firefox waits to render a page from 250 milliseconds to zero. Make the same process and name the string "content.notify.interval" and enter a value of "0".
Force Firefox to release reserved system RAM when the browser is minimized. Right-click anywhere in the "about:config" window, click on "New" and then select "Boolean". Name the entry "config.trim_on_minimize" (without quotes). Change the value to "True" and then click "OK". This setting forces Firefox to only reserve about 10 MB of system memory while minimized.
Normally Firefox only sends one or two tunnels to the website. However, the more tunnels you use the faster you go. To change this, type in filter bar "network.http.pipelining.maxrequests" and change the value to "150".
Attention: The more tunnels you use, the more bandwidth you use, meaning you could use as tunnels as you want but that would probably kill the sites bandwidth if everyone did that. 150 is a very good value.
Type "network.http.pipelining" in filter bar, and set it to "True" by double clicking it.
Type "network.http.proxy.pipelining" in filter bar, and set it to "True" by double clicking it.
4) Also try to backup your firefox settings and reset your Firefox to default:
In short, head to about:support
(or from the menu Help > Troubleshooting Information) and hit the reset button. You will have to reinstall your data and extensions.
Upon much digging this is currently possible but only with limited configurations, specific host OSes, and the use of enterprise software.
Windows Server 2016 and above but with Hyper-V
- This is only possible with Windows Server as the host and Hypervisor. It is not available with windows 10 pro as the host as stated in the question above.
Ubuntu 18.04 and above with Virtualbox
- The guest and host have to both have a Linux kernel that has been compiled with IOMMU support, including DMA remapping, according to the virtualbox documentation. This is done by default in the latest version of Ubuntu.
- The command
find /sys | grep dmar
and dmesg | grep IOMMU
will tell you if the kernal has been compiled with IOMMU support. DMAR: IOMMU enabled
is what you are looking for.
Windows 10 Pro but with VMware Workstation Pro 15 or VMware ESXi
- VMware allows for a couple of ways for GPU passthrough or sharing with the guest VM systems. Again, VT-d or AMD IOMMU has to be enabled on the host.
Best Answer
I realize a few years have passed but wanted to answer since this post shows up pretty high when you google for "virtualbox 3d multiple GPU". In the time that has passed, things have gotten a lot simpler and better.
People that stumble upon this thread will likely land here because they have a laptop or PC that has two GPU's, which is quite common these days -- especially on gaming laptops. The onboard Intel GPU is used for rendering windows and general applications, but applications that make use of GPU 3D functionality should do that via the higher performing Nvidia GPU.
Today, I was building an Ubuntu VM on my laptop to do some cross-platform development, and everything was fine except the guest VM was extremely slow, and there was no explanation for it because CPU, memory, disk were all showing low utilization.
It didn't take long to figure out it was video performance that was causing the problem. Launching applications, maximizing/minimizing windows -- anything that we take for granted in 2019 but needs 3D acceleration to work at any reasonable speed -- was using GPU 0.
It was easy to determine this because Windows 10 now has the ability to see GPU utilization using "task manager", then the "performance" tab. And I could see as I moved windows, maximized, minimized, that was being done through GPU on the host. That GPU on the host is the integrated Intel HD GPU, and I wanted to use the NVidia GTX-1050ti, which was GPU1.
After searching around I didn't really find anywhere where you could specify which GPU to use. But this thread, and some others, reminded me that on these kind of setups you have to go into the NVidia control panel, then "manage 3d settings", then the "Program Settings" tab.
You won't likely find "Virtualbox" in the list. But you can press the "Add" button, and add virtualbox.exe. You may have to drill down the drive/path where your virtualbox installation is. Once you have added it, in the settings below make sure that item 2. "Select the preferred graphics processor for this program" is set to the GPU that you want it to use, which in my case was "HIgh-performance NVIDIA processor".
Don't set it to auto, and certainly don't set it to integrated. Of course, you need the VM settings set with the 3D acceleration box ticked, and you need the guest additions installed on the host. But once you have set the host video 3d settings as described above, shutdown the guest VM, exit virtual box, and then re-launch virtualbox and the VM.
If you use task manager|performacne and look at the "virtualbox manager" process and watch what GPU gets used when you navigate the guest VM's UI, you should see it using the better GPU now. See the image pasted below.
All that said, don't expect to be able to run games in a guest VM. 3D acceleration pass thru still is not quite that far along. But you can expect to have a modern OS and UI in your guest, and have an acceptable experience. One would be able to play older games in the guest VM, like anything based on directX9. Unfortunately, as the ability to virtualize GPU eveolves, the 3d gaming technology evolves quicker.