VMSVGA estremely unstable under Linux Guests? Guest crash every time
Posted: 19. Jan 2019, 14:10
I tested this new 3D graphic interface on many of my machines and I'm definitely unhappy about it.
In years of Virtualbox use, I did never had an application crash under my WIndows 10 Pro host, actual version 10.0.17763.134 .
I wasn't happy with the previous 3D driver, then with some limitations it worked fine for many needed applications (it had a big bug with some Plasma5 components, like Kwin) with a lot of Linux VM guests, never had an application (VM guest) crash.
With the release of VirtualBox 6 (now I do run 6.0.2, latest update), I switched to VMware SVGA driver with confidence on most of my Linux hosts then I'm pretty much unsatisfied.
The problem isn't it is less than half fast compared to the same implementation under native VMware Workstation or lack of OpenGL 3.x support, the real problem is the crash of any Linux Guest I do run with it enabled.
Like I said, I did never had an application crash in ages with modern Virtualbox. With this driver properly installed and running, often if not always, after some guest normal work, the whole virtual machine stop responding and crash with a memory related error message (the memory could not be read).
I think it surely is related with VMSVGA driver becouse if I switch to VBoxVGA driver I can't get 3D working, then the VM do not crash.
Obviously 3D in configuration interface is selected.
I will continue to use the VBoxVGA driver if it could still offer 3D support (like in VB 5.2 and previous) then I see if afte migration from version 5.2.x I do upgrade my VM tools to the latest with this old driver installed, simply 3D is not available anymore.
There is also a VBoxSVGA driver to choose from, then I do not really know what it is, becouse if I choose it, I'm unable to boot into virtual machines graphical interface if I choose this emulation. Which driver it should load?
Now I do ask if this crash issues under VMSVGA driver are known to users and development and how to eventually fix them. Attention: this crash not happen when you boot the machine, it boot fine and it seems to work ok, even if like I said slow, compared to real VMware, then it will crash the machine with the unable to read memory sometimes soon.
If more infos are needed, just ask. It happen on Gentoo, Fedora, Ubuntu, pretty much all the Linux virtual guests I do have around, up and running and updated. I hope I've been clear.
In years of Virtualbox use, I did never had an application crash under my WIndows 10 Pro host, actual version 10.0.17763.134 .
I wasn't happy with the previous 3D driver, then with some limitations it worked fine for many needed applications (it had a big bug with some Plasma5 components, like Kwin) with a lot of Linux VM guests, never had an application (VM guest) crash.
With the release of VirtualBox 6 (now I do run 6.0.2, latest update), I switched to VMware SVGA driver with confidence on most of my Linux hosts then I'm pretty much unsatisfied.
The problem isn't it is less than half fast compared to the same implementation under native VMware Workstation or lack of OpenGL 3.x support, the real problem is the crash of any Linux Guest I do run with it enabled.
Like I said, I did never had an application crash in ages with modern Virtualbox. With this driver properly installed and running, often if not always, after some guest normal work, the whole virtual machine stop responding and crash with a memory related error message (the memory could not be read).
I think it surely is related with VMSVGA driver becouse if I switch to VBoxVGA driver I can't get 3D working, then the VM do not crash.
Obviously 3D in configuration interface is selected.
I will continue to use the VBoxVGA driver if it could still offer 3D support (like in VB 5.2 and previous) then I see if afte migration from version 5.2.x I do upgrade my VM tools to the latest with this old driver installed, simply 3D is not available anymore.
There is also a VBoxSVGA driver to choose from, then I do not really know what it is, becouse if I choose it, I'm unable to boot into virtual machines graphical interface if I choose this emulation. Which driver it should load?
Now I do ask if this crash issues under VMSVGA driver are known to users and development and how to eventually fix them. Attention: this crash not happen when you boot the machine, it boot fine and it seems to work ok, even if like I said slow, compared to real VMware, then it will crash the machine with the unable to read memory sometimes soon.
If more infos are needed, just ask. It happen on Gentoo, Fedora, Ubuntu, pretty much all the Linux virtual guests I do have around, up and running and updated. I hope I've been clear.