VMware Communities
jdelsolar
Contributor
Contributor

kernel 4.9.12-200.fc25.x86_64 FEDORA25 don't work...it is really sad

HI there:

I have already upgrade my OS to kernel 4.9.12-200.fc25.x86_64 and this software is not working, i think the vmware team is not taking serious job....each upgrade of kernel we (users) have a lot of troubles it is not fare, seariuosly changing the virtualization software would be a nice solution, but i will think diferent this time ccause it is necesary, here is the prlblem:

# VMWARE_USE_SHIPPED_LIBS=force vmware-modconfig --console --install-all

Stopping vmware (via systemctl):                           [  OK  ]

make: Entering directory '/tmp/modconfig-Zo1IFu/vmmon-only'

Using kernel build system.

/bin/make -C /lib/modules/4.9.12-200.fc25.x86_64/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. \

  MODULEBUILDDIR= modules

make[1]: Entering directory '/usr/src/kernels/4.9.12-200.fc25.x86_64'

  CC [M]  /tmp/modconfig-Zo1IFu/vmmon-only/linux/driverLog.o

  CC [M]  /tmp/modconfig-Zo1IFu/vmmon-only/linux/driver.o

  CC [M]  /tmp/modconfig-Zo1IFu/vmmon-only/linux/hostif.o

  CC [M]  /tmp/modconfig-Zo1IFu/vmmon-only/common/memtrack.o

  CC [M]  /tmp/modconfig-Zo1IFu/vmmon-only/common/apic.o

  CC [M]  /tmp/modconfig-Zo1IFu/vmmon-only/common/hashFunc.o

  CC [M]  /tmp/modconfig-Zo1IFu/vmmon-only/common/vmx86.o

  CC [M]  /tmp/modconfig-Zo1IFu/vmmon-only/common/cpuid.o

/tmp/modconfig-Zo1IFu/vmmon-only/linux/driver.c:1283:1: warning: always_inline function might not be inlinable [-Wattributes]

LinuxDriverSyncReadTSCs(uint64 *delta) // OUT: TSC max - TSC min

^~~~~~~~~~~~~~~~~~~~~~~

  CC [M]  /tmp/modconfig-Zo1IFu/vmmon-only/common/task.o

  CC [M]  /tmp/modconfig-Zo1IFu/vmmon-only/common/comport.o

  CC [M]  /tmp/modconfig-Zo1IFu/vmmon-only/common/phystrack.o

  CC [M]  /tmp/modconfig-Zo1IFu/vmmon-only/vmcore/moduleloop.o

/tmp/modconfig-Zo1IFu/vmmon-only/common/task.o: warning: objtool: .text: unexpected end of section

/tmp/modconfig-Zo1IFu/vmmon-only/common/phystrack.o: warning: objtool: PhysTrack_Free() falls through to next function PhysTrack_Add()

/tmp/modconfig-Zo1IFu/vmmon-only/common/phystrack.o: warning: objtool: PhysTrack_Add() falls through to next function PhysTrack_Remove()

/tmp/modconfig-Zo1IFu/vmmon-only/common/phystrack.o: warning: objtool: PhysTrack_Remove() falls through to next function PhysTrack_Test()

  LD [M]  /tmp/modconfig-Zo1IFu/vmmon-only/vmmon.o

  Building modules, stage 2.

  MODPOST 1 modules

  CC      /tmp/modconfig-Zo1IFu/vmmon-only/vmmon.mod.o

  LD [M]  /tmp/modconfig-Zo1IFu/vmmon-only/vmmon.ko

make[1]: Leaving directory '/usr/src/kernels/4.9.12-200.fc25.x86_64'

/bin/make -C $PWD SRCROOT=$PWD/. \

  MODULEBUILDDIR= postbuild

make[1]: Entering directory '/tmp/modconfig-Zo1IFu/vmmon-only'

make[1]: 'postbuild' is up to date.

make[1]: Leaving directory '/tmp/modconfig-Zo1IFu/vmmon-only'

cp -f vmmon.ko ./../vmmon.o

make: Leaving directory '/tmp/modconfig-Zo1IFu/vmmon-only'

make: Entering directory '/tmp/modconfig-Zo1IFu/vmnet-only'

Using kernel build system.

/bin/make -C /lib/modules/4.9.12-200.fc25.x86_64/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. \

  MODULEBUILDDIR= modules

make[1]: Entering directory '/usr/src/kernels/4.9.12-200.fc25.x86_64'

  CC [M]  /tmp/modconfig-Zo1IFu/vmnet-only/driver.o

  CC [M]  /tmp/modconfig-Zo1IFu/vmnet-only/hub.o

  CC [M]  /tmp/modconfig-Zo1IFu/vmnet-only/userif.o

  CC [M]  /tmp/modconfig-Zo1IFu/vmnet-only/netif.o

In file included from ./include/linux/pci.h:35:0,

                 from /tmp/modconfig-Zo1IFu/vmnet-only/compat_netdevice.h:27,

                 from /tmp/modconfig-Zo1IFu/vmnet-only/netif.c:43:

./include/linux/pci_ids.h:2253:0: warning: "PCI_VENDOR_ID_VMWARE" redefined

#define PCI_VENDOR_ID_VMWARE  0x15ad

In file included from /tmp/modconfig-Zo1IFu/vmnet-only/net.h:38:0,

                 from /tmp/modconfig-Zo1IFu/vmnet-only/vnetInt.h:26,

                 from /tmp/modconfig-Zo1IFu/vmnet-only/netif.c:42:

/tmp/modconfig-Zo1IFu/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-Zo1IFu/vmnet-only/bridge.o

  CC [M]  /tmp/modconfig-Zo1IFu/vmnet-only/procfs.o

  CC [M]  /tmp/modconfig-Zo1IFu/vmnet-only/smac_compat.o

  CC [M]  /tmp/modconfig-Zo1IFu/vmnet-only/smac.o

  CC [M]  /tmp/modconfig-Zo1IFu/vmnet-only/vnetEvent.o

  CC [M]  /tmp/modconfig-Zo1IFu/vmnet-only/vnetUserListener.o

In file included from /tmp/modconfig-Zo1IFu/vmnet-only/net.h:38:0,

                 from /tmp/modconfig-Zo1IFu/vmnet-only/vnetInt.h:26,

                 from /tmp/modconfig-Zo1IFu/vmnet-only/bridge.c:52:

/tmp/modconfig-Zo1IFu/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:35:0,

                 from /tmp/modconfig-Zo1IFu/vmnet-only/compat_netdevice.h:27,

                 from /tmp/modconfig-Zo1IFu/vmnet-only/bridge.c:51:

./include/linux/pci_ids.h:2253:0: note: this is the location of the previous definition

#define PCI_VENDOR_ID_VMWARE  0x15ad

  LD [M]  /tmp/modconfig-Zo1IFu/vmnet-only/vmnet.o

  Building modules, stage 2.

  MODPOST 1 modules

  CC      /tmp/modconfig-Zo1IFu/vmnet-only/vmnet.mod.o

  LD [M]  /tmp/modconfig-Zo1IFu/vmnet-only/vmnet.ko

make[1]: Leaving directory '/usr/src/kernels/4.9.12-200.fc25.x86_64'

/bin/make -C $PWD SRCROOT=$PWD/. \

  MODULEBUILDDIR= postbuild

make[1]: Entering directory '/tmp/modconfig-Zo1IFu/vmnet-only'

make[1]: 'postbuild' is up to date.

make[1]: Leaving directory '/tmp/modconfig-Zo1IFu/vmnet-only'

cp -f vmnet.ko ./../vmnet.o

make: Leaving directory '/tmp/modconfig-Zo1IFu/vmnet-only'

Starting vmware (via systemctl):  Job for vmware.service failed because the control process exited with error code.

See "systemctl status vmware.service" and "journalctl -xe" for details.

                                                           [FAILED]

Unable to start services

ONE MORE TIME I CAN'T COMPILE THIS STUPID VMMON MODULE

0 Kudos
4 Replies
RDPetruska
Leadership
Leadership

I have already upgrade my OS to kernel 4.9.12-200.fc25.x86_64 and this software is not working, i think the vmware team is not taking serious job....each upgrade of kernel we (users) have a lot of troubles it is not fare, seariuosly changing the virtualization software would be a nice solution, but i will think diferent this time ccause it is necesary, here is the prlblem:

The VMware folks take it VERY seriously.  And put a majority of their efforts into the listed/stated SUPPORTED host OS's.  Fedora has NEVER been a SUPPORTED host OS, because of its very nature - it is Red Hat's experimental branch!  This is of course not to say that VMware won't work on unsupported hosts... but they may require workarounds or unofficial patches, etc. 

0 Kudos
jdelsolar
Contributor
Contributor

The VMware folks take it VERY seriously.  And put a majority of their efforts into the listed/stated SUPPORTED host OS's.  Fedora has NEVER been a SUPPORTED host OS, because of its very nature - it is Red Hat's experimental branch!  This is of course not to say that VMware won't work on unsupported hosts... but they may require workarounds or unofficial patches, etc.

Im sorry man, if you work in VMWARE TEAM let me tell you, you don't make good things, I can suppose that the pay version is more stable  and as you know, freeware needs to be useful in any environment, into any kernel, for any OS....im so so sorry but it is real....

taking in consideration what you've said, it is easy for you....eliminate the free version and just sell your product....you will have less headaches with users like me

Thanks in advance and hope you to work in my trouble, because you are there because of us (FREE USERS)

0 Kudos
dariusd
VMware Employee
VMware Employee

VMware Workstation Player/Pro make heavy use of low-level Linux kernel facilities, and those Linux kernel facilities are not guaranteed to be stable and unchanging.  We're not able to anticipate kernel changes which occur after our product is released, which sometimes leads to compatibility issues if you're running experimental/unsupported/bleeding-edge kernels.  Sorry for the disappointment.

Our free product and our paid product use the same virtualization engine and will almost certainly behave the same way with regard to the problem you are experiencing.

By the way, I do work at VMware, on the team responsible for the kernel modules.  We want our product to work well for all users of our products, free and paid.  I'm taking the time to try to help you out, even while I'm on vacation.  I would appreciate your continued respectful engagement during this discussion.

I'll continue trying to solve your problem over in VMware Workstation 12.5.2 build-4638234 does not compile on Fedora 25 4.9.3-200.fc25.x86_64 #1 SMP F...

Thanks in advance,

--

Darius

0 Kudos
jdelsolar
Contributor
Contributor

Dear Darius:

I appreciate your effort and thanks you very much for your help.

To improve this treat, i have formated my laptop....after install again VMWARE emvironment i will write here

Thank you very much

0 Kudos