I will update this topic if/as I find new data points or a solution. I tried making a copy of the VMs and upgrading the VMware Tools and HW version in Workstation (then powering down and removing from inventory) but they *still * will not open in Player.Īs a workaround I am running the VMs in VMware Workstation but a lack of forward compatibility in VMware Player is a concern. I got the normal errors but installed lzma and liblz1 due to the traced errors but nothing works. This hardware is used by some guest operating systems to mitigate CVE-2018-5715 (also called by the name 'Spectre').
So I turned to strace -eopen vmplayer to try and figure out what I am missing. VMware Workstation 12 Player Version 12.0.1 VMware Workstation 12 Player Security This update of VMware Workstation Player exposes hardware support for branch target injection mitigation to VMware guests. I get no obvious error unless I run from the command line, and when I do run from the command line I get a rather ambiguous "Fail to open executable: No such file or directory" error message. This seems to be irrespective of the client OS as I have a Windows 7 and Ubuntu VM that now will not open in VMPlayer. Virtual machines open fine in Workstation, but those that I was previously running without issue in VMware Player (VM HW version 12.x) now will not open in VMware Player 14. To view release notes for prior releases of VMware Workstation 12 Player, click the following links: VMware Workstation 12 Player Version. Features and Known Issues from prior releases of VMware Workstation Player are described in the release notes for each release. I am running on a fully updated host running Ubuntu 16.04.03 LTS on a beefy Dell Precision 7710. It is a free upgrade for all VMware Workstation 12 Player users.
I recently upgraded to VMware Workstation Pro 14 from the latest version of 12.5.
0 kommentar(er)
