El Capitan?

[FW-Alex]

So since I am reliant on my Windows VM to do my job, I just wanted to say what I tried yesterday. I'm no longer planning to continue working to fix this in VBox, I moved onto another solution.

For anyone who is continuing on fixing this in VBox though, I will let you know what I found out and what I tried, so this can hopefully be solved for other impacted users.

Yesterday I ported my VM over to VMWare Fusion on a 30 day trial. I wanted to see if I had the same problem. I did, but it was MUCH less pronounced.

I think the 256MB limit on GPU memory in VirtualBox is a big factor. I'm sure Windows 10 will run fine on a system with a crappy GPU with the right settings and driver tweaks, but I don't think the VirtualBox guest drivers are optimal. Not sure why El Capitan escalated this for me, but it could be related to this? http://lifehacker.com/how-to-see-all-th ... 1735489877 I originally set up VMWare with 512MB of GPU memory, but after it was still a tiny bit slow, so I moved it up to 1GB and the problem was much reduced. Then finally, I disabled some 3d effects within Windows too and that helped a lot as well: https://www.winhelp.us/disable-visual-e ... ndows.html I'm back to where I was before El Capitan.

Of note, too, I will probably wind up ponying up for VMWare Fusion after the trial, because I can run my VM in full 5120x2880 resolution, instead of the scaled 2560x1440 - this is new to VMWare apparently as of the release in late August. As much as I would rather use a free solution, I'm spoiled now, so VirtualBox will need to add support for this for me to consider a switch back, or I will pay for the VMWare license at the end of 30 days.

Finally, regarding the test build, whether it addresses the problem or not, my bug has not had any updates marked on it.

[loukingjr]

Alex, I'm just curious about something. Does Windows 10 run as fast in Fusion as it did in VirtualBox before you updated to OSX 10.11? I'm asking because on my 27" non-Retina iMac, running VB 5.0.6 and OSX 10.11, my Windows 10 guest is faster than it is running natively on my 7 month old ASUS ZenBook.

[FW-Alex]

Alex, I'm just curious about something. Does Windows 10 run as fast in Fusion as it did in VirtualBox before you updated to OSX 10.11? I'm asking because on my 27" non-Retina iMac, running VB 5.0.6 and OSX 10.11, my Windows 10 guest is faster than it is running natively on my 7 month old ASUS ZenBook.

It runs just as fast or faster than it did in VBox 5.0.0, before my El Capitan issues. I have similar performance with Win 10 as a guest that I did with a physical Dell XPS 27 running Windows 8.1 with an ivy bridge i7 and 16 GB of memory. I had a Macbook air as my app development machine and the Dell as my windows/web development machine, and when it came time to update, I couldn't say no to the 5k display.

[loukingjr]

Thanks for the reply. I have a hard time telling the difference between running Window 10 in VirtualBox or Fusion. Either way, they're both faster than my laptop.

[MichMich]

Yes. Uninstall Elmedia Player. This file "com.eltima.kext" caused numerous problems for people trying to run OSX 10.11 betas and I assume the OSX 10.11 release.

That did the trick! Thanks!

[loukingjr]

welcome.

[Rafaal]

Hi!

I am new in this blog. I hope i am in the correct place.
I am using dorid4x to emulated Android on my mac. Dori4x use VB to run. The process VBox Headless takes extrem to much energy from my computer.
I want to know if is there an option to reduce this consumption or enter to a power nap from VB.

Thanks

[loukingjr]

Droid4X is not supported on this forum.

[loukingjr]

I entered a ticket - 14682. I don't have time to continue to tweak settings on this at the moment, since I'm at work.

The whole power save gpu thing - there may be something there, but I've been running this setup for a few months with no problems and no settings changes required until the El Capitan upgrade.

FWIW, I just received my Late 2015 27" iMac Retina yesterday and I have no guest or guest additions issues running VirtualBox 5.0.8 on OSX 10.11.1. so I'm not sure what your issue may have been.