Opened 8 years ago
Last modified 7 years ago
#15603 new defect
VirtualBox 5.1 3D acceleration issues
| Reported by: | John JJ | Owned by: | |
|---|---|---|---|
| Component: | 3D support | Version: | VirtualBox 5.1.0 |
| Keywords: | 3D 5.1 full-screen toobar | Cc: | |
| Guest type: | Linux | Host type: | Windows |
Description
When 3D acceleration is enabled, several odd things happen. By the way, VB 5.0.24 did not have any of these issues.
- Sometimes only a small rectangle of the screen will redraw after boot with VB set to a normal window. It's about the size rectangle as the boot windows.
- The VB mini toolbar and dialogs are hidden in full-screen.
- Can't display full-screen on display 1 when display 2 is primary. It just ignores the menu setting.
- The non full-screen window randomly shifts to my primary monitor on restart.
With or without 3D enabled, and when the VM is set to auto-login, the Ubuntu launcher is randomly invisible at boot time until I click in the VB window, and it immediately appears. Clicking does not consistently make the launcher appear with 3D enabled.
Host: Windows 10 Home, NVIDIA GTX 650 Ti 368.69 Client: Ubuntu 16.04 with VB guest additions 5.1
Attachments (2)
Change History (4)
by , 8 years ago
| Attachment: | VBoxSVC.log added |
|---|
comment:1 by , 8 years ago
I'm seeing acceleration issues with 5.1 as well.
If I have acceleration enabled in 5.1, my guests are drawing at 1/4 size in the top left. Turning off acceleration allows the guests to draw at a more reasonable size. VB5.0 did not have this issue and guests will draw at correct size even with acceleration enabled under that version.
Are you using a 4k screen, like I am? On the host (Ubuntu 16.10), I have scaling in Unity set to scale menu and title bars to 2x.
comment:2 by , 7 years ago
I, too, have not been able to display full-screen Linux VM on the Windows host’s secondary display in all VirtualBox 5.1 versions I tried (5.1.8, 5.1.10 and 5.1.14). Like in the original report, VB just ignores the menu setting and uses the main display. This happens even before Linux boots up.
It has not occurred to me to disable 3D acceleration, though; since the issue is a show-stopper for me, I just went back to 5.0, which has never had this problem. Also, I never use the mini-toolbar, or any mode other than full-screen, so I would not know if there were anything wrong with them.
Host: Windows 10 Pro 64-bit
Display 1: 1920×1080 NVIDIA GeForce GTX 960
Display 2: 1920×1080 Intel HD Graphics 4600
(Display 2 is the main Windows display and is to the right of display 1)
Guest: Ubuntu 14.04.5 LTS 64-bit with VB Guest Additions
The not very interesting log file