![]() If someone has a VM the frequently locks up, and finds an error in the "dmesg" guest log or the Xorg log (typically /var/log/Xorg.0.log) in the guest, that would be of great help. This will still have the VM think that 3D is available, but will direct all VM 3D operations to Workstation's own software 3D renderer rather than to the host's DX11 subsystem, so things will be a bit slow.Ĭ) Check whether the VM still locks up, and regardless of the result, please post the "vmware.log" file present after the run in the "Locking" VM folder on the host. If someone has a VM that frequently locks up (Let's call it "Locking"),Ī) Locate the "Locking" VM folder on the host.ī) Edit the "Locking.vmx" file by adding the following two lines at the end: ![]() If you have the possibilty to run any (0-2) of these tests, it would be helpful. Unfortunately we have not been able to reproduce this in-house, so we do need some more help to pinpoint which component is at fault. I haven't yet seen anyone say this exact issue happens on HD? is yours 4K? The reason I ask to use a 4K display is because it seems like it might be that this configuration is causing VMWare Workstation to have problems. The GNOME desktop will always eventually completely freeze. I wholeheartedly believe that if the VMware Workstation development team or the open-vm-tools development team took a Windows 10 computer with VMWare Workstation 12.5.x or 14.x and a 4K monitor and installed Fedora 26 guest OS with 3D acceleration turned on they will see this issue within 10-15 minutes of use. Turning off 3D acceleration is not a workaround the desktop is really unusable if you do that. My workaround is to simply use Fedora 24 as guest OS but eventually that will be a problem because for one reason or another I will need to upgrade. Most modern Linux graphical desktops need it to function properly that's why it's a major issue for me and others because you effectively cannot use VMware Workstation with any late guest OS. Here we are describing a major issue where GNOME, on guest Linux OSes Fedora 25 and Ubuntu 17.04 and newer, will always freeze if you have VMware 3D acceleration turned on.īy default 3D acceleration should always be on. Reply to this email directly, view it on GitHub, or mute the I think yours is a different issue. You are receiving this because you were mentioned. ![]() I hope the open-vm-tools team can figure out why, in Fedora 25 and newer using XOrg (not Wayland) and I assume Ubuntu 17.04 and newer, there is this desktop freezing issue that makes it impossible to have the guest OSs in VMware. Thanks for the additional workaround may I ask though is this any different or better performing than my workaround where you disable VMware 3D hardware acceleration for the VM? Turning off hardware acceleration in GNOME makes it almost unusable. This makes the system go smoother, but it's by far not the desired solution. However you can enable it for other applications by setting the environment variable to 0 for them. OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.00 OpenGL ES profile version string: OpenGL ES 3.0 Mesa 17.0.5 OpenGL shading language version string: 1.30 OpenGL core profile profile mask: core profile OpenGL core profile context flags: (none) OpenGL core profile shading language version string: 3.30 OpenGL core profile version string: 3.3 (Core Profile) Mesa 17.0.5 OpenGL renderer string: Gallium 0.4 on SVGA3D build: RELEASE LLVM If I turn off 3D acceleration or not have the VM in full screen (4K) then it doesn't freeze, but this is very inconvenient as Gnome doesn't run well without 3D acceleration. The freezing will occur in both XOrg and Wayland desktop sessions. After a lot of troubleshooting to figure out what is causing the freezing it appears to be due to the 3D acceleration and only in full screen mode. The Gnome desktop will just randomly freeze and I cannot do anything or get control of it without doing a hard reboot of the VM. open-vm-tools and open-vm-tools-desktop (10.1.5-4.fc25) installed automatically and successfully. I created a new guest running the latest Fedora 25, with 2 GB max guest memory for graphics. In the BIOS I've set for the Intel GPU to get the max amount dedicated video memory possible (512 MB). VMware runs on the Intel HD 630 GPU (verified by Nvidia GPU activity monitor never showing VMware process). It uses hybrid graphics between integrated Intel and Nvidia GPUs using Nvidia Optimus with default settings on a 4K display. I have a new Windows laptop running latest Windows 3 and VMware Workstation 12.5.7 build-5813279.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |