![]() ![]() ![]() We can execute from the command line forcing to use all SHIPPED libraries from VMware Workstation. Since libcurl.so.4 was marked as SYSTEM we know that it is trying to use the library from our installed packages. T08:59:45.789-06:00| appLoader| I125: System libcurl.so.4 has version 7.53.1 (need 7.51.0) and has been compiled with c-ares support (SSL compatibility? yes). From the output this month we have the following which is suspect in our log.Ġ17-03-24T08:59:45.773-06:00| appLoader| I125: Marking libxml2.so.2 node as SHIPPED. It will show you in the beginning which libraries it will be using from either SYSTEM or SHIPPED with VMware Workstation. The first thing you can do is inspect the log craeted at /tmp/vmware-/vmware-apploader-.log. So you go ahead and launch vmware, but no VMware Workstation windows opens. So what if for example (which is what happened this month with a newer library version of curl) that we have a newer version of library than what is supported by VMware Workstation. #OPENSUSE TUMBLEWEED VMWARE WORKSTATION PLAYER 12 DRIVERS#Mostly the Kernel problems get worked around with simple patches so that the vmmon and vmnet drivers can compile correctly and I've posted a few here on my blog with a tool that can help as well. As you know Tumbleweed is constantly churning and as such there are points in time where some of the libraries required to run VMware Workstation get a new version that isn't compatible with the latest release or the version you have installed. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |