virtualbox.org

beikaigun wrote:First - I'm kind of curious as to why you thought I was using snapshots. I never have, should I be?

I don't use Snapshots except for occasional testing.

The reason I thought you might be is because there were so many guest addition lines and in one log there were lines for both 4.3.20 and 4.3.22 GAs listed and the only time I've seen that is when I accidentally updated the GAs on a guest that still had a Snapshot I forgot to remove. No biggie.

I have yet to use them. The log probably contains reference to both since I was upgrading.

I also noticed that the 4.3.22 build has a Windows 10 base option when creating a VM. I've started building a new one, but didn't have time to finish just yet. Maybe it will work better....

Unfortunately, the Windows 10 build simply made it easier to get to the point of failure. I attempted with both the 4.3.22 and 4.3.23 drivers to no avail. No 3D capability is currently available for Windows 10.

Attach the vbox.log (compressed) for the guest.

This is from the one that was updated to GA 4.3.23.

This is from the straight build with 4.3.22.

It happens for me too, on Arch. Random interval, Windows 10 latest on a Latitude E6540.

bernat wrote:It happens for me too, on Arch. Random interval, Windows 10 latest on a Latitude E6540.

There is no official VirtualBox build for Arch Linux so you might have better luck finding help in the Arch Linux forums.

Okay, I've come back to this with the latest 4.3.28 and the problem still exists as described.

One thing I'm noticing when I dig around is that those using Windows as a host are not running into this error at all. I'm wondering if it might have something to do with the host OS using the same drivers as the guest.

I'll be digging around more as time allows. I'm just wondering if anyone else is seeing similar behavior with linux as the host.