[Solved] Launch windows 10 as guest always crash the X host

[arnome]

Hi everyone,
I'm in big trouble after setup VBoxGuestAdditions 5.0.16 on Windows 10 as guest. The host is a Debian GNU Linux sid with a 4.4.0-1-amd64 kernel, virtualbox version is 5.0.16-dfsg-2 and virtualbox-ext-pack version is 5.0.16-1. The problem is highly reproductible : since I setup VBoxGuestAdditions on the windows 10 guest to 5.0.16 (donwload from virtuabox dot org ) my host's graphical interface (gnome 3.18.4-1, xserver-xorg-video-nouveau version: 1:1.0.12-1+b1r) and guest completely freeze but the host is still reachable throw ssh. I can only reboot with the magic key (Alt-Imp Screen-b). I make some udev rules to change the group of vboxdrvu and vboxnetctl to vboxusers :

Code: Select all

> $ ll /dev/vbox*                                                                                     
crw------- 1 root root      10, 57 mars  23 15:33 /dev/vboxdrv
crw-rw---- 1 root vboxusers 10, 56 mars  23 15:33 /dev/vboxdrvu
crw-rw---- 1 root vboxusers 10, 55 mars  23 15:33 /dev/vboxnetctl 

After this change the startup go far away but still crash after the login attempt to windows 10. The guest is on a local network. Before the installation of the VBoxGuestAdditions 5.0.16 there is no VBoxGuestAdditions and windows 10 guest works just fine.

I've no idea what to do next... Any help is welcome.
arnome.

[mpack]

You are using the Debian fork of VirtualBox. If you want support on the VirtualBox forums you need to be using VirtualBox, not someone's who-knows-what-they-changed fork.

You need to either install the official version, and then we'll see if you still have a problem, or else go to the Debian forums for support.

[arnome]

Hi,

I try the first solution and follow the "Debian-based Linux distributions" way from https://www.virtualbox.org/wiki/Linux_Downloads. So I've install virtualbox-5.0 official package and the problem still remain exactly the same. My system freeze but will be still reachable throw ssh and only magic-key can restart it. I put the new log files in attachment.

Thank's a lot for help,
arnome.

[mpack]

What version of Windows 10 is it? Build number please.

You log shows a lot of these, leading up to the crash :-

00:01:18.574266 VMMDev: Guest Log: VBoxMP::DxgkDdiQueryCurrentFenceNew: WARNING! :=>DxgkDdiQueryCurrentFenceNew
00:01:18.574425 VMMDev: Guest Log: VBoxMP::DxgkDdiQueryCurrentFenceNew: WARNING! :uncompleted fences, u32FenceSubmitted(2084), u32FenceCompleted(2081) u32FenceProcessed(2081)
00:01:19.533335 VMMDev: Guest Log: VBoxMP::DxgkDdiQueryCurrentFenceNew: WARNING! :uncompleted fences, u32FenceSubmitted(2084), u32FenceCompleted(2081) u32FenceProcessed(2081)
00:01:20.496745 VMMDev: Guest Log: VBoxMP::DxgkDdiQueryCurrentFenceNew: WARNING! :uncompleted fences, u32FenceSubmitted(2084), u32FenceCompleted(2081) u32FenceProcessed(2081)
00:01:21.474549 VMMDev: Guest Log: VBoxMP::DxgkDdiQueryCurrentFenceNew: WARNING! :uncompleted fences, u32FenceSubmitted(2084), u32FenceCompleted(2081) u32FenceProcessed(2081)

I don't believe this is a VirtualBox problem, I think the host 3D graphics driver is crashing. You might want to check for driver updates.

If you Google search for "DxgkDdiQueryCurrentFenceNew" you should find previous discussion of similar problems. It only seems to affect Linux hosts.

The only other thing I notice is that the OpenGL capabilities seem to be dumped to the log several times, sometimes back to back. As if perhaps OpenGL is being initialized several times. I generally expect see this only once, maybe twice. I don't know if it's significant... or does the guest think it has multiple graphics cards?

I assume you already know that you could work around this error by disabling 3D acceleration in the VM settings: that's what causes the VM to require OpenGL.

[arnome]

Hi,

I assume you already know that you could work around this error by disabling 3D acceleration in the VM settings: that's what causes the VM to require OpenGL.

no, I don't know but this the solution !!! So you're right, this is a nouveau driver problem more than a VBoxGuestAddtions setup. I've disabling the 3D acceleration and the guest Windows 10 Professional (10586.164) works nice now.
Thank's a lot.
arnome.

[mpack]

I see you marked the problem as solved - I appreciate the feedback and will leave it that way, but I'd just like to note for future reference that I regard this as a workaround, not a solution. It has the downside that some graphics functions will be slower, but the importance of that depends on individual usage patterns (e.g. video game play and no 3D acceleration == not good).

A better long term solution would be graphics drivers that don't crash.