virtualbox.org

socratis wrote:tsubery had the 970M. Is the "M" for mobile? Are you tsubery(970M) and Poison(980M) both on laptops?

Yes, the M is for mobile.

Update:
I'm trying now "VMware workstation" and it works fine with 3d acceleration. During the configuration of the vm it marked 768MB of video memory as recommended. Is it possible that 128 is not enough and the instability is due to lack of video memory? I'm using a 4k 60Hz screen over display port.

tsubery wrote:During the configuration of the vm it marked 768MB of video memory as recommended. Is it possible that 128 is not enough and the instability is due to lack of video memory? I'm using a 4k 60Hz screen over display port.

I won't comment on what VMWare recommends, but in VirtualBox the virtual graphics memory is not used for 3D acceleration (accelerated rendering is done by the host, not the guest), so the amount of virtual graphics RAM isn't relevant. Even 128MB is probably only there for placebo value.

Not sure if this is relevant, but it sounds similar.

I had two working linux VMs (Ubuntu and Mint) running on Windows 10. Worked OK when last used about 6 weeks ago. Today, both VMs bricked when run; they wouldn't boot. I could create a new Ubuntu VM, which mostly worked, but when I loaded Cinnamon, it would run only in software rendering mode, suggesting something wrong with 3D graphics.

I didn't think I had updated the host NVIDIA drivers since the VMs were last working, but maybe I did. I can remember sometime reloading the NVIDIA stuff and not loading the 3D elements of the driver. Anyway, on updating today to 376.33, checking advanced mode and checking both of the optional 3D parts of the driver, Cinnamon then worked OK , and the two bricked VMs started working again.

Sorry if that's unrelated, just mentioned it in case this thread's issue might be fixed by the latest NVIDIA drivers.

PS - I also first suspected a Guest Additions problem, as that affects 3D rendering with Cinnamon, but it seems it wasn't that.