virtualbox.org

Hi,

Running current VirtualBox for Linux v6.0 on a fully updated Kubuntu 18.04 LTS 64Bit Linux host.
(Linux host is running an nVidia GeForce GTX 970 with nVidia proprietary Linux display driver v415.25)

I can install Windows 10 Pro 64Bit 1809 ISO into a VirtualBox guest but have severe issues:

With 2D acceleration enabled and 3D acceleration enabled after guest addition install I have severe flickering in Win 10 guest.?
With 2D acceleration enabled and 3D acceleration disabled after guest addition install I lose mouse and keyboard input in Win 10 guest?

Is current Linux Virtualbox v6.0 compatible with Win 10 1809 guest?
Any ideas?

Jesse

We need to see a complete VBox.log, from a complete VM run, where the problem occurs:

• Start the VM from cold-boot (not from a paused or saved state) / Observe problem / Shutdown the VM (force close it if you have to).
• With the VM completely shut down (not paused or saved), right-click on the VM in the VirtualBox Manager and select "Show Log".
• Save only the first "VBox.log", ZIP it and attach it to your response. See the "Upload attachment" tab below the reply form.

Attached requested log...

This is a fresh install of Win 10 Pro 64Bit
followed by a full Windows update.

Followed by Windows guest additions installation.

Got no mouse and no keyboard.
2D acceleration is enabled and 3D acceleration is disabled.

Weird thing is after reboot of guest the screen is messed up and unreadable.
Sometimes when I resize the screen gets fixed.
Also when I click with mouse or type with keyboard nothing happens
but if I click outside of VM onto Linux desktop then the VM updates the screen with click or typing shown?

Weird, hope this can be fixed as I need a working Win 10 VM and VMWare Player is 100% broken ATM.
Thanks!

Jesse

Could you change the VM Settings » Display » Screen » Graphics Controller, from VBoxSVGA to VBoxVGA? See if that improves the situation.

socratis wrote:Could you change the VM Settings » Display » Screen » Graphics Controller, from VBoxSVGA to VBoxVGA? See if that improves the situation.

Hi,

VM is fully operational now, thanks!
(changing to "VBoxVGA" solved it)

Jesse

Great, thanks for letting us know, VBoxSVGA is brand new and still has issues. And thank you for marking the topic as [Solved]...