VMware Communities
VMWARETOOLS2011
Contributor
Contributor

Vmware Workstation 12 pro not works with Fedora 23.

Please provide a patch of VMware workstation 12 pro for Fedora 23.

16 Replies
ElCoyote_
Enthusiast
Enthusiast

Here's a workaround I posted yesterday:

1) Become root:

$ sudo su -

2) replace the vmware glib version with the fedora version:

# cd /usr/lib/vmware

# for mylib in $(ls /usr/lib64/*4600*); do /bin/cp -afv $mylib $(basename $mylib .4600.1 )/$(basename $mylib .4600.1 ); done

This basically does this:

# pwd

/usr/lib/vmware/lib

# for mylib in $(ls /usr/lib64/*4600*); do echo /bin/cp -afv $mylib $(basename $mylib .4600.1 )/$(basename $mylib .4600.1 ); done

/bin/cp -afv /usr/lib64/libgio-2.0.so.0.4600.1 libgio-2.0.so.0/libgio-2.0.so.0

/bin/cp -afv /usr/lib64/libglib-2.0.so.0.4600.1 libglib-2.0.so.0/libglib-2.0.so.0

/bin/cp -afv /usr/lib64/libgmodule-2.0.so.0.4600.1 libgmodule-2.0.so.0/libgmodule-2.0.so.0

/bin/cp -afv /usr/lib64/libgobject-2.0.so.0.4600.1 libgobject-2.0.so.0/libgobject-2.0.so.0

/bin/cp -afv /usr/lib64/libgthread-2.0.so.0.4600.1 libgthread-2.0.so.0/libgthread-2.0.so.0

3) start VMware or VMplayer:

$ VMWARE_USE_SHIPPED_LIBS=force vmware

or:

$ VMWARE_USE_SHIPPED_LIBS=force vmplayer

fl57
Contributor
Contributor

A bug has been reported on bugzilla : https://bugzilla.redhat.com/show_bug.cgi?id=1278896

Reply
0 Kudos
ElCoyote_
Enthusiast
Enthusiast

Make that /usr/lib/vmware/lib

(instead of /usr/lib/vmware).

In my haste, I forgot the last part of the subdir.

Sorry about the inconvenience.

Vincent

Reply
0 Kudos
beckola
Contributor
Contributor

Will this procedure work with kernel version 4.2.5?

Reply
0 Kudos
jaujavi
Contributor
Contributor

That's work for me on Fedora 23, Linux 4.2.5

VMWare v12 looks great :smileygrin:

Thanks you very much ElCoyote_‌ !!

Reply
0 Kudos
beckola
Contributor
Contributor

I was not able to get this working using the original script, but can with a minor variation.  I don't know why this worked and the first did not, they should be functionally equivalent.

Here is my little script:

#!/bin/bash

cp -aiv /usr/lib64/libgio-2.0.so.0.4600.1 /usr/lib/vmware/lib/libgio-2.0.so.0/libgio-2.0.so.0

cp -aiv /usr/lib64/libglib-2.0.so.0.4600.1 /usr/lib/vmware/lib/libglib-2.0.so.0/libglib-2.0.so.0

cp -aiv /usr/lib64/libgmodule-2.0.so.0.4600.1 /usr/lib/vmware/lib/libgmodule-2.0.so.0/libgmodule-2.0.so.0

cp -aiv /usr/lib64/libgobject-2.0.so.0.4600.1 /usr/lib/vmware/lib/libgobject-2.0.so.0/libgobject-2.0.so.0

cp -aiv /usr/lib64/libgthread-2.0.so.0.4600.1 /usr/lib/vmware/lib/libgthread-2.0.so.0/libgthread-2.0.so.0

Reply
0 Kudos
nice10150
Contributor
Contributor

It's amazing how slow VMware comes up with a patch to fix the problem of Workstation 12 Pro not working on Fedora 23.

If I compare VMware Workstation with Oracle VirtualBox... we can see that VMware Workstation starts to become expensive software which doesn't always work.

In previous VMware Workstation version USB was always a bit incompatible, while it worked fine with Oracle VirtualBox...

Recompiling kernel modules, especially if the kernel is a bit new... needs patching from "unsecure" sources to make it work, never had that problem with Oracle Virtualbox.

Reply
0 Kudos
rmoskal
Contributor
Contributor

The fix works as far as getting me up and running, but as far as I can tell none of my windoze vms have access to dns.  Not can I run the network editor.

Reply
0 Kudos
nice10150
Contributor
Contributor

Today we installed VMware Workstation 12.1.0 (the latest update) and we were hoping that it would fix the problems with Fedora 23. But nothing like that now VMware Workstation is completely useless as it not even start with the previous work-around....

Reply
0 Kudos
nice10150
Contributor
Contributor

We will start to look into how we can get our money back...  Compare the productivity hours of VMware Workstation with Oracle VirtualBox and you can easily figure it out... So how we can get our money back on 50 licenses? The problems that should resolve community problems only made things more problematic.. with the previous version 12.0.1 we where able to use a work-around, with the latest version 12.1.0 the whole application refuse to launch...

People try to make money while using your Virtual Machines, that is why we pay for it, SO WHY THE FREE SOFTWARE FROM ORACLE works better?? ask yourself that question and think very deep how long you want to stay in business..... You loose us as customer, as we cannot deal with this bullshit of not working... over and over again...

1ee
Contributor
Contributor

The workaround above worked for me after replacing 4600.1 with 4600.2


FYI Per Bug 1278896 – VMware Workstation 12 not starting On Fedora 23 It has been suggested VMware send a patch.

bluerfoot
Contributor
Contributor

ok linux/virtualization newbie here. I purchased a kick ass laptop (32gb ram) to really learn gns3/vmware workstation/vsphere.  I put fedora on it and really just want something to work without workarounds and fixes. Has anyone using vmware player heard if there are any plans to get a compatible version out there with fedora? I don't have much on the laptop and could go the ubuntu route but a buddy said to learn on fedora as it is closer to (red hat?) what one would typically see in production environments.

Thanks if I don't get any good news I guess I will just get started using ubuntu......

Reply
0 Kudos
charris5
Contributor
Contributor

The following commands / script should work to update the libs, regardless if they are suffixed with a 1 or 2, etc, etc.

1) Become root

$ sudo su -

2) replace the vmware glib version with fedora's current version

# cd /usr/lib/vmware/lib ; for mylib in $(/bin/ls /usr/lib64/*4600*); do /bin/cp -afv $mylib $(basename $mylib .4600.${mylib##*.})/$(basename $mylib .4600.${mylib##*.}) ; done

3) start VMware or VMplayer:

$ VMWARE_USE_SHIPPED_LIBS=force vmware

or:

$ VMWARE_USE_SHIPPED_LIBS=force vmplayer

Reply
0 Kudos
markus_roth
Contributor
Contributor

If someone wants to install VMware Workstation 12 Pro on fedora 24, then the command / script looks as follows:

1) Become root

$ su -

2) replace the vmware glib version with fedora's current version

# cd /usr/lib/vmware/lib ; for mylib in $(/bin/ls /usr/lib64/*4800*); do /bin/cp -afv $mylib $(basename $mylib .4800.${mylib##*.})/$(basename $mylib .4800.${mylib##*.}) ; done

3) start VMware or VMplayer in the normal way.

Reply
0 Kudos
danlewisvm
Contributor
Contributor

I tried the suggestion above on FC24 and Workstation Player 12, however it does not solve the issue.  Is there a variant for FC24 and Workstation Player 12.5.1 build-4542065?

Thanks.

Reply
0 Kudos
hazemhemaid
Contributor
Contributor

@

Please check this link for fix this permanently.

Please let me know if it helps.

https://github.com/hhemied/vmwfix

Reply
0 Kudos