virtualbox.org

Hey all,

I have been using VirtualBox for 2 years now and I love it.
I use it for work to keep everything separated from my host machine and this works great for me.
The other week windows decided to do an update and since that update VirtualBox has not been playing well.

I have had a look around on google an on here and found no resolution to my issues, which is why I am creating this post.
Before I go into my issue, I will describe my setup:

Host
OS: Windows 10 Enterprise 64bit
Proc: Intel i7-4790 @ 4GHz
RAM: 16GB

Guest
OS: Windows 10 Enterprise 64bit
RAM: 6GB

It is also worth mentioning that my monitor is ultra wide using a resolution of 3440x1440.
Ok, so the first issue is to do with the display.

For some unknown reason the display drive keeps crashing which resets the resolution to 1024x768. This happens a lot and is frustrating. After searching the internet, the only solution is to re-install guest additions and not to perform a restart. This (somehow) fixes the issue until it crashes again.
It is only a temporary solution and it can get quite annoying as it happens a few times a day.

The second issue is to do with launching a saved state; when I run the VM after it has been saved it keeps the time from when it was saved and does not update to my host machines time (as it should) which is really annoying because things like API calls reject with errors if the time is wrong (I am a developer). The only solution to this issue is to restart the guest machine or to never use saved instances (not likely!).

So, does anyone know how I can solve these issues?
I have attached my recent log (I had to remove some of it because the filesize was too big, I removed the text after I powered down as I "assume" that won't be needed ).

Cheers,
r3plica

r3plica wrote: For some unknown reason the display drive keeps crashing which resets the resolution to 1024x768.

Not a lot can be said unless you provide details of the crash. The log is a log of activity on the host, it will not show guest executables crashing. Usually however the crashing is due to 3D acceleration and dodgy host OpenGL drivers.

r3plica wrote: The second issue is to do with launching a saved state; when I run the VM after it has been saved it keeps the time from when it was saved and does not update to my host machines time (as it should).

As it should - why? A saved state is what it says: the guest will be restored to the state it was in when the state was saved. Normally the guest OS will query a network time server soon after restart which will correct the time, however it is possible for you to interfere with that in many ways, none of which is a VirtualBox issue.

Thanks for your reply

I don't have 3d acceleration turn on on the guest machine. My drivers on my host are up to date (not using windows generic drivers, using nvidia geforce experience).
I did try disabling 2d accelaration too, but that just caused the guest to be sluggish so I re-enabled it.
The crash seems to happen if my guest OS is minimised, if I leave it for a while.

As for the time, I read that it should use the same time as the host and even after a restored state it "used to" bring the time back inline with the host. Now it doesn't.
Is there a way that you know of to force it to update to the host?

r3plica wrote: I don't have 3d acceleration turn on on the guest machine.

The log appears to say otherwise. Starting on line 1164 is a whole load of OpenGL capabilities, which IME are only reported when 3D acceleration is enabled.

It's definitely unchecked in the settings, which bit of the log shows you that it is on?

I gave you that information already - I quoted the line number. Plus there's the following on line 1257 :-

00:00:40.571219 VMMDev: Guest Log: VBoxMP::DriverEntry: VBox WDDM Driver for Windows 8+ version 5.0.12r104815, 64 bit; Built Dec 18 2015 16:00:07
00:00:40.571376 VMMDev: Guest Log: VBoxMP::DriverEntry: OsVersion(10, 0, 10586)
00:00:40.571647 VMMDev: Guest Log: VBoxMP::VBoxMpCrCtlConConnectHgcm: WARNING! :vboxCrCtlConConnect failed, rc (-3302)
00:00:40.571743 VMMDev: Guest Log: VBoxMP::VBoxMpCrCtlConInit: VBoxMpCrCtlConConnectHgcm failed with rc(-3302), 3D not supported!
00:00:40.571820 VMMDev: Guest Log: VBoxMP::DriverEntry: 3D is NOT supported by the host, falling back to display-only mode..
00:00:40.695081 VMMDev: Guest Log: VBoxMP::vboxWddmPickResources: found the VBE card
00:00:40.696358 VMMDev: Guest Log: VBoxMP::DxgkDdiStartDevice: using HGSMI

Implying that the VM thinks that 3D acceleration is required, and there's a problem with it.

I suspect that in fact it is enabled, but the settings dialog shows it as off and disabled since it isn't available. If you looked at the VBox file you'd see what I mean.

Missed the line number before, sorry
I will edit the settings again and enable then disable the 3d acceration because I don't need it.

I also ran across this post: https://bbs.archlinux.org/viewtopic.php?id=189067 which suggests that extensions might be an issue. I did have an extension so I have removed it and started my vm again. I will wait until the display driver crashes before I change the settings just to make sure that it isn't the extension (although I did update it the other day).

I will let you know if any of them work or not. Thanks for your help so far.

Removing the extension didn't fix the graphics issue, I have now changed the setting for 3d acceleration (by checking and unchecking it).
Hopefully this will solve it.

Changing the settings didn't fix it either

This is still happening, anyone have any idea how to solve it?