[opensuse] Can't run vmware player in Leap 43.3, failure to build kernel modules.
Hi Can't build the vmware modules, some compile errors. I did not expect this after upgrading from Leap 42.2 to Leap 42.3, the kernel is not supposed to change that much and 42.3 is supposed to be mature. I typically prepare vmware by first preparing the kernel sources: #!/bin/bash echo -e "\n-- cloneconfig --" && make cloneconfig && echo -e "\n-- scripts --" && make scripts && echo -e "\n-- prepare --" && make prepare && echo -e "\n-- Done good! --" The output of this part was correct: cer@Telcontar:~> su - Password: Telcontar:~ # cd /usr/src/linux Telcontar:/usr/src/linux # ../preparar -- cloneconfig -- HOSTCC scripts/basic/fixdep HOSTCC scripts/kconfig/conf.o SHIPPED scripts/kconfig/zconf.tab.c SHIPPED scripts/kconfig/zconf.lex.c SHIPPED scripts/kconfig/zconf.hash.c HOSTCC scripts/kconfig/zconf.tab.o HOSTLD scripts/kconfig/conf Cloning configuration file /proc/config.gz # # configuration written to .config # -- scripts -- scripts/kconfig/conf --silentoldconfig Kconfig HOSTCC scripts/basic/bin2c WRAP arch/x86/include/generated/asm/clkdev.h WRAP arch/x86/include/generated/asm/cputime.h WRAP arch/x86/include/generated/asm/dma-contiguous.h WRAP arch/x86/include/generated/asm/early_ioremap.h WRAP arch/x86/include/generated/asm/mcs_spinlock.h WRAP arch/x86/include/generated/asm/mm-arch-hooks.h HOSTCC scripts/genksyms/genksyms.o SHIPPED scripts/genksyms/parse.tab.c HOSTCC scripts/genksyms/parse.tab.o SHIPPED scripts/genksyms/lex.lex.c SHIPPED scripts/genksyms/keywords.hash.c SHIPPED scripts/genksyms/parse.tab.h HOSTCC scripts/genksyms/lex.lex.o HOSTLD scripts/genksyms/genksyms CC scripts/mod/empty.o HOSTCC scripts/mod/mk_elfconfig MKELF scripts/mod/elfconfig.h HOSTCC scripts/mod/modpost.o CC scripts/mod/devicetable-offsets.s GEN scripts/mod/devicetable-offsets.h HOSTCC scripts/mod/file2alias.o HOSTCC scripts/mod/sumversion.o HOSTLD scripts/mod/modpost HOSTCC scripts/selinux/genheaders/genheaders HOSTCC scripts/selinux/mdp/mdp HOSTCC scripts/kallsyms HOSTCC scripts/conmakehash HOSTCC scripts/recordmcount HOSTCC scripts/sortextable HOSTCC scripts/asn1_compiler -- prepare -- SYSTBL arch/x86/entry/syscalls/../../include/generated/asm/syscalls_32.h SYSHDR arch/x86/entry/syscalls/../../include/generated/asm/unistd_32_ia32.h SYSHDR arch/x86/entry/syscalls/../../include/generated/asm/unistd_64_x32.h SYSTBL arch/x86/entry/syscalls/../../include/generated/asm/syscalls_64.h HYPERCALLS arch/x86/entry/syscalls/../../include/generated/asm/xen-hypercalls.h SYSHDR arch/x86/entry/syscalls/../../include/generated/uapi/asm/unistd_32.h SYSHDR arch/x86/entry/syscalls/../../include/generated/uapi/asm/unistd_64.h SYSHDR arch/x86/entry/syscalls/../../include/generated/uapi/asm/unistd_x32.h HOSTCC arch/x86/tools/relocs_32.o HOSTCC arch/x86/tools/relocs_64.o HOSTCC arch/x86/tools/relocs_common.o HOSTLD arch/x86/tools/relocs CHK include/config/kernel.release UPD include/config/kernel.release CHK include/generated/uapi/linux/version.h UPD include/generated/uapi/linux/version.h CHK include/generated/utsrelease.h UPD include/generated/utsrelease.h CC arch/x86/purgatory/purgatory.o AS arch/x86/purgatory/stack.o AS arch/x86/purgatory/setup-x86_64.o CC arch/x86/purgatory/sha256.o AS arch/x86/purgatory/entry64.o CC arch/x86/purgatory/string.o LD arch/x86/purgatory/purgatory.ro BIN2C arch/x86/purgatory/kexec-purgatory.c CC kernel/bounds.s CHK include/generated/bounds.h UPD include/generated/bounds.h CHK include/generated/timeconst.h UPD include/generated/timeconst.h CC arch/x86/kernel/asm-offsets.s CHK include/generated/asm-offsets.h UPD include/generated/asm-offsets.h CALL scripts/checksyscalls.sh -- Done good! -- If using Nvidia driver, now go to /root/Downloads, run the Nvidia.run file. If using vmplayer, now run vmplayer as root so that it updates itself accordingly to this kernel, wait for it to finish, then close it to start it again as plain user. Telcontar:/usr/src/linux # cd So then I run "vmplayer" as root, which starts a GUI and automatically builds the vmware modules. This is the result, and as you see it fails: Telcontar:~ # vmplayer (vmware-modconfig:18005): Gtk-WARNING **: Unable to locate theme engine in module_path: "crux-engine", (vmware-modconfig:18005): Gtk-WARNING **: Unable to locate theme engine in module_path: "crux-engine", Stopping VMware services: VMware Authentication Daemon VM communication interface socket family Virtual machine communication interface Virtual machine monitor Blocking file system make: Entering directory '/tmp/modconfig-YmrQpy/vmmon-only' Using kernel build system. /usr/bin/make -C /lib/modules/4.4.104-39-default/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. \ MODULEBUILDDIR= modules make[1]: Entering directory '/usr/src/linux-4.4.104-39-obj/x86_64/default' CC [M] /tmp/modconfig-YmrQpy/vmmon-only/linux/driverLog.o CC [M] /tmp/modconfig-YmrQpy/vmmon-only/linux/driver.o CC [M] /tmp/modconfig-YmrQpy/vmmon-only/linux/hostif.o CC [M] /tmp/modconfig-YmrQpy/vmmon-only/common/memtrack.o CC [M] /tmp/modconfig-YmrQpy/vmmon-only/common/apic.o CC [M] /tmp/modconfig-YmrQpy/vmmon-only/common/hashFunc.o CC [M] /tmp/modconfig-YmrQpy/vmmon-only/common/vmx86.o CC [M] /tmp/modconfig-YmrQpy/vmmon-only/common/cpuid.o CC [M] /tmp/modconfig-YmrQpy/vmmon-only/common/task.o /tmp/modconfig-YmrQpy/vmmon-only/linux/driver.c:1291:1: warning: always_inline function might not be inlinable [-Wattributes] LinuxDriverSyncReadTSCs(uint64 *delta) // OUT: TSC max - TSC min ^ /tmp/modconfig-YmrQpy/vmmon-only/linux/hostif.c: In function ‘HostIFGetUserPages’: /tmp/modconfig-YmrQpy/vmmon-only/linux/hostif.c:1174:28: warning: passing argument 1 of ‘get_user_pages’ makes integer from pointer without a cast [enabled by default] numPages, 0, 0, ppages, NULL); ^ In file included from /tmp/modconfig-YmrQpy/vmmon-only/./include/compat_page.h:23:0, from /tmp/modconfig-YmrQpy/vmmon-only/linux/hostif.c:32: /usr/src/linux-4.4.104-39/include/linux/mm.h:1264:6: note: expected ‘long unsigned int’ but argument is of type ‘struct task_struct *’ long get_user_pages(unsigned long start, unsigned long nr_pages, ^ /tmp/modconfig-YmrQpy/vmmon-only/linux/hostif.c:1174:28: warning: passing argument 2 of ‘get_user_pages’ makes integer from pointer without a cast [enabled by default] numPages, 0, 0, ppages, NULL); ^ In file included from /tmp/modconfig-YmrQpy/vmmon-only/./include/compat_page.h:23:0, from /tmp/modconfig-YmrQpy/vmmon-only/linux/hostif.c:32: /usr/src/linux-4.4.104-39/include/linux/mm.h:1264:6: note: expected ‘long unsigned int’ but argument is of type ‘struct mm_struct *’ long get_user_pages(unsigned long start, unsigned long nr_pages, ^ /tmp/modconfig-YmrQpy/vmmon-only/linux/hostif.c:1174:28: warning: passing argument 4 of ‘get_user_pages’ makes pointer from integer without a cast [enabled by default] numPages, 0, 0, ppages, NULL); ^ In file included from /tmp/modconfig-YmrQpy/vmmon-only/./include/compat_page.h:23:0, from /tmp/modconfig-YmrQpy/vmmon-only/linux/hostif.c:32: /usr/src/linux-4.4.104-39/include/linux/mm.h:1264:6: note: expected ‘struct page **’ but argument is of type ‘unsigned int’ long get_user_pages(unsigned long start, unsigned long nr_pages, ^ /tmp/modconfig-YmrQpy/vmmon-only/linux/hostif.c:1174:28: error: too many arguments to function ‘get_user_pages’ numPages, 0, 0, ppages, NULL); ^ In file included from /tmp/modconfig-YmrQpy/vmmon-only/./include/compat_page.h:23:0, from /tmp/modconfig-YmrQpy/vmmon-only/linux/hostif.c:32: /usr/src/linux-4.4.104-39/include/linux/mm.h:1264:6: note: declared here long get_user_pages(unsigned long start, unsigned long nr_pages, ^ /usr/src/linux-4.4.104-39/scripts/Makefile.build:259: recipe for target '/tmp/modconfig-YmrQpy/vmmon-only/linux/hostif.o' failed make[4]: *** [/tmp/modconfig-YmrQpy/vmmon-only/linux/hostif.o] Error 1 make[4]: *** Waiting for unfinished jobs.... /usr/src/linux-4.4.104-39/Makefile:1431: recipe for target '_module_/tmp/modconfig-YmrQpy/vmmon-only' failed make[3]: *** [_module_/tmp/modconfig-YmrQpy/vmmon-only] Error 2 Makefile:150: recipe for target 'sub-make' failed make[2]: *** [sub-make] Error 2 Makefile:24: recipe for target '__sub-make' failed make[1]: *** [__sub-make] Error 2 make[1]: Leaving directory '/usr/src/linux-4.4.104-39-obj/x86_64/default' Makefile:120: recipe for target 'vmmon.ko' failed make: *** [vmmon.ko] Error 2 make: Leaving directory '/tmp/modconfig-YmrQpy/vmmon-only' make: Entering directory '/tmp/modconfig-YmrQpy/vmnet-only' Using kernel build system. /usr/bin/make -C /lib/modules/4.4.104-39-default/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. \ MODULEBUILDDIR= modules make[1]: Entering directory '/usr/src/linux-4.4.104-39-obj/x86_64/default' CC [M] /tmp/modconfig-YmrQpy/vmnet-only/driver.o CC [M] /tmp/modconfig-YmrQpy/vmnet-only/hub.o CC [M] /tmp/modconfig-YmrQpy/vmnet-only/netif.o CC [M] /tmp/modconfig-YmrQpy/vmnet-only/userif.o /tmp/modconfig-YmrQpy/vmnet-only/userif.c: In function ‘UserifLockPage’: /tmp/modconfig-YmrQpy/vmnet-only/userif.c:125:28: warning: passing argument 1 of ‘get_user_pages’ makes integer from pointer without a cast [enabled by default] 1, 1, 0, &page, NULL); ^ In file included from /usr/src/linux-4.4.104-39/include/linux/highmem.h:7:0, from /tmp/modconfig-YmrQpy/vmnet-only/userif.c:26: /usr/src/linux-4.4.104-39/include/linux/mm.h:1264:6: note: expected ‘long unsigned int’ but argument is of type ‘struct task_struct *’ long get_user_pages(unsigned long start, unsigned long nr_pages, ^ /tmp/modconfig-YmrQpy/vmnet-only/userif.c:125:28: warning: passing argument 2 of ‘get_user_pages’ makes integer from pointer without a cast [enabled by default] 1, 1, 0, &page, NULL); ^ In file included from /usr/src/linux-4.4.104-39/include/linux/highmem.h:7:0, from /tmp/modconfig-YmrQpy/vmnet-only/userif.c:26: /usr/src/linux-4.4.104-39/include/linux/mm.h:1264:6: note: expected ‘long unsigned int’ but argument is of type ‘struct mm_struct *’ long get_user_pages(unsigned long start, unsigned long nr_pages, ^ /tmp/modconfig-YmrQpy/vmnet-only/userif.c:125:28: warning: passing argument 4 of ‘get_user_pages’ makes pointer from integer without a cast [enabled by default] 1, 1, 0, &page, NULL); ^ In file included from /usr/src/linux-4.4.104-39/include/linux/highmem.h:7:0, from /tmp/modconfig-YmrQpy/vmnet-only/userif.c:26: /usr/src/linux-4.4.104-39/include/linux/mm.h:1264:6: note: expected ‘struct page **’ but argument is of type ‘int’ long get_user_pages(unsigned long start, unsigned long nr_pages, ^ /tmp/modconfig-YmrQpy/vmnet-only/userif.c:125:28: warning: passing argument 5 of ‘get_user_pages’ makes pointer from integer without a cast [enabled by default] 1, 1, 0, &page, NULL); ^ In file included from /usr/src/linux-4.4.104-39/include/linux/highmem.h:7:0, from /tmp/modconfig-YmrQpy/vmnet-only/userif.c:26: /usr/src/linux-4.4.104-39/include/linux/mm.h:1264:6: note: expected ‘struct vm_area_struct **’ but argument is of type ‘int’ long get_user_pages(unsigned long start, unsigned long nr_pages, ^ /tmp/modconfig-YmrQpy/vmnet-only/userif.c:125:28: error: too many arguments to function ‘get_user_pages’ 1, 1, 0, &page, NULL); ^ In file included from /usr/src/linux-4.4.104-39/include/linux/highmem.h:7:0, from /tmp/modconfig-YmrQpy/vmnet-only/userif.c:26: /usr/src/linux-4.4.104-39/include/linux/mm.h:1264:6: note: declared here long get_user_pages(unsigned long start, unsigned long nr_pages, ^ In file included from /usr/src/linux-4.4.104-39/include/linux/pci.h:36:0, from /tmp/modconfig-YmrQpy/vmnet-only/compat_netdevice.h:27, from /tmp/modconfig-YmrQpy/vmnet-only/netif.c:43: /usr/src/linux-4.4.104-39/include/linux/pci_ids.h:2256:0: warning: "PCI_VENDOR_ID_VMWARE" redefined [enabled by default] #define PCI_VENDOR_ID_VMWARE 0x15ad ^ In file included from /tmp/modconfig-YmrQpy/vmnet-only/net.h:38:0, from /tmp/modconfig-YmrQpy/vmnet-only/vnetInt.h:26, from /tmp/modconfig-YmrQpy/vmnet-only/netif.c:42: /tmp/modconfig-YmrQpy/vmnet-only/vm_device_version.h:56:0: note: this is the location of the previous definition #define PCI_VENDOR_ID_VMWARE 0x15AD ^ /usr/src/linux-4.4.104-39/scripts/Makefile.build:259: recipe for target '/tmp/modconfig-YmrQpy/vmnet-only/userif.o' failed make[4]: *** [/tmp/modconfig-YmrQpy/vmnet-only/userif.o] Error 1 make[4]: *** Waiting for unfinished jobs.... In file included from /tmp/modconfig-YmrQpy/vmnet-only/netif.c:43:0: /tmp/modconfig-YmrQpy/vmnet-only/netif.c: In function ‘VNetNetifStartXmit’: /tmp/modconfig-YmrQpy/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-YmrQpy/vmnet-only/netif.c:468:4: note: in expansion of macro ‘compat_netif_trans_update’ compat_netif_trans_update(dev); ^ /usr/src/linux-4.4.104-39/scripts/Makefile.build:259: recipe for target '/tmp/modconfig-YmrQpy/vmnet-only/netif.o' failed make[4]: *** [/tmp/modconfig-YmrQpy/vmnet-only/netif.o] Error 1 /usr/src/linux-4.4.104-39/Makefile:1431: recipe for target '_module_/tmp/modconfig-YmrQpy/vmnet-only' failed make[3]: *** [_module_/tmp/modconfig-YmrQpy/vmnet-only] Error 2 Makefile:150: recipe for target 'sub-make' failed make[2]: *** [sub-make] Error 2 Makefile:24: recipe for target '__sub-make' failed make[1]: *** [__sub-make] Error 2 make[1]: Leaving directory '/usr/src/linux-4.4.104-39-obj/x86_64/default' Makefile:120: recipe for target 'vmnet.ko' failed make: *** [vmnet.ko] Error 2 make: Leaving directory '/tmp/modconfig-YmrQpy/vmnet-only' Starting VMware services: Virtual machine monitor Virtual machine communication interface VM communication interface socket family Blocking file system Virtual ethernet VMware Authentication Daemon Telcontar:~ # It also pops up a window telling to read certain log file: Telcontar:/tmp/vmware-root # cat /tmp/vmware-root/vmware-18005.log 2018-02-06T01:35:05.836+01:00| vthread-4| I125: Log for VMware Workstation pid=18005 version=12.5.6 build=build-5528349 option=Release 2018-02-06T01:35:05.836+01:00| vthread-4| I125: The process is 64-bit. 2018-02-06T01:35:05.836+01:00| vthread-4| I125: Host codepage=UTF-8 encoding=UTF-8 2018-02-06T01:35:05.836+01:00| vthread-4| I125: Host is Linux 4.4.104-39-default openSUSE Leap 42.3 2018-02-06T01:35:05.832+01:00| vthread-4| I125: DictionaryLoad: Cannot open file "/usr/lib/vmware/settings": No such file or directory. 2018-02-06T01:35:05.832+01:00| vthread-4| I125: PREF Optional preferences file not found at /usr/lib/vmware/settings. Using default values. 2018-02-06T01:35:05.834+01:00| vthread-4| I125: DictionaryLoad: Cannot open file "/root/.vmware/config": No such file or directory. 2018-02-06T01:35:05.834+01:00| vthread-4| I125: PREF Optional preferences file not found at /root/.vmware/config. Using default values. 2018-02-06T01:35:05.854+01:00| vthread-4| W115: Logging to /tmp/vmware-root/vmware-18005.log 2018-02-06T01:35:05.875+01:00| vthread-4| I125: System distribution is SuSE 2018-02-06T01:35:05.875+01:00| vthread-4| I125: System version is 42.3 2018-02-06T01:35:05.875+01:00| vthread-4| I125: Obtaining info using the running kernel. 2018-02-06T01:35:05.875+01:00| vthread-4| I125: Created new pathsHash. 2018-02-06T01:35:05.875+01:00| vthread-4| I125: Setting header path for 4.4.104-39-default to "/lib/modules/4.4.104-39-default/build/include". 2018-02-06T01:35:05.875+01:00| vthread-4| I125: Validating path "/lib/modules/4.4.104-39-default/build/include" for kernel release "4.4.104-39-default". 2018-02-06T01:35:07.381+01:00| vthread-4| I125: Failed to find /lib/modules/4.4.104-39-default/build/include/linux/version.h 2018-02-06T01:35:07.381+01:00| vthread-4| I125: /lib/modules/4.4.104-39-default/build/include/linux/version.h not found, looking for generated/uapi/linux/version.h instead. 2018-02-06T01:35:07.381+01:00| vthread-4| I125: using /usr/bin/gcc-4.8 for preprocess check 2018-02-06T01:35:07.391+01:00| vthread-4| I125: Preprocessed UTS_RELEASE, got value "4.4.104-39-default". 2018-02-06T01:35:07.391+01:00| vthread-4| I125: The header path "/lib/modules/4.4.104-39-default/build/include" for the kernel "4.4.104-39-default" is valid. Whoohoo! 2018-02-06T01:35:07.565+01:00| vthread-4| I125: found symbol version file /lib/modules/4.4.104-39-default/build/Module.symvers 2018-02-06T01:35:07.565+01:00| vthread-4| I125: Reading symbol versions from /lib/modules/4.4.104-39-default/build/Module.symvers. 2018-02-06T01:35:07.658+01:00| vthread-4| I125: Read 18154 symbol versions 2018-02-06T01:35:07.663+01:00| vthread-4| I125: Reading in info for the vmmon module. 2018-02-06T01:35:07.663+01:00| vthread-4| I125: Reading in info for the vmnet module. 2018-02-06T01:35:07.663+01:00| vthread-4| I125: Reading in info for the vmblock module. 2018-02-06T01:35:07.663+01:00| vthread-4| I125: Reading in info for the vmci module. 2018-02-06T01:35:07.663+01:00| vthread-4| I125: Reading in info for the vsock module. 2018-02-06T01:35:07.663+01:00| vthread-4| I125: Setting vsock to depend on vmci. 2018-02-06T01:35:07.663+01:00| vthread-4| I125: Invoking modinfo on "vmmon". 2018-02-06T01:35:07.667+01:00| vthread-4| I125: "/sbin/modinfo" exited with status 256. 2018-02-06T01:35:07.667+01:00| vthread-4| I125: Invoking modinfo on "vmnet". 2018-02-06T01:35:07.669+01:00| vthread-4| I125: "/sbin/modinfo" exited with status 256. 2018-02-06T01:35:07.670+01:00| vthread-4| I125: Invoking modinfo on "vmblock". 2018-02-06T01:35:07.672+01:00| vthread-4| I125: "/sbin/modinfo" exited with status 256. 2018-02-06T01:35:07.672+01:00| vthread-4| I125: Invoking modinfo on "vmci". 2018-02-06T01:35:07.673+01:00| vthread-4| I125: "/sbin/modinfo" exited with status 256. 2018-02-06T01:35:07.673+01:00| vthread-4| I125: Invoking modinfo on "vsock". 2018-02-06T01:35:07.677+01:00| vthread-4| I125: "/sbin/modinfo" exited with status 0. 2018-02-06T01:35:07.695+01:00| vthread-4| I125: to be installed: vmmon status: 0 2018-02-06T01:35:07.695+01:00| vthread-4| I125: to be installed: vmnet status: 0 2018-02-06T01:35:07.740+01:00| vthread-4| I125: Obtaining info using the running kernel. 2018-02-06T01:35:07.740+01:00| vthread-4| I125: Setting header path for 4.4.104-39-default to "/lib/modules/4.4.104-39-default/build/include". 2018-02-06T01:35:07.740+01:00| vthread-4| I125: Validating path "/lib/modules/4.4.104-39-default/build/include" for kernel release "4.4.104-39-default". 2018-02-06T01:35:07.741+01:00| vthread-4| I125: Failed to find /lib/modules/4.4.104-39-default/build/include/linux/version.h 2018-02-06T01:35:07.741+01:00| vthread-4| I125: /lib/modules/4.4.104-39-default/build/include/linux/version.h not found, looking for generated/uapi/linux/version.h instead. 2018-02-06T01:35:07.741+01:00| vthread-4| I125: using /usr/bin/gcc-4.8 for preprocess check 2018-02-06T01:35:07.749+01:00| vthread-4| I125: Preprocessed UTS_RELEASE, got value "4.4.104-39-default". 2018-02-06T01:35:07.749+01:00| vthread-4| I125: The header path "/lib/modules/4.4.104-39-default/build/include" for the kernel "4.4.104-39-default" is valid. Whoohoo! 2018-02-06T01:35:07.922+01:00| vthread-4| I125: found symbol version file /lib/modules/4.4.104-39-default/build/Module.symvers 2018-02-06T01:35:07.922+01:00| vthread-4| I125: Reading symbol versions from /lib/modules/4.4.104-39-default/build/Module.symvers. 2018-02-06T01:35:07.943+01:00| vthread-4| I125: Read 18154 symbol versions 2018-02-06T01:35:07.943+01:00| vthread-4| I125: Kernel header path retrieved from FileEntry: /lib/modules/4.4.104-39-default/build/include 2018-02-06T01:35:07.943+01:00| vthread-4| I125: Update kernel header path to /lib/modules/4.4.104-39-default/build/include 2018-02-06T01:35:07.943+01:00| vthread-4| I125: Validating path "/lib/modules/4.4.104-39-default/build/include" for kernel release "4.4.104-39-default". 2018-02-06T01:35:07.943+01:00| vthread-4| I125: Failed to find /lib/modules/4.4.104-39-default/build/include/linux/version.h 2018-02-06T01:35:07.943+01:00| vthread-4| I125: /lib/modules/4.4.104-39-default/build/include/linux/version.h not found, looking for generated/uapi/linux/version.h instead. 2018-02-06T01:35:07.943+01:00| vthread-4| I125: using /usr/bin/gcc-4.8 for preprocess check 2018-02-06T01:35:07.952+01:00| vthread-4| I125: Preprocessed UTS_RELEASE, got value "4.4.104-39-default". 2018-02-06T01:35:07.952+01:00| vthread-4| I125: The header path "/lib/modules/4.4.104-39-default/build/include" for the kernel "4.4.104-39-default" is valid. Whoohoo! 2018-02-06T01:35:07.953+01:00| vthread-4| I125: Found compiler at "/usr/bin/gcc" 2018-02-06T01:35:07.957+01:00| vthread-4| I125: Got gcc version "4.8". 2018-02-06T01:35:07.957+01:00| vthread-4| I125: The GCC version matches the kernel GCC minor version like a glove. 2018-02-06T01:35:07.957+01:00| vthread-4| I125: Using user supplied compiler "/usr/bin/gcc". 2018-02-06T01:35:07.961+01:00| vthread-4| I125: Got gcc version "4.8". 2018-02-06T01:35:07.961+01:00| vthread-4| I125: The GCC version matches the kernel GCC minor version like a glove. 2018-02-06T01:35:07.963+01:00| vthread-4| I125: Trying to find a suitable PBM set for kernel "4.4.104-39-default". 2018-02-06T01:35:07.963+01:00| vthread-4| I125: No matching PBM set was found for kernel "4.4.104-39-default". 2018-02-06T01:35:07.963+01:00| vthread-4| I125: The GCC version matches the kernel GCC minor version like a glove. 2018-02-06T01:35:07.963+01:00| vthread-4| I125: Validating path "/lib/modules/4.4.104-39-default/build/include" for kernel release "4.4.104-39-default". 2018-02-06T01:35:07.963+01:00| vthread-4| I125: Failed to find /lib/modules/4.4.104-39-default/build/include/linux/version.h 2018-02-06T01:35:07.963+01:00| vthread-4| I125: /lib/modules/4.4.104-39-default/build/include/linux/version.h not found, looking for generated/uapi/linux/version.h instead. 2018-02-06T01:35:07.963+01:00| vthread-4| I125: using /usr/bin/gcc-4.8 for preprocess check 2018-02-06T01:35:07.972+01:00| vthread-4| I125: Preprocessed UTS_RELEASE, got value "4.4.104-39-default". 2018-02-06T01:35:07.972+01:00| vthread-4| I125: The header path "/lib/modules/4.4.104-39-default/build/include" for the kernel "4.4.104-39-default" is valid. Whoohoo! 2018-02-06T01:35:07.975+01:00| vthread-4| I125: The GCC version matches the kernel GCC minor version like a glove. 2018-02-06T01:35:07.975+01:00| vthread-4| I125: Validating path "/lib/modules/4.4.104-39-default/build/include" for kernel release "4.4.104-39-default". 2018-02-06T01:35:07.975+01:00| vthread-4| I125: Failed to find /lib/modules/4.4.104-39-default/build/include/linux/version.h 2018-02-06T01:35:07.975+01:00| vthread-4| I125: /lib/modules/4.4.104-39-default/build/include/linux/version.h not found, looking for generated/uapi/linux/version.h instead. 2018-02-06T01:35:07.975+01:00| vthread-4| I125: using /usr/bin/gcc-4.8 for preprocess check 2018-02-06T01:35:07.984+01:00| vthread-4| I125: Preprocessed UTS_RELEASE, got value "4.4.104-39-default". 2018-02-06T01:35:07.984+01:00| vthread-4| I125: The header path "/lib/modules/4.4.104-39-default/build/include" for the kernel "4.4.104-39-default" is valid. Whoohoo! 2018-02-06T01:35:07.984+01:00| vthread-4| I125: Using temp dir "/tmp". 2018-02-06T01:35:07.985+01:00| vthread-4| I125: Obtaining info using the running kernel. 2018-02-06T01:35:07.985+01:00| vthread-4| I125: Setting header path for 4.4.104-39-default to "/lib/modules/4.4.104-39-default/build/include". 2018-02-06T01:35:07.985+01:00| vthread-4| I125: Validating path "/lib/modules/4.4.104-39-default/build/include" for kernel release "4.4.104-39-default". 2018-02-06T01:35:07.985+01:00| vthread-4| I125: Failed to find /lib/modules/4.4.104-39-default/build/include/linux/version.h 2018-02-06T01:35:07.985+01:00| vthread-4| I125: /lib/modules/4.4.104-39-default/build/include/linux/version.h not found, looking for generated/uapi/linux/version.h instead. 2018-02-06T01:35:07.985+01:00| vthread-4| I125: using /usr/bin/gcc-4.8 for preprocess check 2018-02-06T01:35:07.994+01:00| vthread-4| I125: Preprocessed UTS_RELEASE, got value "4.4.104-39-default". 2018-02-06T01:35:07.994+01:00| vthread-4| I125: The header path "/lib/modules/4.4.104-39-default/build/include" for the kernel "4.4.104-39-default" is valid. Whoohoo! 2018-02-06T01:35:08.167+01:00| vthread-4| I125: found symbol version file /lib/modules/4.4.104-39-default/build/Module.symvers 2018-02-06T01:35:08.167+01:00| vthread-4| I125: Reading symbol versions from /lib/modules/4.4.104-39-default/build/Module.symvers. 2018-02-06T01:35:08.188+01:00| vthread-4| I125: Read 18154 symbol versions 2018-02-06T01:35:08.188+01:00| vthread-4| I125: Invoking modinfo on "vmmon". 2018-02-06T01:35:08.191+01:00| vthread-4| I125: "/sbin/modinfo" exited with status 256. 2018-02-06T01:35:08.191+01:00| vthread-4| I125: Invoking modinfo on "vmnet". 2018-02-06T01:35:08.194+01:00| vthread-4| I125: "/sbin/modinfo" exited with status 256. 2018-02-06T01:35:08.415+01:00| vthread-4| I125: Setting destination path for vmmon to "/lib/modules/4.4.104-39-default/misc/vmmon.ko". 2018-02-06T01:35:08.416+01:00| vthread-4| I125: Extracting the vmmon source from "/usr/lib/vmware/modules/source/vmmon.tar". 2018-02-06T01:35:08.437+01:00| vthread-4| I125: Successfully extracted the vmmon source. 2018-02-06T01:35:08.437+01:00| vthread-4| I125: Building module with command "/usr/bin/make -j4 -C /tmp/modconfig-YmrQpy/vmmon-only auto-build HEADER_DIR=/lib/modules/4.4.104-39-default/build/include CC=/usr/bin/gcc IS_GCC_3=no" 2018-02-06T01:35:10.518+01:00| vthread-4| W115: Failed to build vmmon. Failed to execute the build command. 2018-02-06T01:35:10.521+01:00| vthread-4| I125: Setting destination path for vmnet to "/lib/modules/4.4.104-39-default/misc/vmnet.ko". 2018-02-06T01:35:10.521+01:00| vthread-4| I125: Extracting the vmnet source from "/usr/lib/vmware/modules/source/vmnet.tar". 2018-02-06T01:35:10.531+01:00| vthread-4| I125: Successfully extracted the vmnet source. 2018-02-06T01:35:10.531+01:00| vthread-4| I125: Building module with command "/usr/bin/make -j4 -C /tmp/modconfig-YmrQpy/vmnet-only auto-build HEADER_DIR=/lib/modules/4.4.104-39-default/build/include CC=/usr/bin/gcc IS_GCC_3=no" 2018-02-06T01:35:12.673+01:00| vthread-4| W115: Failed to build vmnet. Failed to execute the build command. 2018-02-06T01:43:47.423+01:00| vthread-4| I125: The GCC version matches the kernel GCC minor version like a glove. 2018-02-06T01:43:47.423+01:00| vthread-4| I125: Validating path "/lib/modules/4.4.104-39-default/build/include" for kernel release "4.4.104-39-default". 2018-02-06T01:43:47.423+01:00| vthread-4| I125: Failed to find /lib/modules/4.4.104-39-default/build/include/linux/version.h 2018-02-06T01:43:47.423+01:00| vthread-4| I125: /lib/modules/4.4.104-39-default/build/include/linux/version.h not found, looking for generated/uapi/linux/version.h instead. 2018-02-06T01:43:47.423+01:00| vthread-4| I125: using /usr/bin/gcc-4.8 for preprocess check 2018-02-06T01:43:47.432+01:00| vthread-4| I125: Preprocessed UTS_RELEASE, got value "4.4.104-39-default". 2018-02-06T01:43:47.432+01:00| vthread-4| I125: The header path "/lib/modules/4.4.104-39-default/build/include" for the kernel "4.4.104-39-default" is valid. Whoohoo! 2018-02-06T01:43:47.432+01:00| vthread-4| I125: Using temp dir "/tmp". 2018-02-06T01:43:47.433+01:00| vthread-4| I125: Obtaining info using the running kernel. 2018-02-06T01:43:47.433+01:00| vthread-4| I125: Setting header path for 4.4.104-39-default to "/lib/modules/4.4.104-39-default/build/include". 2018-02-06T01:43:47.433+01:00| vthread-4| I125: Validating path "/lib/modules/4.4.104-39-default/build/include" for kernel release "4.4.104-39-default". 2018-02-06T01:43:47.433+01:00| vthread-4| I125: Failed to find /lib/modules/4.4.104-39-default/build/include/linux/version.h 2018-02-06T01:43:47.433+01:00| vthread-4| I125: /lib/modules/4.4.104-39-default/build/include/linux/version.h not found, looking for generated/uapi/linux/version.h instead. 2018-02-06T01:43:47.433+01:00| vthread-4| I125: using /usr/bin/gcc-4.8 for preprocess check 2018-02-06T01:43:47.442+01:00| vthread-4| I125: Preprocessed UTS_RELEASE, got value "4.4.104-39-default". 2018-02-06T01:43:47.442+01:00| vthread-4| I125: The header path "/lib/modules/4.4.104-39-default/build/include" for the kernel "4.4.104-39-default" is valid. Whoohoo! 2018-02-06T01:43:47.619+01:00| vthread-4| I125: found symbol version file /lib/modules/4.4.104-39-default/build/Module.symvers 2018-02-06T01:43:47.619+01:00| vthread-4| I125: Reading symbol versions from /lib/modules/4.4.104-39-default/build/Module.symvers. 2018-02-06T01:43:47.646+01:00| vthread-4| I125: Read 18154 symbol versions 2018-02-06T01:43:47.646+01:00| vthread-4| I125: Invoking modinfo on "vmmon". 2018-02-06T01:43:47.650+01:00| vthread-4| I125: "/sbin/modinfo" exited with status 256. 2018-02-06T01:43:47.650+01:00| vthread-4| I125: Invoking modinfo on "vmnet". 2018-02-06T01:43:47.653+01:00| vthread-4| I125: "/sbin/modinfo" exited with status 256. 2018-02-06T01:43:48.064+01:00| vthread-4| I125: Setting destination path for vmmon to "/lib/modules/4.4.104-39-default/misc/vmmon.ko". 2018-02-06T01:43:48.065+01:00| vthread-4| I125: Extracting the vmmon source from "/usr/lib/vmware/modules/source/vmmon.tar". 2018-02-06T01:43:48.076+01:00| vthread-4| I125: Successfully extracted the vmmon source. 2018-02-06T01:43:48.076+01:00| vthread-4| I125: Building module with command "/usr/bin/make -j4 -C /tmp/modconfig-G87D7K/vmmon-only auto-build HEADER_DIR=/lib/modules/4.4.104-39-default/build/include CC=/usr/bin/gcc IS_GCC_3=no" 2018-02-06T01:43:50.035+01:00| vthread-4| W115: Failed to build vmmon. Failed to execute the build command. 2018-02-06T01:43:50.038+01:00| vthread-4| I125: Setting destination path for vmnet to "/lib/modules/4.4.104-39-default/misc/vmnet.ko". 2018-02-06T01:43:50.038+01:00| vthread-4| I125: Extracting the vmnet source from "/usr/lib/vmware/modules/source/vmnet.tar". 2018-02-06T01:43:50.045+01:00| vthread-4| I125: Successfully extracted the vmnet source. 2018-02-06T01:43:50.045+01:00| vthread-4| I125: Building module with command "/usr/bin/make -j4 -C /tmp/modconfig-G87D7K/vmnet-only auto-build HEADER_DIR=/lib/modules/4.4.104-39-default/build/include CC=/usr/bin/gcc IS_GCC_3=no" 2018-02-06T01:43:51.784+01:00| vthread-4| W115: Failed to build vmnet. Failed to execute the build command. Telcontar:/tmp/vmware-root # -- Cheers / Saludos, Carlos E. R. (from 42.2 x86_64 "Malachite" at Telcontar)
06.02.2018 03:56, Carlos E. R. пишет:
Hi
Can't build the vmware modules, some compile errors. I did not expect this after upgrading from Leap 42.2 to Leap 42.3, the kernel is not supposed to change that much and 42.3 is supposed to be mature.
I typically prepare vmware by first preparing the kernel sources:
#!/bin/bash echo -e "\n-- cloneconfig --" && make cloneconfig && echo -e "\n-- scripts --" && make scripts && echo -e "\n-- prepare --" && make prepare && echo -e "\n-- Done good! --"
Which you neither need nor should do for the last 15 years or so. That is what kernel-devel packages are for.
On 2018-02-06 04:48, Andrei Borzenkov wrote:
06.02.2018 03:56, Carlos E. R. пишет:
Hi
Can't build the vmware modules, some compile errors. I did not expect this after upgrading from Leap 42.2 to Leap 42.3, the kernel is not supposed to change that much and 42.3 is supposed to be mature.
I typically prepare vmware by first preparing the kernel sources:
#!/bin/bash echo -e "\n-- cloneconfig --" && make cloneconfig && echo -e "\n-- scripts --" && make scripts && echo -e "\n-- prepare --" && make prepare && echo -e "\n-- Done good! --"
Which you neither need nor should do for the last 15 years or so.
That is what kernel-devel packages are for.
Maybe, but as this machine does have the sources installed (and always had), then they have to be prepared, AFAIK :-) Anyway, that was not the problem, I had to update vmware. -- Cheers / Saludos, Carlos E. R. (from 42.2 x86_64 "Malachite" at Telcontar)
Am Dienstag, 6. Februar 2018, 01:56:53 CET schrieb Carlos E. R.:
Hi
Can't build the vmware modules, some compile errors. I did not expect this after upgrading from Leap 42.2 to Leap 42.3, the kernel is not supposed to change that much and 42.3 is supposed to be mature.
You are trying to use vmware-12.5.6, which doesn't support Leap-42.3 because
the 42.3 kernel includes some backports from later kernels, which vmware-12.5
isn't aware of.
Either upgrade to vmware-14, which officially supports Leap-42.3 or hack the
source of vmwares kernel modules as described in henrikw84s post in
On 2018-02-06 11:33, Markus Koßmann wrote:
Am Dienstag, 6. Februar 2018, 01:56:53 CET schrieb Carlos E. R.:
Hi
Can't build the vmware modules, some compile errors. I did not expect this after upgrading from Leap 42.2 to Leap 42.3, the kernel is not supposed to change that much and 42.3 is supposed to be mature.
You are trying to use vmware-12.5.6, which doesn't support Leap-42.3 because the 42.3 kernel includes some backports from later kernels, which vmware-12.5 isn't aware of. Either upgrade to vmware-14, which officially supports Leap-42.3 or hack the source of vmwares kernel modules as described in henrikw84s post in
Ok, thanks. As vmware doesn't start, it does not offer to upgrade... I'll try manually. https://www.vmware.com/products/workstation-player/workstation-player-evalua... Got version 14.0.0 -- Cheers / Saludos, Carlos E. R. (from 42.2 x86_64 "Malachite" at Telcontar)
On 2018-02-06 13:26, Carlos E. R. wrote:
On 2018-02-06 11:33, Markus Koßmann wrote:
Am Dienstag, 6. Februar 2018, 01:56:53 CET schrieb Carlos E. R.:
Hi
Can't build the vmware modules, some compile errors. I did not expect this after upgrading from Leap 42.2 to Leap 42.3, the kernel is not supposed to change that much and 42.3 is supposed to be mature.
You are trying to use vmware-12.5.6, which doesn't support Leap-42.3 because the 42.3 kernel includes some backports from later kernels, which vmware-12.5 isn't aware of. Either upgrade to vmware-14, which officially supports Leap-42.3 or hack the source of vmwares kernel modules as described in henrikw84s post in
Ok, thanks.
As vmware doesn't start, it does not offer to upgrade... I'll try manually.
https://www.vmware.com/products/workstation-player/workstation-player-evalua...
Got version 14.0.0
Installed, run vmplayer, says it wants to update itself to version 14.1.1, and now pops up a message: Unsupported CPU detected The host CPU does not support the necessary hardware requirements. Click Quit to stop installation. If you Ignore this message to proceed with installation, you may not be able to launch virtual machines on this host. For details, please refer to the following Knowledge Base article: https://kb.vmware.com/kb/51643 WTF? And when I try to run a machine, I get this: This host does not support "Intel EPT" hardware assisted MMU virtualization. This host does not support virtualizing real mode. The Intel "VMX Unrestricted Guest" feature is necessary to run this virtual machine on an Intel processor. Module 'CPUIDEarly' power on failed. Failed to start the virtual machine. WTF? I have a "6.23.10 "Intel(R) Core(TM)2 Quad CPU Q9550 @ 2.83GHz", it does have virtualization support. :-// -- Cheers / Saludos, Carlos E. R. (from 42.2 x86_64 "Malachite" at Telcontar)
Carlos E. R. wrote:
On 2018-02-06 13:26, Carlos E. R. wrote: [snip]
I have a "6.23.10 "Intel(R) Core(TM)2 Quad CPU Q9550 @ 2.83GHz", it does have virtualization support.
The kb article you mentioned says "systems using processors laucnhed in 2011 or later are supported", with some exceptions. Your Q9550 is from 2008. Wow. -- Per Jessen, Zürich (1.7°C) http://www.dns24.ch/ - your free DNS host, made in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2018-02-06 15:40, Per Jessen wrote:
Carlos E. R. wrote:
On 2018-02-06 13:26, Carlos E. R. wrote: [snip]
I have a "6.23.10 "Intel(R) Core(TM)2 Quad CPU Q9550 @ 2.83GHz", it does have virtualization support.
The kb article you mentioned says "systems using processors laucnhed in 2011 or later are supported", with some exceptions. Your Q9550 is from 2008.
Wow.
Yep. But I bought it on 2009-12, and I have no intention to buy a new computer. -- Cheers / Saludos, Carlos E. R. (from 42.2 x86_64 "Malachite" at Telcontar)
On 2018-02-06 14:09, Carlos E. R. wrote:
On 2018-02-06 13:26, Carlos E. R. wrote:
On 2018-02-06 11:33, Markus Koßmann wrote:
Am Dienstag, 6. Februar 2018, 01:56:53 CET schrieb Carlos E. R.:
Hi
Can't build the vmware modules, some compile errors. I did not expect this after upgrading from Leap 42.2 to Leap 42.3, the kernel is not supposed to change that much and 42.3 is supposed to be mature.
You are trying to use vmware-12.5.6, which doesn't support Leap-42.3 because the 42.3 kernel includes some backports from later kernels, which vmware-12.5 isn't aware of. Either upgrade to vmware-14, which officially supports Leap-42.3 or hack the source of vmwares kernel modules as described in henrikw84s post in
Ok, thanks.
As vmware doesn't start, it does not offer to upgrade... I'll try manually.
https://www.vmware.com/products/workstation-player/workstation-player-evalua...
Got version 14.0.0
Installed, run vmplayer, says it wants to update itself to version 14.1.1, and now pops up a message:
Unsupported CPU detected
The host CPU does not support the necessary hardware requirements.
Click Quit to stop installation. If you Ignore this message to proceed with installation, you may not be able to launch virtual machines on this host.
For details, please refer to the following Knowledge Base article: https://kb.vmware.com/kb/51643
WTF?
And when I try to run a machine, I get this:
This host does not support "Intel EPT" hardware assisted MMU virtualization. This host does not support virtualizing real mode. The Intel "VMX Unrestricted Guest" feature is necessary to run this virtual machine on an Intel processor. Module 'CPUIDEarly' power on failed. Failed to start the virtual machine.
WTF?
I have a "6.23.10 "Intel(R) Core(TM)2 Quad CPU Q9550 @ 2.83GHz", it does have virtualization support.
:-//
The link says: +++-.-.-.-.-.-.-.- CPU Requirements for VMware Workstation 14.x (51643) Document Id 51643 Purpose This article lists the CPU requirements for running VMware Workstation Pro/Workstation Player 14.x. Resolution Systems using Processors (CPUs) launched in 2011 or later are supported except: Intel Atom processors based on the 2011 “Bonnell” micro-architecture (e.g. Atom Z670/Z650; Atom N570) Systems using Intel Atom processors based on the 2012 “Saltwell” micro-architecture (e.g. Atom S1200, Atom D2700/D2500, Atom N2800/N2600. Systems using AMD processors based on the “Llano” and “Bobcat” micro-architectures (e.g. code-named “Hondo”, “Ontario”, “Zacate”, “Llano”) In addition, the following are supported: Systems using Intel processors based on the 2010 “Westmere” micro-architecture (e.g. Xeon 5600, Xeon 3600, Core i7-970, Core i7-980, Core i7-990) -.-.-.-.-.-.-.-++- So, what are my alternatives? vmplayer 13 perhaps? Migrate to virtualbox? [...] I have downgraded to version 12 and applied the patch. -- Cheers / Saludos, Carlos E. R. (from 42.2 x86_64 "Malachite" at Telcontar)
Op dinsdag 6 februari 2018 23:07:10 CET schreef Carlos E. R.:
On 2018-02-06 14:09, Carlos E. R. wrote:
On 2018-02-06 13:26, Carlos E. R. wrote:
On 2018-02-06 11:33, Markus Koßmann wrote:
Am Dienstag, 6. Februar 2018, 01:56:53 CET schrieb Carlos E. R.:
Hi
Can't build the vmware modules, some compile errors. I did not expect this after upgrading from Leap 42.2 to Leap 42.3, the kernel is not supposed to change that much and 42.3 is supposed to be mature.
You are trying to use vmware-12.5.6, which doesn't support Leap-42.3 because the 42.3 kernel includes some backports from later kernels, which vmware-12.5 isn't aware of. Either upgrade to vmware-14, which officially supports Leap-42.3 or hack the source of vmwares kernel modules as described in henrikw84s post in
Ok, thanks.
As vmware doesn't start, it does not offer to upgrade... I'll try manually.
<https://www.vmware.com/products/workstation-player/workstation-player-ev aluation.html>
Got version 14.0.0
Installed, run vmplayer, says it wants to update itself to version
14.1.1, and now pops up a message: Unsupported CPU detected
The host CPU does not support the necessary hardware requirements.
Click Quit to stop installation. If you Ignore this message to proceed with installation, you may not
be able to launch virtual machines on this host.
For details, please refer to the following Knowledge Base article: https://kb.vmware.com/kb/51643
WTF?
And when I try to run a machine, I get this: This host does not support "Intel EPT" hardware assisted MMU
virtualization.
This host does not support virtualizing real mode. The Intel "VMX
Unrestricted Guest" feature is necessary to run this virtual machine on an Intel processor.
Module 'CPUIDEarly' power on failed. Failed to start the virtual machine.
WTF?
I have a "6.23.10 "Intel(R) Core(TM)2 Quad CPU Q9550 @ 2.83GHz", it does have virtualization support.
:-//
The link says:
+++-.-.-.-.-.-.-.- CPU Requirements for VMware Workstation 14.x (51643) Document Id 51643 Purpose This article lists the CPU requirements for running VMware Workstation Pro/Workstation Player 14.x. Resolution Systems using Processors (CPUs) launched in 2011 or later are supported except:
Intel Atom processors based on the 2011 “Bonnell” micro-architecture (e.g. Atom Z670/Z650; Atom N570) Systems using Intel Atom processors based on the 2012 “Saltwell” micro-architecture (e.g. Atom S1200, Atom D2700/D2500, Atom N2800/N2600. Systems using AMD processors based on the “Llano” and “Bobcat” micro-architectures (e.g. code-named “Hondo”, “Ontario”, “Zacate”, “Llano”)
In addition, the following are supported:
Systems using Intel processors based on the 2010 “Westmere” micro-architecture (e.g. Xeon 5600, Xeon 3600, Core i7-970, Core i7-980, Core i7-990)
-.-.-.-.-.-.-.-++-
So, what are my alternatives? vmplayer 13 perhaps? Migrate to virtualbox?,
A good alternative, yes. It can import your vmware VM's
[...]
I have downgraded to version 12 and applied the patch.
-- Gertjan Lettink, a.k.a. Knurpht openSUSE Board Member openSUSE Forums Team Linux user #548252 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2018-02-07 02:49, Knurpht - Gertjan Lettink wrote:
Op dinsdag 6 februari 2018 23:07:10 CET schreef Carlos E. R.:
So, what are my alternatives? vmplayer 13 perhaps? Migrate to virtualbox?,
A good alternative, yes. It can import your vmware VM's
I'll go that route, but at least now I have some time. Let's hope that VB doesn't kill support for older processors as well...
[...]
I have downgraded to version 12 and applied the patch.
-- Cheers / Saludos, Carlos E. R. (from 42.2 x86_64 "Malachite" at Telcontar)
On 2018-02-06 11:33, Markus Koßmann wrote:
Am Dienstag, 6. Februar 2018, 01:56:53 CET schrieb Carlos E. R.:
Hi
Can't build the vmware modules, some compile errors. I did not expect this after upgrading from Leap 42.2 to Leap 42.3, the kernel is not supposed to change that much and 42.3 is supposed to be mature.
You are trying to use vmware-12.5.6, which doesn't support Leap-42.3 because the 42.3 kernel includes some backports from later kernels, which vmware-12.5 isn't aware of. Either upgrade to vmware-14, which officially supports Leap-42.3 or hack the source of vmwares kernel modules as described in henrikw84s post in
I had to go the second route, vmware-14 refuses to run on my processor, it is to old for them. I will have to migrate to virtualbox. Meanwhile I have downgraded to vmware-12 again and applied the patch - which is not a patch in the typical fashion, but instructions to edit yourself the source code and build it. vmware player does start, and I could run a machine. It did seem a bit slower, but I have no way to know for sure. Is that possible? patch (linked from a post in the other thread linked above): https://communities.vmware.com/message/2693257#2693257 Note: To be able to downgrade to vmware 12 when 14 was installed, I had to remove it manually: Telcontar:~ # vmware-installer -l Product Name Product Version ==================== ==================== vmware-player 14.1.1.7528167 Telcontar:~ # vmware-installer -u vmware-player -- Cheers / Saludos, Carlos E. R. (from 42.2 x86_64 "Malachite" at Telcontar)
participants (5)
-
Andrei Borzenkov -
Carlos E. R. -
Knurpht - Gertjan Lettink -
Markus Koßmann -
Per Jessen