Re: After Upgrade from F25 to F26 VMware Workstation is refusing anything ...

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On 07/13/2017 12:33 PM, Walter H. wrote:
> On 12.07.2017 21:27, Mark C. Allman wrote:
>> On 07/12/2017 12:14 PM, Walter H. wrote:
>>> Hello,
>>>
>>> I did this as explained here:
>>> https://fedoraproject.org/wiki/DNF_system_upgrade
>>>
>>> and after this I can't start VMware Workstation;
>>> removing and installing VMware Workstation (latest release: 12.5.7)
>>> new doesn't help ...
>>> (the same as if I hadn't removed and installed new)
>>>
>>> ifconfig   only shows this:
>>>
>>> enp63s0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>   mtu 1500
>>>          inet 192.168.1.1  netmask 255.255.255.0  broadcast
>>> 192.168.1.255
>>>          inet6 fe80::673e:4262:54d2:1816  prefixlen 64  scopeid
>>> 0x20<link>
>>>          inet6 #myprefix#::1:1  prefixlen 64  scopeid 0x0<global>
>>>          ether 24:00:00:00:00:24  txqueuelen 1000  (Ethernet)
>>>          RX packets 18656  bytes 1210711 (1.1 MiB)
>>>          RX errors 0  dropped 0  overruns 0  frame 0
>>>          TX packets 25349  bytes 35314278 (33.6 MiB)
>>>          TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
>>>          device interrupt 17
>>>
>>> lo: flags=73<UP,LOOPBACK,RUNNING>   mtu 65536
>>>          inet 127.0.0.1  netmask 255.0.0.0
>>>          inet6 ::1  prefixlen 128  scopeid 0x10<host>
>>>          loop  txqueuelen 1000  (Local Loopback)
>>>          RX packets 32  bytes 2848 (2.7 KiB)
>>>          RX errors 0  dropped 0  overruns 0  frame 0
>>>          TX packets 32  bytes 2848 (2.7 KiB)
>>>          TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
>>>
>>>
>>> and before the upgrade there were two extra virtual interfaces from
>>> VMware ...
>>> one used when VMs run with Host-only network connection, and
>>> one used when VMs run with NAT network connection ...
>>> (the same as I'm used to with Windows release)
>>>
>>> Greetings,
>>> Walter
>>>
>>>
>>>
>>>
>>> _______________________________________________
>>> users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx
>>> To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
>> First, sorry if this doesn't show up as plain text.  It should but
>> typing it in Thunderbird isn't showing it as plain text.
>>
>> Use "systemctl status vmware" to determine if the vmware services are
>> all running.  If it's my experience then I bet not.  When I run
>>      sudo vmware-modconfig --console --install-all
>>
>> I get the error message "Failed to get gcc information."  I had to do
>> this (as root):
>>        cd /usr/lib/vmware/modules/source
>>        tar xf vmmon.tar
>>        cd vmmon-only
>>        make
>>        cd ..
>>        tar xf vmnet.tar
>>        cd vmnet-only
>>        make
>>        cd ../
>>        mkdir /lib/modules/`uname -r`/misc
>>        cp vmmon.ko /lib/modules/`uname -r`/misc
>>        cp vmnet.ko /lib/modules/`uname -r`/misc
>>        depmod -a
>>        systemctl vmware restart
> so far this works and brings back the two virtual network interfaces ...
> with the only difference I had to do this:
>
> cp vmmon.o /lib/modules/`uname -r`/misc/vmmon.ko
> cp vmnet.o /lib/modules/`uname -r`/misc/vmnet.ko
>
> vmnet1: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
>         inet 192.168.151.1  netmask 255.255.255.0  broadcast
> 192.168.151.255
>         inet6 fe80::250:56ff:fec0:1  prefixlen 64  scopeid 0x20<link>
>         ether 00:50:56:c0:00:01  txqueuelen 1000  (Ethernet)
>         RX packets 0  bytes 0 (0.0 B)
>         RX errors 0  dropped 0  overruns 0  frame 0
>         TX packets 41  bytes 0 (0.0 B)
>         TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
>
> vmnet8: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
>         inet 192.168.21.1  netmask 255.255.255.0  broadcast
> 192.168.21.255
>         inet6 fe80::250:56ff:fec0:8  prefixlen 64  scopeid 0x20<link>
>         ether 00:50:56:c0:00:08  txqueuelen 1000  (Ethernet)
>         RX packets 0  bytes 0 (0.0 B)
>         RX errors 0  dropped 0  overruns 0  frame 0
>         TX packets 40  bytes 0 (0.0 B)
>         TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
>
> but
>>
>> vmware (as in VMware-Workstation) still wouldn't start.  Using strace I
>> found that libexpat.so.0 wasn't being found so I then ran:
>>      ln -s /usr/lib64/libexpat.so.1.6.2 /usr/lib64/libexpat.so.0
> this doesn't help anything, VMware Wkst. still refuses to start ...
> (even after a shutdown -r now)
>
> is there any log or similar where I can look for the reason if this?
>> vmware would then run and my Windows 10 VM appears to be working fine
>> (so far ;-).
>>
>> i googled around for the first part about the need to manually rebuild
>> vmmon and vmnet.
>>
> Thanks,
> Walter
>
>
>
> _______________________________________________
> users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx
> To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
Ugh! Yea -- forgot that the object files needed to have a ".ko"
extension.  I typed that all up from memory.

Next step is to try to figure out why vmware still won't run.  I'd
recommend editing /usr/bin/vmware (which is a shell script) to tweak the
bottom of the script from:

    if "$BINDIR"/vmware-modconfig --appname="VMware Workstation"
--icon="vmware-workstation" &&
       vmware_module_exists $vmmon; then
       exec "$libdir"/bin/"vmware" "$@"
    fi

to look something like:

    #if "$BINDIR"/vmware-modconfig --appname="VMware Workstation"
--icon="vmware-workstation" &&
    if   vmware_module_exists $vmmon; then
       exec "$libdir"/bin/"vmware" "$@"
    fi

We may need to comment out running "$BINDIR"/vmware-modconfig
--appname="VMware Workstation" --icon="vmware-workstation" because it
might be failing with a "Failed to get gcc information" error. 

If it still won't start then make a copy of the exec line inside the
"if," comment out the copy, and edit the uncommented line to something like:

       strace -o /tmp/debug.txt "$libdir"/bin/"vmware" "$@"

Open /tmp/debug.txt and go to the bottom to look for some type of error
that's happening.  I removed the soft link to /usr/lib64/libexpat.so.0
that I mentioned in the earlier post, made the changes to
/usr/bin/vmware, ran it, opened /tmp/debug.txt and I see a few lines
from the bottom several error lines where the app is trying to open
libexpat.so.0 from several different locations.  Use strace to see if at
about the end of the /tmp/debug.txt file you see some error messages.


*Mark C. Allman, PMP, CSM*
Founder, See How You Ski, www.seehowyouski.com <http://www.seehowyouski.com>
Sr. Project Manager, Allman Professional Consulting, Inc.,
www.allmanpc.com <http://www.allmanpc.com>
617-947-4263, Twitter:  @allmanpc
_______________________________________________
users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx



[Index of Archives]     [Older Fedora Users]     [Fedora Announce]     [Fedora Package Announce]     [EPEL Announce]     [EPEL Devel]     [Fedora Magazine]     [Fedora Summer Coding]     [Fedora Laptop]     [Fedora Cloud]     [Fedora Advisory Board]     [Fedora Education]     [Fedora Security]     [Fedora Scitech]     [Fedora Robotics]     [Fedora Infrastructure]     [Fedora Websites]     [Anaconda Devel]     [Fedora Devel Java]     [Fedora Desktop]     [Fedora Fonts]     [Fedora Marketing]     [Fedora Management Tools]     [Fedora Mentors]     [Fedora Package Review]     [Fedora R Devel]     [Fedora PHP Devel]     [Kickstart]     [Fedora Music]     [Fedora Packaging]     [Fedora SELinux]     [Fedora Legal]     [Fedora Kernel]     [Fedora OCaml]     [Coolkey]     [Virtualization Tools]     [ET Management Tools]     [Yum Users]     [Yosemite News]     [Gnome Users]     [KDE Users]     [Fedora Art]     [Fedora Docs]     [Fedora Sparc]     [Libvirt Users]     [Fedora ARM]

  Powered by Linux