Leandro Hermida

> This issue is also reported in https://communities.vmware.com/t5/VMware-Workstation-Pro/VM-Crash-16-2-1-build-18811642/m-p/2878409/highlight/false#M172530 , a fix is made in the next major VMware Workstation release. Please disable 3D in the VM config as a workaround...

> Thank you, > Filed an internal ticket to track this. Thank you, it’s good to try and get support for it since the default filesystem has been btrfs for...

I can confirm the same, I've tested both Fedora 25 and 26 identical VM guest installs, using Xorg (not Wayland), and tested using open-vm-tools or proprietary VMWare Tools. GNOME desktops...

Thanks for the additional workaround @josepmc, may I ask though is this any different or better performing than my workaround where you disable VMware 3D hardware acceleration for the VM?...

I can also confirm that on the latest VMware Workstation 14 Pro (14.0.0 build-6661328) this major problem still exists. I created a brand new Fedora 26 guest OS using my...

Hi - sorry I should've mentioned this, when troubleshooting I did turn off hybrid graphics in BIOS and play around with Nvidia control settings and it doesn't matter the GNOME...

@thomashvmw I've had a support ticket open with VMware regarding this issue and they had me generate all this extra logging of the failing VM, the logs don't seem to...

Ok I started up the new Fedora 26 guest OS I made and after a couple minutes as usual GNOME froze, I sshed into it and ran dmesg, here's the...

I restarted the VM and ran dmesg again while GNOME is working and unfortunately that message is the last line in the dmesg log after startup: ``` [ 16.373174] vmtoolsd[2152]:...

Here you go, used the GNOME desktop on restarted VM and let it freeze again [vmware.log](https://github.com/vmware/open-vm-tools/files/1352374/vmware.log)