[SOLVED] unable to run VMware Player 10 on Fedora 21???

cyberdome · 04-16-2015, 09:19 AM

When I start the VMware Player on Fedora 21, I am unable to execute the VMware Player 10. It is throwing errors at me.
Here is the error message log when I run the VMware Player GUI startup.

Any help is appreciated.

Thanks

Code:

2015-04-16T07:14:16.917-08:00| vthread-3| I120: Log for VMware Workstation pid=4108 version=10.0.4 build=build-2249910 option=Release
2015-04-16T07:14:16.917-08:00| vthread-3| I120: The process is 64-bit.
2015-04-16T07:14:16.917-08:00| vthread-3| I120: Host codepage=UTF-8 encoding=UTF-8
2015-04-16T07:14:16.917-08:00| vthread-3| I120: Host is Linux 3.19.3-200.fc21.x86_64 Fedora release 21 (Twenty One)
2015-04-16T07:14:16.917-08:00| vthread-3| I120: Msg_Reset:
2015-04-16T07:14:16.917-08:00| vthread-3| I120: [msg.dictionary.load.openFailed] Cannot open file "/usr/lib/vmware/settings": No such file or directory.
2015-04-16T07:14:16.917-08:00| vthread-3| I120: ----------------------------------------
2015-04-16T07:14:16.917-08:00| vthread-3| I120: PREF Optional preferences file not found at /usr/lib/vmware/settings. Using default values.
2015-04-16T07:14:16.917-08:00| vthread-3| I120: Msg_Reset:
2015-04-16T07:14:16.917-08:00| vthread-3| I120: [msg.dictionary.load.openFailed] Cannot open file "/home/asif2k/.vmware/config": No such file or directory.
2015-04-16T07:14:16.917-08:00| vthread-3| I120: ----------------------------------------
2015-04-16T07:14:16.917-08:00| vthread-3| I120: PREF Optional preferences file not found at /home/asif2k/.vmware/config. Using default values.
2015-04-16T07:14:16.917-08:00| vthread-3| W110: Logging to /tmp/vmware-root/vmware-modconfig-4108.log
2015-04-16T07:14:16.928-08:00| vthread-3| I120: Obtaining info using the running kernel.
2015-04-16T07:14:16.928-08:00| vthread-3| I120: Created new pathsHash.
2015-04-16T07:14:16.928-08:00| vthread-3| I120: Setting header path for 3.19.3-200.fc21.x86_64 to "/lib/modules/3.19.3-200.fc21.x86_64/build/include".
2015-04-16T07:14:16.928-08:00| vthread-3| I120: Validating path "/lib/modules/3.19.3-200.fc21.x86_64/build/include" for kernel release "3.19.3-200.fc21.x86_64".
2015-04-16T07:14:16.929-08:00| vthread-3| I120: Failed to find /lib/modules/3.19.3-200.fc21.x86_64/build/include/linux/version.h
2015-04-16T07:14:16.929-08:00| vthread-3| I120: /lib/modules/3.19.3-200.fc21.x86_64/build/include/linux/version.h not found, looking for generated/uapi/linux/version.h instead.
2015-04-16T07:14:16.929-08:00| vthread-3| I120: using /usr/bin/gcc for preprocess check
2015-04-16T07:14:16.938-08:00| vthread-3| I120: Preprocessed UTS_RELEASE, got value "3.19.3-200.fc21.x86_64".
2015-04-16T07:14:16.938-08:00| vthread-3| I120: The header path "/lib/modules/3.19.3-200.fc21.x86_64/build/include" for the kernel "3.19.3-200.fc21.x86_64" is valid.  Whoohoo!
2015-04-16T07:14:17.122-08:00| vthread-3| I120: Reading in info for the vmmon module.
2015-04-16T07:14:17.122-08:00| vthread-3| I120: Reading in info for the vmnet module.
2015-04-16T07:14:17.122-08:00| vthread-3| I120: Reading in info for the vmblock module.
2015-04-16T07:14:17.122-08:00| vthread-3| I120: Reading in info for the vmci module.
2015-04-16T07:14:17.122-08:00| vthread-3| I120: Reading in info for the vsock module.
2015-04-16T07:14:17.122-08:00| vthread-3| I120: Setting vsock to depend on vmci.
2015-04-16T07:14:17.122-08:00| vthread-3| I120: Invoking modinfo on "vmmon".
2015-04-16T07:14:17.125-08:00| vthread-3| I120: "/sbin/modinfo" exited with status 0.
2015-04-16T07:14:17.125-08:00| vthread-3| I120: Invoking modinfo on "vmnet".
2015-04-16T07:14:17.128-08:00| vthread-3| I120: "/sbin/modinfo" exited with status 256.
2015-04-16T07:14:17.128-08:00| vthread-3| I120: Invoking modinfo on "vmblock".
2015-04-16T07:14:17.132-08:00| vthread-3| I120: "/sbin/modinfo" exited with status 256.
2015-04-16T07:14:17.132-08:00| vthread-3| I120: Invoking modinfo on "vmci".
2015-04-16T07:14:17.135-08:00| vthread-3| I120: "/sbin/modinfo" exited with status 256.
2015-04-16T07:14:17.135-08:00| vthread-3| I120: Invoking modinfo on "vsock".
2015-04-16T07:14:17.139-08:00| vthread-3| I120: "/sbin/modinfo" exited with status 0.
2015-04-16T07:14:17.154-08:00| vthread-3| I120: to be installed: vmnet status: 0
2015-04-16T07:14:17.154-08:00| vthread-3| I120: to be installed: vmci status: 0
2015-04-16T07:14:17.172-08:00| vthread-3| I120: Obtaining info using the running kernel.
2015-04-16T07:14:17.172-08:00| vthread-3| I120: Setting header path for 3.19.3-200.fc21.x86_64 to "/lib/modules/3.19.3-200.fc21.x86_64/build/include".
2015-04-16T07:14:17.172-08:00| vthread-3| I120: Validating path "/lib/modules/3.19.3-200.fc21.x86_64/build/include" for kernel release "3.19.3-200.fc21.x86_64".
2015-04-16T07:14:17.172-08:00| vthread-3| I120: Failed to find /lib/modules/3.19.3-200.fc21.x86_64/build/include/linux/version.h
2015-04-16T07:14:17.172-08:00| vthread-3| I120: /lib/modules/3.19.3-200.fc21.x86_64/build/include/linux/version.h not found, looking for generated/uapi/linux/version.h instead.
2015-04-16T07:14:17.172-08:00| vthread-3| I120: using /usr/bin/gcc for preprocess check
2015-04-16T07:14:17.182-08:00| vthread-3| I120: Preprocessed UTS_RELEASE, got value "3.19.3-200.fc21.x86_64".
2015-04-16T07:14:17.182-08:00| vthread-3| I120: The header path "/lib/modules/3.19.3-200.fc21.x86_64/build/include" for the kernel "3.19.3-200.fc21.x86_64" is valid.  Whoohoo!
2015-04-16T07:14:17.364-08:00| vthread-3| I120: Kernel header path retrieved from FileEntry: /lib/modules/3.19.3-200.fc21.x86_64/build/include
2015-04-16T07:14:17.364-08:00| vthread-3| I120: Update kernel header path to /lib/modules/3.19.3-200.fc21.x86_64/build/include
2015-04-16T07:14:17.364-08:00| vthread-3| I120: Validating path "/lib/modules/3.19.3-200.fc21.x86_64/build/include" for kernel release "3.19.3-200.fc21.x86_64".
2015-04-16T07:14:17.364-08:00| vthread-3| I120: Failed to find /lib/modules/3.19.3-200.fc21.x86_64/build/include/linux/version.h
2015-04-16T07:14:17.364-08:00| vthread-3| I120: /lib/modules/3.19.3-200.fc21.x86_64/build/include/linux/version.h not found, looking for generated/uapi/linux/version.h instead.
2015-04-16T07:14:17.364-08:00| vthread-3| I120: using /usr/bin/gcc for preprocess check
2015-04-16T07:14:17.374-08:00| vthread-3| I120: Preprocessed UTS_RELEASE, got value "3.19.3-200.fc21.x86_64".
2015-04-16T07:14:17.374-08:00| vthread-3| I120: The header path "/lib/modules/3.19.3-200.fc21.x86_64/build/include" for the kernel "3.19.3-200.fc21.x86_64" is valid.  Whoohoo!
2015-04-16T07:14:17.375-08:00| vthread-3| I120: Found compiler at "/usr/bin/gcc"
2015-04-16T07:14:17.380-08:00| vthread-3| I120: Got gcc version "4.9.2".
2015-04-16T07:14:17.380-08:00| vthread-3| I120: The GCC version matches the kernel GCC minor version like a glove.
2015-04-16T07:14:17.380-08:00| vthread-3| I120: Using user supplied compiler "/usr/bin/gcc".
2015-04-16T07:14:17.384-08:00| vthread-3| I120: Got gcc version "4.9.2".
2015-04-16T07:14:17.385-08:00| vthread-3| I120: The GCC version matches the kernel GCC minor version like a glove.
2015-04-16T07:14:17.390-08:00| vthread-3| I120: Trying to find a suitable PBM set for kernel "3.19.3-200.fc21.x86_64".
2015-04-16T07:14:17.390-08:00| vthread-3| I120: No matching PBM set was found for kernel "3.19.3-200.fc21.x86_64".
2015-04-16T07:14:17.390-08:00| vthread-3| I120: The GCC version matches the kernel GCC minor version like a glove.
2015-04-16T07:14:17.390-08:00| vthread-3| I120: Validating path "/lib/modules/3.19.3-200.fc21.x86_64/build/include" for kernel release "3.19.3-200.fc21.x86_64".
2015-04-16T07:14:17.390-08:00| vthread-3| I120: Failed to find /lib/modules/3.19.3-200.fc21.x86_64/build/include/linux/version.h
2015-04-16T07:14:17.390-08:00| vthread-3| I120: /lib/modules/3.19.3-200.fc21.x86_64/build/include/linux/version.h not found, looking for generated/uapi/linux/version.h instead.
2015-04-16T07:14:17.390-08:00| vthread-3| I120: using /usr/bin/gcc for preprocess check
2015-04-16T07:14:17.400-08:00| vthread-3| I120: Preprocessed UTS_RELEASE, got value "3.19.3-200.fc21.x86_64".
2015-04-16T07:14:17.400-08:00| vthread-3| I120: The header path "/lib/modules/3.19.3-200.fc21.x86_64/build/include" for the kernel "3.19.3-200.fc21.x86_64" is valid.  Whoohoo!
2015-04-16T07:14:17.401-08:00| vthread-3| I120: The GCC version matches the kernel GCC minor version like a glove.
2015-04-16T07:14:17.401-08:00| vthread-3| I120: Validating path "/lib/modules/3.19.3-200.fc21.x86_64/build/include" for kernel release "3.19.3-200.fc21.x86_64".
2015-04-16T07:14:17.401-08:00| vthread-3| I120: Failed to find /lib/modules/3.19.3-200.fc21.x86_64/build/include/linux/version.h
2015-04-16T07:14:17.401-08:00| vthread-3| I120: /lib/modules/3.19.3-200.fc21.x86_64/build/include/linux/version.h not found, looking for generated/uapi/linux/version.h instead.
2015-04-16T07:14:17.401-08:00| vthread-3| I120: using /usr/bin/gcc for preprocess check
2015-04-16T07:14:17.411-08:00| vthread-3| I120: Preprocessed UTS_RELEASE, got value "3.19.3-200.fc21.x86_64".
2015-04-16T07:14:17.411-08:00| vthread-3| I120: The header path "/lib/modules/3.19.3-200.fc21.x86_64/build/include" for the kernel "3.19.3-200.fc21.x86_64" is valid.  Whoohoo!
2015-04-16T07:14:17.411-08:00| vthread-3| I120: Using temp dir "/tmp".
2015-04-16T07:14:17.412-08:00| vthread-3| I120: Obtaining info using the running kernel.
2015-04-16T07:14:17.412-08:00| vthread-3| I120: Setting header path for 3.19.3-200.fc21.x86_64 to "/lib/modules/3.19.3-200.fc21.x86_64/build/include".
2015-04-16T07:14:17.412-08:00| vthread-3| I120: Validating path "/lib/modules/3.19.3-200.fc21.x86_64/build/include" for kernel release "3.19.3-200.fc21.x86_64".
2015-04-16T07:14:17.412-08:00| vthread-3| I120: Failed to find /lib/modules/3.19.3-200.fc21.x86_64/build/include/linux/version.h
2015-04-16T07:14:17.412-08:00| vthread-3| I120: /lib/modules/3.19.3-200.fc21.x86_64/build/include/linux/version.h not found, looking for generated/uapi/linux/version.h instead.
2015-04-16T07:14:17.412-08:00| vthread-3| I120: using /usr/bin/gcc for preprocess check
2015-04-16T07:14:17.421-08:00| vthread-3| I120: Preprocessed UTS_RELEASE, got value "3.19.3-200.fc21.x86_64".
2015-04-16T07:14:17.422-08:00| vthread-3| I120: The header path "/lib/modules/3.19.3-200.fc21.x86_64/build/include" for the kernel "3.19.3-200.fc21.x86_64" is valid.  Whoohoo!
2015-04-16T07:14:17.601-08:00| vthread-3| I120: Invoking modinfo on "vmnet".
2015-04-16T07:14:17.605-08:00| vthread-3| I120: "/sbin/modinfo" exited with status 256.
2015-04-16T07:14:17.605-08:00| vthread-3| I120: Invoking modinfo on "vmci".
2015-04-16T07:14:17.609-08:00| vthread-3| I120: "/sbin/modinfo" exited with status 256.
2015-04-16T07:14:17.661-08:00| vthread-3| I120: Setting destination path for vmnet to "/lib/modules/3.19.3-200.fc21.x86_64/misc/vmnet.ko".
2015-04-16T07:14:17.661-08:00| vthread-3| I120: Extracting the vmnet source from "/usr/lib/vmware/modules/source/vmnet.tar".
2015-04-16T07:14:17.667-08:00| vthread-3| I120: Successfully extracted the vmnet source.
2015-04-16T07:14:17.667-08:00| vthread-3| I120: Building module with command "/usr/bin/make -j8 -C /tmp/modconfig-g1ZENn/vmnet-only auto-build HEADER_DIR=/lib/modules/3.19.3-200.fc21.x86_64/build/include CC=/usr/bin/gcc IS_GCC_3=no"
2015-04-16T07:14:19.833-08:00| vthread-3| W110: Failed to build vmnet.  Failed to execute the build command.
2015-04-16T07:14:19.836-08:00| vthread-3| I120: Setting destination path for vmci to "/lib/modules/3.19.3-200.fc21.x86_64/misc/vmci.ko".
2015-04-16T07:14:19.836-08:00| vthread-3| I120: Extracting the vmci source from "/usr/lib/vmware/modules/source/vmci.tar".
2015-04-16T07:14:19.844-08:00| vthread-3| I120: Successfully extracted the vmci source.
2015-04-16T07:14:19.844-08:00| vthread-3| I120: Building module with command "/usr/bin/make -j8 -C /tmp/modconfig-g1ZENn/vmci-only auto-build HEADER_DIR=/lib/modules/3.19.3-200.fc21.x86_64/build/include CC=/usr/bin/gcc IS_GCC_3=no"
2015-04-16T07:14:21.915-08:00| vthread-3| W110: Failed to build vmci.  Failed to execute the build command.

Thanks

T3RM1NVT0R · 04-16-2015, 09:30 AM

Do you have kernel-headers installed on the system. I had similar issue long ago and at that time it turned out to be the issue that kernel-headers weren't installed.

cyberdome · 04-16-2015, 09:57 AM

Quote:

Originally Posted by T3RM1NVT0R

Do you have kernel-headers installed on the system. I had similar issue long ago and at that time it turned out to be the issue that kernel-headers weren't installed.

How do I check for that?

T3RM1NVT0R · 04-16-2015, 10:00 AM

Here is how you can check:

Code:

rpm -qa | grep -i kernel

I would also suggest to check gcc installed on this system. You can check that by:

Code:

rpm -qa | grep -i gcc

John VV · 04-16-2015, 01:01 PM

VMware Player 10
??????

would that be version 7.1.0 ???? ( that 1.0 as 10 )

on fedora 21 gcc should be 4.9.2-6

BUT

not many things YET build with gcc 4.9 without hacking the code

-- that is life with fedora
LIVE WITH IT or use a different OS

fedora always uses the newest of the NEWEST version of GCC

this often causes slightly older code ( 6 months old ) to not build without updating the software to build on the NEW gcc

this is not new with fedora nor is is a bug
it is a feature!!!!

piping rpm to grep will inform you as to what is INSTALLED only

using yum will also inform you as to what CAN be installed

Code:

su -
yum search kernel
----------- and -------------
yum search gcc

there will be a nice "i" in front of the installed software

cyberdome · 04-16-2015, 10:57 PM

Code:

rpm -qa | grep -i kernel

For this command, this is what I got.

rpm -qa | grep -i kernel
kernel-3.17.7-200.fc20.x86_64
kernel-headers-3.19.3-200.fc21.x86_64
kernel-3.19.3-200.fc21.x86_64
kernel-modules-extra-3.19.3-100.fc20.x86_64
kernel-modules-3.19.3-200.fc21.x86_64
kernel-modules-extra-3.17.7-200.fc20.x86_64
libreport-plugin-kerneloops-2.3.0-6.fc21.x86_64
kernel-devel-3.17.7-200.fc20.x86_64
kernel-modules-extra-3.19.3-200.fc21.x86_64
kernel-devel-3.19.3-200.fc21.x86_64
abrt-addon-kerneloops-2.3.0-4.fc21.x86_64
kernel-3.19.3-100.fc20.x86_64
kernel-core-3.19.3-200.fc21.x86_64
kernel-devel-3.19.3-100.fc20.x86_64

Code:

rpm -qa | grep -i gcc

For this command, I got this result.

gcc-4.9.2-6.fc21.x86_64
libgcc-4.9.2-6.fc21.x86_64
gcc-c++-4.9.2-6.fc21.x86_64

cyberdome · 04-16-2015, 11:01 PM

Quote:

Originally Posted by John VV

VMware Player 10
??????

would that be version 7.1.0 ???? ( that 1.0 as 10 )

on fedora 21 gcc should be 4.9.2-6

BUT

not many things YET build with gcc 4.9 without hacking the code

-- that is life with fedora
LIVE WITH IT or use a different OS

fedora always uses the newest of the NEWEST version of GCC

this often causes slightly older code ( 6 months old ) to not build without updating the software to build on the NEW gcc

this is not new with fedora nor is is a bug
it is a feature!!!!

piping rpm to grep will inform you as to what is INSTALLED only

using yum will also inform you as to what CAN be installed

Code:

su -
yum search kernel
----------- and -------------
yum search gcc

there will be a nice "i" in front of the installed software

It is actually VMware Player 6 version. Sorry for the confusion. I ran both commands, posted the results. Any advice on how to overcome this issue.

I followed this tutorial, did not get much success.
https://wiki.archlinux.org/index.php...e#3.17_kernels

Code:

3.19 kernels
Since 3.19 kernel the vmnet module will fail to build.
A patch is available at [1]:
$ curl http://pastie.org/pastes/9934018/download -o /tmp/vmnet-3.19.patch
Extract the vmnet module sources:
$ cd /usr/lib/vmware/modules/source
# tar -xf vmnet.tar
Apply the patch:
# patch -p0 -i /tmp/vmnet-3.19.patch
Recreate the archive:
# tar -cf vmnet.tar vmnet-only
Remove leftover:
# rm -r *-only
Rebuild modules:
# vmware-modconfig --console --install-all

source:
https://wiki.archlinux.org/index.php...e#3.17_kernels

cyberdome · 04-16-2015, 11:40 PM

When I run vmplayer on the shell prompt, this is what I get.

Code:

#vmplayer
Logging to /tmp/vmware-root/vmware-modconfig-4353.log
Stopping vmware (via systemctl):                           [  OK  ]
make: Entering directory '/tmp/modconfig-mhBvOn/vmnet-only'
Using 2.6.x kernel build system.
/usr/bin/make -C /lib/modules/3.19.3-200.fc21.x86_64/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. \
  MODULEBUILDDIR= modules
make[1]: Entering directory '/usr/src/kernels/3.19.3-200.fc21.x86_64'
  CC [M]  /tmp/modconfig-mhBvOn/vmnet-only/driver.o
  CC [M]  /tmp/modconfig-mhBvOn/vmnet-only/hub.o
  CC [M]  /tmp/modconfig-mhBvOn/vmnet-only/userif.o
  CC [M]  /tmp/modconfig-mhBvOn/vmnet-only/netif.o
  CC [M]  /tmp/modconfig-mhBvOn/vmnet-only/bridge.o
  CC [M]  /tmp/modconfig-mhBvOn/vmnet-only/procfs.o
  CC [M]  /tmp/modconfig-mhBvOn/vmnet-only/smac_compat.o
  CC [M]  /tmp/modconfig-mhBvOn/vmnet-only/smac.o
In file included from include/linux/pci.h:34:0,
                 from /tmp/modconfig-mhBvOn/vmnet-only/compat_netdevice.h:27,
                 from /tmp/modconfig-mhBvOn/vmnet-only/netif.c:43:
include/linux/pci_ids.h:2251:0: warning: "PCI_VENDOR_ID_VMWARE" redefined
 #define PCI_VENDOR_ID_VMWARE  0x15ad
 ^
In file included from /tmp/modconfig-mhBvOn/vmnet-only/net.h:38:0,
                 from /tmp/modconfig-mhBvOn/vmnet-only/vnetInt.h:26,
                 from /tmp/modconfig-mhBvOn/vmnet-only/netif.c:42:
/tmp/modconfig-mhBvOn/vmnet-only/vm_device_version.h:56:0: note: this is the location of the previous definition
 #define PCI_VENDOR_ID_VMWARE                    0x15AD
 ^
  CC [M]  /tmp/modconfig-mhBvOn/vmnet-only/vnetEvent.o
/tmp/modconfig-mhBvOn/vmnet-only/netif.c: In function ‘VNetNetIf_Create’:
/tmp/modconfig-mhBvOn/vmnet-only/netif.c:152:64: error: macro "alloc_netdev" requires 4 arguments, but only 3 given
    dev = alloc_netdev(sizeof *netIf, deviceName, VNetNetIfSetup);
                                                                ^
/tmp/modconfig-mhBvOn/vmnet-only/netif.c:152:10: error: ‘alloc_netdev’ undeclared (first use in this function)
    dev = alloc_netdev(sizeof *netIf, deviceName, VNetNetIfSetup);
          ^
/tmp/modconfig-mhBvOn/vmnet-only/netif.c:152:10: note: each undeclared identifier is reported only once for each function it appears in
/tmp/modconfig-mhBvOn/vmnet-only/netif.c: At top level:
/tmp/modconfig-mhBvOn/vmnet-only/netif.c:85:1: warning: ‘VNetNetIfSetup’ defined but not used [-Wunused-function]
 VNetNetIfSetup(struct net_device *dev)  // IN:
 ^
scripts/Makefile.build:257: recipe for target '/tmp/modconfig-mhBvOn/vmnet-only/netif.o' failed
make[2]: *** [/tmp/modconfig-mhBvOn/vmnet-only/netif.o] Error 1
make[2]: *** Waiting for unfinished jobs....
In file included from /tmp/modconfig-mhBvOn/vmnet-only/net.h:38:0,
                 from /tmp/modconfig-mhBvOn/vmnet-only/vnetInt.h:26,
                 from /tmp/modconfig-mhBvOn/vmnet-only/bridge.c:52:
/tmp/modconfig-mhBvOn/vmnet-only/vm_device_version.h:56:0: warning: "PCI_VENDOR_ID_VMWARE" redefined
 #define PCI_VENDOR_ID_VMWARE                    0x15AD
 ^
In file included from include/linux/pci.h:34:0,
                 from /tmp/modconfig-mhBvOn/vmnet-only/compat_netdevice.h:27,
                 from /tmp/modconfig-mhBvOn/vmnet-only/bridge.c:51:
include/linux/pci_ids.h:2251:0: note: this is the location of the previous definition
 #define PCI_VENDOR_ID_VMWARE  0x15ad
 ^
Makefile:1386: recipe for target '_module_/tmp/modconfig-mhBvOn/vmnet-only' failed
make[1]: *** [_module_/tmp/modconfig-mhBvOn/vmnet-only] Error 2
make[1]: Leaving directory '/usr/src/kernels/3.19.3-200.fc21.x86_64'
Makefile:130: recipe for target 'vmnet.ko' failed
make: *** [vmnet.ko] Error 2
make: Leaving directory '/tmp/modconfig-mhBvOn/vmnet-only'
Failed to build vmnet.  Failed to execute the build command.
make: Entering directory '/tmp/modconfig-mhBvOn/vmci-only'
Using 2.6.x kernel build system.
/usr/bin/make -C /lib/modules/3.19.3-200.fc21.x86_64/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. \
  MODULEBUILDDIR= modules
make[1]: Entering directory '/usr/src/kernels/3.19.3-200.fc21.x86_64'
  CC [M]  /tmp/modconfig-mhBvOn/vmci-only/linux/driver.o
  CC [M]  /tmp/modconfig-mhBvOn/vmci-only/linux/vmciKernelIf.o
  CC [M]  /tmp/modconfig-mhBvOn/vmci-only/common/vmciDatagram.o
  CC [M]  /tmp/modconfig-mhBvOn/vmci-only/common/vmciDriver.o
  CC [M]  /tmp/modconfig-mhBvOn/vmci-only/common/vmciResource.o
  CC [M]  /tmp/modconfig-mhBvOn/vmci-only/common/vmciContext.o
  CC [M]  /tmp/modconfig-mhBvOn/vmci-only/common/vmciRoute.o
  CC [M]  /tmp/modconfig-mhBvOn/vmci-only/common/vmciHashtable.o
  CC [M]  /tmp/modconfig-mhBvOn/vmci-only/common/vmciQueuePair.o
  CC [M]  /tmp/modconfig-mhBvOn/vmci-only/common/vmciEvent.o
In file included from /tmp/modconfig-mhBvOn/vmci-only/linux/driver.c:60:0:
/tmp/modconfig-mhBvOn/vmci-only/./shared/vm_device_version.h:56:0: warning: "PCI_VENDOR_ID_VMWARE" redefined
 #define PCI_VENDOR_ID_VMWARE                    0x15AD
 ^
In file included from include/linux/pci.h:34:0,
                 from /tmp/modconfig-mhBvOn/vmci-only/./shared/compat_pci.h:27,
                 from /tmp/modconfig-mhBvOn/vmci-only/linux/driver.c:49:
include/linux/pci_ids.h:2251:0: note: this is the location of the previous definition
 #define PCI_VENDOR_ID_VMWARE  0x15ad
 ^
  CC [M]  /tmp/modconfig-mhBvOn/vmci-only/common/vmciQPair.o
/tmp/modconfig-mhBvOn/vmci-only/linux/vmciKernelIf.c: In function ‘__VMCIMemcpyFromQueue’:
/tmp/modconfig-mhBvOn/vmci-only/linux/vmciKernelIf.c:1309:10: error: implicit declaration of function ‘memcpy_toiovec’ [-Werror=implicit-function-declaration]
          err = memcpy_toiovec(iov, (uint8 *)va + pageOffset, toCopy);
          ^
  CC [M]  /tmp/modconfig-mhBvOn/vmci-only/common/vmciDoorbell.o
  CC [M]  /tmp/modconfig-mhBvOn/vmci-only/driverLog.o
cc1: some warnings being treated as errors
scripts/Makefile.build:257: recipe for target '/tmp/modconfig-mhBvOn/vmci-only/linux/vmciKernelIf.o' failed
make[2]: *** [/tmp/modconfig-mhBvOn/vmci-only/linux/vmciKernelIf.o] Error 1
make[2]: *** Waiting for unfinished jobs....
Makefile:1386: recipe for target '_module_/tmp/modconfig-mhBvOn/vmci-only' failed
make[1]: *** [_module_/tmp/modconfig-mhBvOn/vmci-only] Error 2
make[1]: Leaving directory '/usr/src/kernels/3.19.3-200.fc21.x86_64'
Makefile:130: recipe for target 'vmci.ko' failed
make: *** [vmci.ko] Error 2
make: Leaving directory '/tmp/modconfig-mhBvOn/vmci-only'
Failed to build vmci.  Failed to execute the build command.
Starting vmware (via systemctl):  Job for vmware.service failed. See "systemctl status vmware.service" and "journalctl -xe" for details.
                                                           [FAILED]

T3RM1NVT0R · 04-17-2015, 03:58 AM

Quite old thread of mine, go through it and see if that helps: http://www.linuxquestions.org/questi...centos-895366/

Looking at this only I requested for gcc output along with kernel-headers ;-)

John VV · 04-17-2015, 03:24 PM

the OLD vmware 6
fedora 21 is WAY TOO NEW to run on it ( way too new of a kernel)

install vmware 7.1.0
even then 21 or the soon to be release 22 might be a bit new

cyberdome · 04-18-2015, 07:21 AM

Alrighty then, This issue is finally resolved, after many months for troubleshooting. And I am a newbie at this. So, I am glad I got this fixed. For those in need of help. For future Linux newbies. This is what I did.

Step 1, Install the latest VMPlayer 7 from the VMware website. here is the link.

http://www.vmware.com/products/player

Step 2, whatever directory u install the VMPlayer 7, U go into the following directory. U run the command "chmod +x VMPlayer7.bin" (whatever name of bin file)

Step 3, then, run command from same directory "./VMPlayer.bin"

Step 4, run throught the GUI installer, simple walkthrough process.

Step 5, after installing u will get errors, then u must run a vmware patch using the tutorial from this website,
https://wiki.archlinux.org/index.php...e#3.17_kernels

Step 6, run through these commands on the shell prompt,

Since 3.19 kernel the vmnet module will fail to build.

Step 7, A patch is available at:
$ curl http://pastie.org/pastes/9934018/download -o /tmp/vmnet-3.19.patch

Step 8, Extract the vmnet module sources:
$ cd /usr/lib/vmware/modules/source
# tar -xf vmnet.tar

Step 9, Apply the patch:
# patch -p0 -i /tmp/vmnet-3.19.patch

Step 10, Recreate the archive:
# tar -cf vmnet.tar vmnet-only

Step 11, Rebuild modules:
# vmware-modconfig --console --install-all

Step 12, Start the VMware. (Before starting VMware, make sure u reboot the computer) WOOHOO!!!! You're all done!!!

jefro · 04-18-2015, 02:53 PM

Thanks for the update and solution.

cyberdome · 02-19-2016, 09:45 PM

Just FYI, VMWare Player 12 will NOT work with Fedora 23. So, here is a guru who figured out a workaround. For those who come to find this post.

https://communities.vmware.com/thread/523835

cyberdome · 02-19-2016, 10:31 PM

http://vcojot.blogspot.ca/2015/11/vm...a-core-23.html