Vmware workstation 14 freezes free -

Looking for:

- Vmware workstation 14 freezes free 

Click here to DOWNLOAD

     

- Vmware workstation 14 freezes free

 

I hope the open-vm-tools team can figure out why, in Fedora 25 and newer using XOrg not Wayland and I assume Ubuntu Thanks for reporting. I believe this is an issue with Workstation I may be wrong , and filed an internal bug. I can also confirm that on the latest VMware Workstation 14 Pro I created a brand new Fedora 26 guest OS using my exact same procedure mentioned above and after using the GNOME desktop for a few minutes in 4k resolution everything freezes.

I tried to reproduce with an older hybrid graphics laptop but never saw the problem. Not running 4K, though. Could anyone seeing this problem try one of the following suggestions to help pinpoint the problem:.

And give them the logs. No, the vmtoolsd error is unrelated. While it's bad, it shouldn't cause a freeze. It would also be helpful if you could find and post the vmware.

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:. I have the same issue. My host is a Windows 10 desktop ver My guest system is a fully updated Manjaro. I've been running without 3D acceleration for over a year. I'm happy to provide any of my configuration files or logs if they'd be of any help.

Same problem here. Also, turning off 3D acceleration causes multi-monitor mode to display black screens. By default 3D acceleration should always be on. 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.

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. Turning off 3D acceleration is not a workaround the desktop is really unusable if you do that. 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 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.

I haven't yet seen anyone say this exact issue happens on HD? I am using 2 4k monitors. I was just pointing out that when I disable 3D acceleration which avoids the freeze , I cannot use my dual monitors.

I should have made that clear. I think the issue happened to me when only using one monitor, but it's been so long since I've had 3D acceleration enabled that I'd need to test it again to be completely sure. GNOME simply "blacks out". I can use one of the monitors, but not both. With 3D acceleration enabled I can use both 4k monitors but then I have to deal with periodic freezing.

Thanks for the follow up and clarification abecher22 and mumblyOMOD. More info and data points for the VMware Workstation team to show this is a real problem. I'm going to hazard a guess and say that this issue has something to do with a flaw in VMware Workstation and its 3D acceleration using late version Linux guest OSes on single 4K and dual HD monitors.

Could it be some flaw there isn't enough memory somewhere? My guess is that a single 4K or dual HD displays will require much more memory for 3D acceleration, etc. We are all setting our video memory to the max 2 GB in the settings. Hi all. 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.

If you have the possibilty to run any of these tests, it would be helpful. If someone has a VM that frequently locks up and can try the exact same VM using a Linux Player or Workstation setup to determine whether there is a lockup also on linux hosts, that would be of great help. And another simple test that would also be useful if you're running on a Nvidia system Optimus disabled if multi-GPUs : 3. Exactly the same as 0. After it exhibits the Locking behavior I'll tweak my vmx file according to 0 and will provide an update once I've tested it for a good 8 hours or so enough time that I know my machine should have exhibited the Locking behavior at least once.

I can confirm the kernel part. I'm running: Linux archlinux 4. But it may be hard to say if it is exactly the same problem. Last summer when I opened this issue and worked with open-vm-tools team to troubleshoot it I had multiple parallel testing VMs of Fedora 24, 25, 26, and then 27 in Xorg and Wayland configurations. I was testing things extensively. The problem did not exist in Fedora 24 and only appeared starting in I would keep all test instances up-to-date and retest the issue.

Only when Fedora 26 and 27 updated to kernel 4. The issue not comeback either and I'm currently running latest Fedora I'm certain if you install a fresh Fedora 28 VM on your host and bring it up-to-date this will help troubleshoot the source of your problem.

It takes no more than 30 min to install. If the desktop locks up then that strongly suggests the issue is something specific to your hardware, VMware Workstation version if you aren't using the latest Yes, it could be there is some specific open-vm-tools or VWware Workstation issue with your hardware causing the lockup, but statistically that is a less likely explanation and you won't find out until you do the above test.

You would log in to GNOME desktop and after sometimes 30 sec, sometimes 2 min, sometimes 10 min, but always without fail within a few minutes and without any particular sequence of events preceding it the entire desktop would permanently lockup and freeze.

The only way out would be to reboot either via terminal or VMware signalled reboot. Getting the same problem here, in fact exactly the same as RyanEwen above Seeing the same issue with Ubuntu 18,04 Budgie on This seems to kill the VM and then I can't power it down or do anything with it.

We have no repro on this in-house. To be able to make progress we need logs, so could anybody suffering from this please provide a A screen shot of the artifacts, b A "dmesg" log from the guest c A vmware. I've tried upgrading to 4. I also believe the problem RyanEwen and you are getting is a different issue than described in this issue.

Please see my detailed description of the issue I and others were getting last summer comment is quite a bit different than the issue RyanEwen and you are getting. IMO I think a separate issue should be opened for this. Same here. VMWare Workstation Issue is still not fixed; on Windows 10 Pro host with Ubuntu To all the people who still have this problem. For me the issue suddenly disappeared in November and it was after a Linux kernel update or something in Fedora that got updated.

I haven't had the issue since. It had nothing to do with VMware Workstation or open-vm-tools as nothing changed on the VMware or tools side between having the issue and not having the issue. I would ask people who are on Windows 10 and latest patched VMware Workstation Pro 14 or 15 to make a test and install Fedora 30 guest and see if you still get the freezing. It seems that people who are still having the issue are either using other guest Linuxes and older versions of them or older versions of host.

It's an easy test to do to start ruling out what is causing the problem. I use latest VMware Workstation See also Improving performance.

This article or section is a candidate for merging with Improving performance. To disable them for the current session, run on the host :. If you are certain you have enough spare memory, you can ensure the guest OS writes its memory directly to the host's RAM by adding the following to the VM's. If these settings are not in the virtual machine's configuration, the paravirtual SCSI adapter can still be enabled.

Ensure that the paravirtual SCSI adapter is included in the kernel image by modifying the mkinitcpio. Regenerate the initramfs. Shut down the virtual machine and change the SCSI adapter: set the. VMware offers multiple network adapters for the guest OS. This Intel adapter is generally compatible with the built-in drivers across most operating systems, including Arch.

For more performance and additional features such as multiqueue support , the VMware native vmxnet3 network adapter can be used. Arch has the vmxnet3 kernel module available with a default install. Once enabled in mkinitcpio or if it is auto-detected; check by running lsmod grep vmxnet3 to see if it is loaded , shut down and change the network adapter type in the.

After changing network adapters, the network and dhcpcd settings will need to be updated to use the new adapter name and MAC address. Vmware's KB provides the following optimizations:. Install the headers linux-headers. If not using the systemd service to automatically handle the services, you need to manually start the vmware-usbarbitrator binary as root each time.

VMware Workstation provides the possibility to remotely manage Shared VMs through the vmware-workstation-server service. To fix sound quality issues or enabling proper HD audio output, first run:. If interested in playing 5. Finally put the name in the. OSS emulation should also be disabled. This means that at least the vmmon module is not loaded. See the systemd services section for automatic loading. If you just get back to the prompt when opening the.

This can be fixed by either installing the ncurses5-compat-libs AUR dependency or temporarily allowing root access to X:. Version 14 has stricter CPU requirements than version If you try to start a virtual machine with an affected CPU, the following message will appear:. The solution is to uninstall version 14 and install version 12 vmware-workstation12 AUR.

Please try a cold boot shutting the system down and starting it again. On systems with librsvg version A workaround is to downgrade librsvg to earlier version, or more preferably, force VMware to use its own shipped version of librsvg :. As per [1] the temporary workaround is to downgrade the package libpng to version 1.

If the system have installed gcc-libs , that library is already installed. Therefore, it is possible to remove that file and vmplayer will use the one provided by gcc-libs instead.

As root do:. Registered bug at Mageia , but it seems that there are no error messages shown in terminal with arch. Solution is the same, as root do:. An example is the libfontconfig.

Check vmware logs in the tmp directory to see which libraries are still not found. Copy them to the appropriate path with libraries existing on the system:. Instead of copying all these files manually, you may want to try exporting an additional setting:. On systems with fontconfig version 2.