The experience with VBox 5.2 is that it works just as expected. I don't think end-users really care what the "proper" option is here, they just want things to work out-of-the-box. Wouldn't the issue be with VirtualBox in this case?Įither way it seems a little bit finger pointy to keep saying that VBoxSVGA is the wrong option and to use VMSVGA which is the intended option (and is the default). I know it's being said that it's a "Kernel bug" - but if the software used to emulate an expected result (which is to have a mouse visible) works on other hardware, etc.
Switching to VboxSVGA appears to fix this as others have mentioned, and gives the expected result. Everything was working perfectly prior to the upgrade, and suddenly when VirtualBox changes (all other variables remain the same) - suddenly the mouse has disappeared completely. I just came from VirtualBox 5.2 to 6.0 and immediately ran into this bug.
0 kommentar(er)
