VMware Communities
gk75abs
Contributor
Contributor
Jump to solution

VMware Workstation for Linux v12.5.7-5813279 don't install on RedHat Enterprise Linux 7.4 Beta1 ( kernel: 3.10.0-663.el7 )

Hello everybody,

For information:

VMware Workstation for Linux v12.5.7-5813279 don't install on RedHat Enterprise Linux 7.4 Beta1 ( kernel: 3.10.0-663.el7 )

During installation process, when VMware's kernel modules are compiling, is error, and installation process is break.

Informations from console:

...

make[1]: Opuszczenie katalogu `/usr/src/kernels/3.10.0-663.el7.x86_64'

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

  MODULEBUILDDIR= postbuild

make[1]: Wejście do katalogu `/tmp/modconfig-eNBseL/vmmon-only'

make[1]: `postbuild' jest aktualne.

make[1]: Opuszczenie katalogu `/tmp/modconfig-eNBseL/vmmon-only'

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

make: Opuszczenie katalogu `/tmp/modconfig-eNBseL/vmmon-only'

Using kernel build system.

make: Wejście do katalogu `/tmp/modconfig-eNBseL/vmnet-only'

/usr/bin/make -C /lib/modules/3.10.0-663.el7.x86_64/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. \

  MODULEBUILDDIR= modules

make[1]: Wejście do katalogu `/usr/src/kernels/3.10.0-663.el7.x86_64'

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

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

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

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

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

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

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

include/linux/pci_ids.h:2251:0: warning: "PCI_VENDOR_ID_VMWARE" redefined [enabled by default]

#define PCI_VENDOR_ID_VMWARE  0x15ad

^

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

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

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

/tmp/modconfig-eNBseL/vmnet-only/vm_device_version.h:56:0: note: this is the location of the previous definition

#define PCI_VENDOR_ID_VMWARE                    0x15AD

^

In file included from /tmp/modconfig-eNBseL/vmnet-only/netif.c:43:0:

/tmp/modconfig-eNBseL/vmnet-only/netif.c: In function ‘VNetNetifStartXmit’:

/tmp/modconfig-eNBseL/vmnet-only/compat_netdevice.h:343:46: error: ‘struct net_device’ has no member named ‘trans_start’

#define compat_netif_trans_update(d) do { (d)->trans_start = jiffies; } while (0)

                                              ^

/tmp/modconfig-eNBseL/vmnet-only/netif.c:468:4: note: in expansion of macro ‘compat_netif_trans_update’

    compat_netif_trans_update(dev);

    ^

make[2]: *** [/tmp/modconfig-eNBseL/vmnet-only/netif.o] Błąd 1

make[2]: *** Oczekiwanie na niezakończone zadania....

make[1]: *** [_module_/tmp/modconfig-eNBseL/vmnet-only] Błąd 2

make[1]: Opuszczenie katalogu `/usr/src/kernels/3.10.0-663.el7.x86_64'

make: *** [vmnet.ko] Błąd 2

make: Opuszczenie katalogu `/tmp/modconfig-eNBseL/vmnet-only'

Log from /tmp/vmware-root/vmware-31688.log as attach file.

Regards

Greg

20 Replies
dariusd
VMware Employee
VMware Employee
Jump to solution

arch/x86/Makefile:166: *** CONFIG_RETPOLINE=y, but not supported by the compiler. Toolchain update recommended..  Stop.

This isn't a problem with our modules, and can't be fixed with patching.

Your distro has included a kernel with "retpoline" mitigations for the Spectre/Meltdown issues.  When building any sort of kernel module, it's expected that the same compiler be used for the modules as was used for the kernel itself.  Unfortunately, the compiler on your host does not know about "retpoline" – in other words, it doesn't match the compiler which was used to build the kernel itself.  In this situation, I don't think any kernel modules can be built from source on that host.

Hopefully your distro will soon release an updated compiler which knows about "retpoline", at which time our kernel module should build correctly.

If your host is configured to receive security updates only, it's possible that the new kernel was considered a security update and delivered automatically, while the new compiler may not be considered a security update, so perhaps adjusting your update configuration will make the new compiler available for installation, which would also resolve the problem.

Cheers,

--

Darius

Reply
0 Kudos