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(a)lists.fedoraproject.org
To unsubscribe send an email to users-leave(a)lists.fedoraproject.org
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
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
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.
*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