Re: El Capitan?
Posted: 9. Oct 2015, 18:59
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.
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.