[opensuse-factory] [SOLVED] Installing VMware Workstation 7.1.4 on openSUSE 12.1
Hello I managed to install VMware-Workstation-7.1.4-385536.i386.bundle on openSUSE 12.1 so I thought that I would share it here in a "How To" form. My Factory install was updated today and I was getting "Failed to compile module vmmon!" | "Unable to install vmmon" error messages (see below) when I tried to manually compile the vmware modules. OS Information OS: Linux 3.0.0-rc7-2-desktop i686 System: openSUSE 12.1 (i586) KDE: 4.7.00 (4.7.0) # installed packages kernel-source-3.0.rc7-2.1.noarch kernel-desktop-devel-3.0.rc7-2.1.i586 kernel-default-3.0.0-2.4.i586 kernel-default-devel-3.0.rc7-2.1.i586 kernel-desktop-3.0.rc7-2.1.i586 kernel-firmware-20110709-8.1.noarch kernel-devel-3.0.rc7-2.1.noarch gcc-4.6-14.2.i586 make-3.82-144.3.i586 gcc-c++-4.6-14.2.i586 # Error message # "vmware-modconfig" command log M3A78:~ # vmware-modconfig --console --install-all Stopping VMware services: VMware USB Arbitrator done VM communication interface socket family done Virtual machine communication interface done Virtual machine monitor done Blocking file system done Using 2.6.x kernel build system. make: Entering directory `/tmp/vmware-root/modules/vmmon-only' make -C /lib/modules/3.0.0-rc7-2-desktop/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. \ MODULEBUILDDIR= modules make[1]: Entering directory `/usr/src/linux-3.0.0-rc7-2-obj/i386/desktop' make -C ../../../linux-3.0.0-rc7-2 O=/usr/src/linux-3.0.0-rc7-2-obj/i386/desktop/. modules CC [M] /tmp/vmware-root/modules/vmmon-only/linux/driverLog.o CC [M] /tmp/vmware-root/modules/vmmon-only/linux/iommu.o /tmp/vmware-root/modules/vmmon-only/linux/iommu.c:47:44: error: ‘SPIN_LOCK_UNLOCKED’ undeclared here (not in a function) /tmp/vmware-root/modules/vmmon-only/linux/iommu.c: In function ‘IOMMU_SetupMMU’: /tmp/vmware-root/modules/vmmon-only/linux/iommu.c:103:28: warning: cast from pointer to integer of different size [-Wpointer-to-int-cast] /tmp/vmware-root/modules/vmmon-only/linux/iommu.c:113:17: warning: format ‘%lx’ expects argument of type ‘long unsigned int’, but argument 3 has type ‘long long unsigned int’ [-Wformat] /tmp/vmware-root/modules/vmmon-only/linux/iommu.c:117:35: warning: cast to pointer from integer of different size [-Wint-to-pointer-cast] /tmp/vmware-root/modules/vmmon-only/linux/iommu.c:120:20: warning: format ‘%lu’ expects argument of type ‘long unsigned int’, but argument 3 has type ‘uint64’ [-Wformat] make[4]: *** [/tmp/vmware-root/modules/vmmon-only/linux/iommu.o] Error 1 make[3]: *** [_module_/tmp/vmware-root/modules/vmmon-only] Error 2 make[2]: *** [sub-make] Error 2 make[1]: *** [all] Error 2 make[1]: Leaving directory `/usr/src/linux-3.0.0-rc7-2-obj/i386/desktop' make: *** [vmmon.ko] Error 2 make: Leaving directory `/tmp/vmware-root/modules/vmmon-only' Unable to install vmmon # Solution I googled and found a solution by making a patch "The patch is made extracting all packages in a folder and doing a diff between the clean packages and the edited ones extracted that way. The patches are based on 7.1.4 sources" $ mkdir /tmp/vmware && cd /tmp/vmware $ cp -R /usr/lib/vmware/modules/source/ . $ cd /tmp/vmware/source $ wget http://weltall.heliohost.org/wordpress/wp-content/uploads/2011/05/vmware2.6.... # if the link above does not work, an alternative is to wget http://kaslit.com/downloads/vmware2.6.39fixed.patch $ for i in ./*.tar; do tar -xf $i; done $ for i in ./*.tar; do mv $i $i.orginal; done $ patch –batch –force -p1 < vmware2.6.39fixed.patch $ tar cf vmblock.tar vmblock-only $ tar cf vmci.tar vmci-only $ tar cf vmmon.tar vmmon-only $ tar cf vmnet.tar vmnet-only $ tar cf vsock.tar vsock-only $ cp -vf *.tar /usr/lib/vmware/modules/source/ ########### # Start ########### mkdir /tmp/vmware && cd /tmp/vmware cp -R /usr/lib/vmware/modules/source/ . M3A78:/tmp/vmware # ls -trl total 4 drwxr-xr-x 2 root root 4096 Aug 26 11:59 source cd /tmp/vmware/source wget http://weltall.heliohost.org/wordpress/wp-content/uploads/2011/05/vmware2.6.... M3A78:/tmp/vmware/source # ls -trl total 4448 -rw-r--r-- 1 root root 9536 May 14 20:05 vmware2.6.39fixed.patch -rw-r--r-- 1 root root 942080 Aug 26 11:59 vsock.tar -rw-r--r-- 1 root root 757760 Aug 26 11:59 vmblock.tar -rw-r--r-- 1 root root 870400 Aug 26 11:59 vmnet.tar -rw-r--r-- 1 root root 1177600 Aug 26 11:59 vmmon.tar -rw-r--r-- 1 root root 788480 Aug 26 11:59 vmci.tar for i in ./*.tar; do tar -xf $i; done M3A78:/tmp/vmware/source # for i in ./*.tar; do tar -xf $i; done M3A78:/tmp/vmware/source # ls -trl total 4468 drwxr-xr-x 7 root root 4096 Mar 26 06:02 vmmon-only drwxr-xr-x 2 root root 4096 Mar 26 06:02 vmnet-only drwxr-xr-x 6 root root 4096 Mar 26 06:02 vmci-only drwxr-xr-x 4 root root 4096 Mar 26 06:02 vmblock-only drwxr-xr-x 4 root root 4096 Mar 26 06:02 vsock-only -rw-r--r-- 1 root root 9536 May 14 20:05 vmware2.6.39fixed.patch -rw-r--r-- 1 root root 942080 Aug 26 11:59 vsock.tar -rw-r--r-- 1 root root 757760 Aug 26 11:59 vmblock.tar -rw-r--r-- 1 root root 870400 Aug 26 11:59 vmnet.tar -rw-r--r-- 1 root root 1177600 Aug 26 11:59 vmmon.tar -rw-r--r-- 1 root root 788480 Aug 26 11:59 vmci.tar for i in ./*.tar; do mv $i $i.orginal; done M3A78:/tmp/vmware/source # for i in ./*.tar; do mv $i $i.orginal; done M3A78:/tmp/vmware/source # ls -trl total 4468 drwxr-xr-x 7 root root 4096 Mar 26 06:02 vmmon-only drwxr-xr-x 2 root root 4096 Mar 26 06:02 vmnet-only drwxr-xr-x 6 root root 4096 Mar 26 06:02 vmci-only drwxr-xr-x 4 root root 4096 Mar 26 06:02 vmblock-only drwxr-xr-x 4 root root 4096 Mar 26 06:02 vsock-only -rw-r--r-- 1 root root 9536 May 14 20:05 vmware2.6.39fixed.patch -rw-r--r-- 1 root root 942080 Aug 26 11:59 vsock.tar.orginal -rw-r--r-- 1 root root 757760 Aug 26 11:59 vmblock.tar.orginal -rw-r--r-- 1 root root 870400 Aug 26 11:59 vmnet.tar.orginal -rw-r--r-- 1 root root 1177600 Aug 26 11:59 vmmon.tar.orginal -rw-r--r-- 1 root root 788480 Aug 26 11:59 vmci.tar.orginal -rw-r--r-- 1 root root 9536 May 14 20:05 vmware2.6.39fixed.patch -rw-r--r-- 1 root root 942080 Aug 26 11:59 vsock.tar.orginal -rw-r--r-- 1 root root 757760 Aug 26 11:59 vmblock.tar.orginal -rw-r--r-- 1 root root 870400 Aug 26 11:59 vmnet.tar.orginal -rw-r--r-- 1 root root 1177600 Aug 26 11:59 vmmon.tar.orginal -rw-r--r-- 1 root root 788480 Aug 26 11:59 vmci.tar.orginal ls -trl /tmp/vmware/source/vmware2.6.39fixed.patch patch -t -f -p1 < /tmp/vmware/source/vmware2.6.39fixed.patch M3A78:/tmp/vmware/source # patch -t -f -p1 < /tmp/vmware/source/vmware2.6.39fixed.patch patching file vmblock-only/linux/dentry.c patching file vmblock-only/linux/filesystem.c patching file vmblock-only/linux/module.c patching file vmci-only/linux/driver.c patching file vmmon-only/linux/driver.c patching file vmmon-only/linux/hostif.c patching file vmmon-only/linux/iommu.c patching file vmnet-only/driver.c patching file vmnet-only/filter.c patching file vmnet-only/hub.c patching file vsock-only/linux/af_vsock.c patching file vsock-only/linux/util.c tar cf vmblock.tar vmblock-only tar cf vmci.tar vmci-only tar cf vmmon.tar vmmon-only tar cf vmnet.tar vmnet-only tar cf vsock.tar vsock-only cp -vf *.tar /usr/lib/vmware/modules/source/ Tried to compile Vmwareworkstation manually again vmware-modconfig --console --install-all M3A78:/tmp/vmware/source # vmware-modconfig --console --install-all Stopping VMware services: VMware USB Arbitrator done VM communication interface socket family done Virtual machine communication interface done Virtual machine monitor done Blocking file system done Using 2.6.x kernel build system. make: Entering directory `/tmp/vmware-root/modules/vmmon-only' make -C /lib/modules/3.0.0-rc7-2-desktop/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. \ MODULEBUILDDIR= modules make[1]: Entering directory `/usr/src/linux-3.0.0-rc7-2-obj/i386/desktop' make -C ../../../linux-3.0.0-rc7-2 O=/usr/src/linux-3.0.0-rc7-2-obj/i386/desktop/. modules CC [M] /tmp/vmware-root/modules/vmmon-only/linux/driverLog.o CC [M] /tmp/vmware-root/modules/vmmon-only/linux/iommu.o /tmp/vmware-root/modules/vmmon-only/linux/iommu.c: In function ‘IOMMU_SetupMMU’: /tmp/vmware-root/modules/vmmon-only/linux/iommu.c:103:28: warning: cast from pointer to integer of different size [-Wpointer-to-int-cast] /tmp/vmware-root/modules/vmmon-only/linux/iommu.c:113:17: warning: format ‘%lx’ expects argument of type ‘long unsigned int’, but argument 3 has type ‘long long unsigned int’ [-Wformat] /tmp/vmware-root/modules/vmmon-only/linux/iommu.c:117:35: warning: cast to pointer from integer of different size [-Wint-to-pointer-cast] /tmp/vmware-root/modules/vmmon-only/linux/iommu.c:120:20: warning: format ‘%lu’ expects argument of type ‘long unsigned int’, but argument 3 has type ‘uint64’ [-Wformat] CC [M] /tmp/vmware-root/modules/vmmon-only/linux/driver.o CC [M] /tmp/vmware-root/modules/vmmon-only/linux/hostif.o /tmp/vmware-root/modules/vmmon-only/linux/hostif.c: In function ‘HostIFReadUptimeWork’: /tmp/vmware-root/modules/vmmon-only/linux/hostif.c:2048:10: warning: ‘newUpBase’ may be used uninitialized in this function [-Wuninitialized] CC [M] /tmp/vmware-root/modules/vmmon-only/common/memtrack.o CC [M] /tmp/vmware-root/modules/vmmon-only/common/hashFunc.o CC [M] /tmp/vmware-root/modules/vmmon-only/common/vmx86.o CC [M] /tmp/vmware-root/modules/vmmon-only/common/cpuid.o CC [M] /tmp/vmware-root/modules/vmmon-only/common/task.o CC [M] /tmp/vmware-root/modules/vmmon-only/common/comport.o CC [M] /tmp/vmware-root/modules/vmmon-only/common/phystrack.o CC [M] /tmp/vmware-root/modules/vmmon-only/vmcore/moduleloop.o LD [M] /tmp/vmware-root/modules/vmmon-only/vmmon.o Building modules, stage 2. MODPOST 1 modules CC /tmp/vmware-root/modules/vmmon-only/vmmon.mod.o LD [M] /tmp/vmware-root/modules/vmmon-only/vmmon.ko make[1]: Leaving directory `/usr/src/linux-3.0.0-rc7-2-obj/i386/desktop' make -C $PWD SRCROOT=$PWD/. \ MODULEBUILDDIR= postbuild make[1]: Entering directory `/tmp/vmware-root/modules/vmmon-only' make[1]: `postbuild' is up to date. make[1]: Leaving directory `/tmp/vmware-root/modules/vmmon-only' cp -f vmmon.ko ./../vmmon.o make: Leaving directory `/tmp/vmware-root/modules/vmmon-only' Built vmmon module Using 2.6.x kernel build system. make: Entering directory `/tmp/vmware-root/modules/vmnet-only' make -C /lib/modules/3.0.0-rc7-2-desktop/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. \ MODULEBUILDDIR= modules make[1]: Entering directory `/usr/src/linux-3.0.0-rc7-2-obj/i386/desktop' make -C ../../../linux-3.0.0-rc7-2 O=/usr/src/linux-3.0.0-rc7-2-obj/i386/desktop/. modules CC [M] /tmp/vmware-root/modules/vmnet-only/driver.o CC [M] /tmp/vmware-root/modules/vmnet-only/hub.o CC [M] /tmp/vmware-root/modules/vmnet-only/userif.o CC [M] /tmp/vmware-root/modules/vmnet-only/netif.o CC [M] /tmp/vmware-root/modules/vmnet-only/bridge.o CC [M] /tmp/vmware-root/modules/vmnet-only/filter.o CC [M] /tmp/vmware-root/modules/vmnet-only/procfs.o CC [M] /tmp/vmware-root/modules/vmnet-only/smac_compat.o CC [M] /tmp/vmware-root/modules/vmnet-only/smac.o CC [M] /tmp/vmware-root/modules/vmnet-only/vnetEvent.o CC [M] /tmp/vmware-root/modules/vmnet-only/vnetUserListener.o LD [M] /tmp/vmware-root/modules/vmnet-only/vmnet.o Building modules, stage 2. MODPOST 1 modules CC /tmp/vmware-root/modules/vmnet-only/vmnet.mod.o LD [M] /tmp/vmware-root/modules/vmnet-only/vmnet.ko make[1]: Leaving directory `/usr/src/linux-3.0.0-rc7-2-obj/i386/desktop' make -C $PWD SRCROOT=$PWD/. \ MODULEBUILDDIR= postbuild make[1]: Entering directory `/tmp/vmware-root/modules/vmnet-only' make[1]: `postbuild' is up to date. make[1]: Leaving directory `/tmp/vmware-root/modules/vmnet-only' cp -f vmnet.ko ./../vmnet.o make: Leaving directory `/tmp/vmware-root/modules/vmnet-only' Built vmnet module Using 2.6.x kernel build system. make: Entering directory `/tmp/vmware-root/modules/vmblock-only' make -C /lib/modules/3.0.0-rc7-2-desktop/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. \ MODULEBUILDDIR= modules make[1]: Entering directory `/usr/src/linux-3.0.0-rc7-2-obj/i386/desktop' make -C ../../../linux-3.0.0-rc7-2 O=/usr/src/linux-3.0.0-rc7-2-obj/i386/desktop/. modules CC [M] /tmp/vmware-root/modules/vmblock-only/linux/dbllnklst.o CC [M] /tmp/vmware-root/modules/vmblock-only/linux/dentry.o /tmp/vmware-root/modules/vmblock-only/linux/dentry.c: In function ‘DentryOpRevalidate’: /tmp/vmware-root/modules/vmblock-only/linux/dentry.c:107:4: warning: passing argument 3 of ‘kern_path’ from incompatible pointer type [enabled by default] /usr/src/linux-3.0.0-rc7-2/include/linux/namei.h:76:12: note: expected ‘struct path *’ but argument is of type ‘struct nameidata *’ CC [M] /tmp/vmware-root/modules/vmblock-only/linux/file.o CC [M] /tmp/vmware-root/modules/vmblock-only/linux/block.o CC [M] /tmp/vmware-root/modules/vmblock-only/linux/inode.o CC [M] /tmp/vmware-root/modules/vmblock-only/linux/super.o CC [M] /tmp/vmware-root/modules/vmblock-only/linux/filesystem.o /tmp/vmware-root/modules/vmblock-only/linux/filesystem.c: In function ‘Iget’: /tmp/vmware-root/modules/vmblock-only/linux/filesystem.c:348:4: warning: passing argument 3 of ‘kern_path’ from incompatible pointer type [enabled by default] /usr/src/linux-3.0.0-rc7-2/include/linux/namei.h:76:12: note: expected ‘struct path *’ but argument is of type ‘struct nameidata *’ CC [M] /tmp/vmware-root/modules/vmblock-only/linux/module.o CC [M] /tmp/vmware-root/modules/vmblock-only/linux/stubs.o CC [M] /tmp/vmware-root/modules/vmblock-only/linux/control.o LD [M] /tmp/vmware-root/modules/vmblock-only/vmblock.o Building modules, stage 2. MODPOST 1 modules CC /tmp/vmware-root/modules/vmblock-only/vmblock.mod.o LD [M] /tmp/vmware-root/modules/vmblock-only/vmblock.ko make[1]: Leaving directory `/usr/src/linux-3.0.0-rc7-2-obj/i386/desktop' make -C $PWD SRCROOT=$PWD/. \ MODULEBUILDDIR= postbuild make[1]: Entering directory `/tmp/vmware-root/modules/vmblock-only' make[1]: `postbuild' is up to date. make[1]: Leaving directory `/tmp/vmware-root/modules/vmblock-only' cp -f vmblock.ko ./../vmblock.o make: Leaving directory `/tmp/vmware-root/modules/vmblock-only' Built vmblock module Using 2.6.x kernel build system. make: Entering directory `/tmp/vmware-root/modules/vmci-only' make -C /lib/modules/3.0.0-rc7-2-desktop/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. \ MODULEBUILDDIR= modules make[1]: Entering directory `/usr/src/linux-3.0.0-rc7-2-obj/i386/desktop' make -C ../../../linux-3.0.0-rc7-2 O=/usr/src/linux-3.0.0-rc7-2-obj/i386/desktop/. modules CC [M] /tmp/vmware-root/modules/vmci-only/linux/driverLog.o CC [M] /tmp/vmware-root/modules/vmci-only/linux/driver.o CC [M] /tmp/vmware-root/modules/vmci-only/linux/vmciKernelIf.o CC [M] /tmp/vmware-root/modules/vmci-only/common/vmciProcess.o CC [M] /tmp/vmware-root/modules/vmci-only/common/vmciDriver.o CC [M] /tmp/vmware-root/modules/vmci-only/common/vmciResource.o CC [M] /tmp/vmware-root/modules/vmci-only/common/vmciContext.o CC [M] /tmp/vmware-root/modules/vmci-only/common/vmciDatagram.o CC [M] /tmp/vmware-root/modules/vmci-only/common/vmciHashtable.o CC [M] /tmp/vmware-root/modules/vmci-only/common/vmciEvent.o CC [M] /tmp/vmware-root/modules/vmci-only/common/vmciQueuePair.o CC [M] /tmp/vmware-root/modules/vmci-only/common/vmciGroup.o CC [M] /tmp/vmware-root/modules/vmci-only/common/vmciDs.o LD [M] /tmp/vmware-root/modules/vmci-only/vmci.o Building modules, stage 2. MODPOST 1 modules CC /tmp/vmware-root/modules/vmci-only/vmci.mod.o LD [M] /tmp/vmware-root/modules/vmci-only/vmci.ko make[1]: Leaving directory `/usr/src/linux-3.0.0-rc7-2-obj/i386/desktop' make -C $PWD SRCROOT=$PWD/. \ MODULEBUILDDIR= postbuild make[1]: Entering directory `/tmp/vmware-root/modules/vmci-only' make[1]: `postbuild' is up to date. make[1]: Leaving directory `/tmp/vmware-root/modules/vmci-only' cp -f vmci.ko ./../vmci.o make: Leaving directory `/tmp/vmware-root/modules/vmci-only' Built vmci module Using 2.6.x kernel build system. make: Entering directory `/tmp/vmware-root/modules/vsock-only' make -C /lib/modules/3.0.0-rc7-2-desktop/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. \ MODULEBUILDDIR= modules make[1]: Entering directory `/usr/src/linux-3.0.0-rc7-2-obj/i386/desktop' make -C ../../../linux-3.0.0-rc7-2 O=/usr/src/linux-3.0.0-rc7-2-obj/i386/desktop/. modules CC [M] /tmp/vmware-root/modules/vsock-only/linux/af_vsock.o CC [M] /tmp/vmware-root/modules/vsock-only/linux/vsockAddr.o CC [M] /tmp/vmware-root/modules/vsock-only/linux/util.o CC [M] /tmp/vmware-root/modules/vsock-only/linux/stats.o CC [M] /tmp/vmware-root/modules/vsock-only/linux/notify.o CC [M] /tmp/vmware-root/modules/vsock-only/driverLog.o LD [M] /tmp/vmware-root/modules/vsock-only/vsock.o Building modules, stage 2. MODPOST 1 modules CC /tmp/vmware-root/modules/vsock-only/vsock.mod.o LD [M] /tmp/vmware-root/modules/vsock-only/vsock.ko make[1]: Leaving directory `/usr/src/linux-3.0.0-rc7-2-obj/i386/desktop' make -C $PWD SRCROOT=$PWD/. \ MODULEBUILDDIR= postbuild make[1]: Entering directory `/tmp/vmware-root/modules/vsock-only' make[1]: `postbuild' is up to date. make[1]: Leaving directory `/tmp/vmware-root/modules/vsock-only' cp -f vsock.ko ./../vsock.o make: Leaving directory `/tmp/vmware-root/modules/vsock-only' Built vsock module Starting VMware services: VMware USB Arbitrator done Virtual machine monitor done Virtual machine communication interface done VM communication interface socket family done Blocking file system done Virtual ethernet done Shared Memory Available done Hope this helps someone. James -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
On Fri, 26 Aug 2011 12:33:30 +0200 pearson44j <pearson44j@wanadoo.fr> wrote:
Hello
I managed to install VMware-Workstation-7.1.4-385536.i386.bundle on openSUSE 12.1 so I thought that I would share it here in a "How To" form.
My Factory install was updated today and I was getting "Failed to compile module vmmon!" | "Unable to install vmmon" error messages (see below) when I tried to manually compile the vmware modules.
OS Information OS: Linux 3.0.0-rc7-2-desktop i686 System: openSUSE 12.1 (i586) KDE: 4.7.00 (4.7.0) Hi You should look at updating the SDB article I started with this; http://en.opensuse.org/SDB:Installing_VMware_server_or_workstation
-- Cheers Malcolm °¿° (Linux Counter #276890) openSUSE 11.4 (x86_64) Kernel 2.6.37.6-0.7-desktop up 2 days 23:01, 3 users, load average: 0.16, 0.25, 0.17 GPU GeForce 8600 GTS Silent - Driver Version: 280.13 -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
Hello, I used the same patch with 12.1 Milestone 1 and with Milestone 3. You can use the script patch-modules_2.6.39.sh from the website you mentioned to apply the patch. But, that's not all. If you try to start vmware you will receive the following error: process 31673: Attempt to remove filter function 0x7ff3fbdd0f50 user data 0x8d17c0, but no such filter has been added D-Bus not built with -rdynamic so unable to print a backtrace This can be avoided by starting haldaemon: /etc/init.d/haldaemon start Then you can start vmware. I'm able to create, delete and modify virtual machines. But I'm able to start a virtual machine. Starting a virtual machine always fails with the error: *** VMware Workstation internal monitor error *** vcpu-0:ASSERT vmcore/vmm/main/irq.c:100 bugNr=2293 Haven't found a solution for this one. Bye, viele gruesse aus der physik in wuerzburg, andreas klein From: pearson44j <pearson44j@wanadoo.fr> To: opensuse-factory@opensuse.org Date: 08/26/2011 12:33 PM Subject: [opensuse-factory] [SOLVED] Installing VMware Workstation 7.1.4 on openSUSE 12.1 Hello I managed to install VMware-Workstation-7.1.4-385536.i386.bundle on openSUSE 12.1 so I thought that I would share it here in a "How To" form. My Factory install was updated today and I was getting "Failed to compile module vmmon!" | "Unable to install vmmon" error messages (see below) when I tried to manually compile the vmware modules. OS Information OS: Linux 3.0.0-rc7-2-desktop i686 System: openSUSE 12.1 (i586) KDE: 4.7.00 (4.7.0) # installed packages kernel-source-3.0.rc7-2.1.noarch kernel-desktop-devel-3.0.rc7-2.1.i586 kernel-default-3.0.0-2.4.i586 kernel-default-devel-3.0.rc7-2.1.i586 kernel-desktop-3.0.rc7-2.1.i586 kernel-firmware-20110709-8.1.noarch kernel-devel-3.0.rc7-2.1.noarch gcc-4.6-14.2.i586 make-3.82-144.3.i586 gcc-c++-4.6-14.2.i586 # Error message # "vmware-modconfig" command log M3A78:~ # vmware-modconfig --console --install-all Stopping VMware services: VMware USB Arbitrator done VM communication interface socket family done Virtual machine communication interface done Virtual machine monitor done Blocking file system done Using 2.6.x kernel build system. make: Entering directory `/tmp/vmware-root/modules/vmmon-only' make -C /lib/modules/3.0.0-rc7-2-desktop/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. \ MODULEBUILDDIR= modules make[1]: Entering directory `/usr/src/linux-3.0.0-rc7-2-obj/i386/desktop' make -C ../../../linux-3.0.0-rc7-2 O=/usr/src/linux-3.0.0-rc7-2-obj/i386/desktop/. modules CC [M] /tmp/vmware-root/modules/vmmon-only/linux/driverLog.o CC [M] /tmp/vmware-root/modules/vmmon-only/linux/iommu.o /tmp/vmware-root/modules/vmmon-only/linux/iommu.c:47:44: error: ?SPIN_LOCK_UNLOCKED? undeclared here (not in a function) /tmp/vmware-root/modules/vmmon-only/linux/iommu.c: In function ?IOMMU_SetupMMU?: /tmp/vmware-root/modules/vmmon-only/linux/iommu.c:103:28: warning: cast from pointer to integer of different size [-Wpointer-to-int-cast] /tmp/vmware-root/modules/vmmon-only/linux/iommu.c:113:17: warning: format ?%lx? expects argument of type ?long unsigned int?, but argument 3 has type ?long long unsigned int? [-Wformat] /tmp/vmware-root/modules/vmmon-only/linux/iommu.c:117:35: warning: cast to pointer from integer of different size [-Wint-to-pointer-cast] /tmp/vmware-root/modules/vmmon-only/linux/iommu.c:120:20: warning: format ?%lu? expects argument of type ?long unsigned int?, but argument 3 has type ?uint64? [-Wformat] make[4]: *** [/tmp/vmware-root/modules/vmmon-only/linux/iommu.o] Error 1 make[3]: *** [_module_/tmp/vmware-root/modules/vmmon-only] Error 2 make[2]: *** [sub-make] Error 2 make[1]: *** [all] Error 2 make[1]: Leaving directory `/usr/src/linux-3.0.0-rc7-2-obj/i386/desktop' make: *** [vmmon.ko] Error 2 make: Leaving directory `/tmp/vmware-root/modules/vmmon-only' Unable to install vmmon # Solution I googled and found a solution by making a patch "The patch is made extracting all packages in a folder and doing a diff between the clean packages and the edited ones extracted that way. The patches are based on 7.1.4 sources" $ mkdir /tmp/vmware && cd /tmp/vmware $ cp -R /usr/lib/vmware/modules/source/ . $ cd /tmp/vmware/source $ wget http://weltall.heliohost.org/wordpress/wp-content/uploads/2011/05/vmware2.6.... # if the link above does not work, an alternative is to wget http://kaslit.com/downloads/vmware2.6.39fixed.patch $ for i in ./*.tar; do tar -xf $i; done $ for i in ./*.tar; do mv $i $i.orginal; done $ patch ?batch ?force -p1 < vmware2.6.39fixed.patch $ tar cf vmblock.tar vmblock-only $ tar cf vmci.tar vmci-only $ tar cf vmmon.tar vmmon-only $ tar cf vmnet.tar vmnet-only $ tar cf vsock.tar vsock-only $ cp -vf *.tar /usr/lib/vmware/modules/source/ ########### # Start ########### mkdir /tmp/vmware && cd /tmp/vmware cp -R /usr/lib/vmware/modules/source/ . M3A78:/tmp/vmware # ls -trl total 4 drwxr-xr-x 2 root root 4096 Aug 26 11:59 source cd /tmp/vmware/source wget http://weltall.heliohost.org/wordpress/wp-content/uploads/2011/05/vmware2.6.... M3A78:/tmp/vmware/source # ls -trl total 4448 -rw-r--r-- 1 root root 9536 May 14 20:05 vmware2.6.39fixed.patch -rw-r--r-- 1 root root 942080 Aug 26 11:59 vsock.tar -rw-r--r-- 1 root root 757760 Aug 26 11:59 vmblock.tar -rw-r--r-- 1 root root 870400 Aug 26 11:59 vmnet.tar -rw-r--r-- 1 root root 1177600 Aug 26 11:59 vmmon.tar -rw-r--r-- 1 root root 788480 Aug 26 11:59 vmci.tar for i in ./*.tar; do tar -xf $i; done M3A78:/tmp/vmware/source # for i in ./*.tar; do tar -xf $i; done M3A78:/tmp/vmware/source # ls -trl total 4468 drwxr-xr-x 7 root root 4096 Mar 26 06:02 vmmon-only drwxr-xr-x 2 root root 4096 Mar 26 06:02 vmnet-only drwxr-xr-x 6 root root 4096 Mar 26 06:02 vmci-only drwxr-xr-x 4 root root 4096 Mar 26 06:02 vmblock-only drwxr-xr-x 4 root root 4096 Mar 26 06:02 vsock-only -rw-r--r-- 1 root root 9536 May 14 20:05 vmware2.6.39fixed.patch -rw-r--r-- 1 root root 942080 Aug 26 11:59 vsock.tar -rw-r--r-- 1 root root 757760 Aug 26 11:59 vmblock.tar -rw-r--r-- 1 root root 870400 Aug 26 11:59 vmnet.tar -rw-r--r-- 1 root root 1177600 Aug 26 11:59 vmmon.tar -rw-r--r-- 1 root root 788480 Aug 26 11:59 vmci.tar for i in ./*.tar; do mv $i $i.orginal; done M3A78:/tmp/vmware/source # for i in ./*.tar; do mv $i $i.orginal; done M3A78:/tmp/vmware/source # ls -trl total 4468 drwxr-xr-x 7 root root 4096 Mar 26 06:02 vmmon-only drwxr-xr-x 2 root root 4096 Mar 26 06:02 vmnet-only drwxr-xr-x 6 root root 4096 Mar 26 06:02 vmci-only drwxr-xr-x 4 root root 4096 Mar 26 06:02 vmblock-only drwxr-xr-x 4 root root 4096 Mar 26 06:02 vsock-only -rw-r--r-- 1 root root 9536 May 14 20:05 vmware2.6.39fixed.patch -rw-r--r-- 1 root root 942080 Aug 26 11:59 vsock.tar.orginal -rw-r--r-- 1 root root 757760 Aug 26 11:59 vmblock.tar.orginal -rw-r--r-- 1 root root 870400 Aug 26 11:59 vmnet.tar.orginal -rw-r--r-- 1 root root 1177600 Aug 26 11:59 vmmon.tar.orginal -rw-r--r-- 1 root root 788480 Aug 26 11:59 vmci.tar.orginal -rw-r--r-- 1 root root 9536 May 14 20:05 vmware2.6.39fixed.patch -rw-r--r-- 1 root root 942080 Aug 26 11:59 vsock.tar.orginal -rw-r--r-- 1 root root 757760 Aug 26 11:59 vmblock.tar.orginal -rw-r--r-- 1 root root 870400 Aug 26 11:59 vmnet.tar.orginal -rw-r--r-- 1 root root 1177600 Aug 26 11:59 vmmon.tar.orginal -rw-r--r-- 1 root root 788480 Aug 26 11:59 vmci.tar.orginal ls -trl /tmp/vmware/source/vmware2.6.39fixed.patch patch -t -f -p1 < /tmp/vmware/source/vmware2.6.39fixed.patch M3A78:/tmp/vmware/source # patch -t -f -p1 < /tmp/vmware/source/vmware2.6.39fixed.patch patching file vmblock-only/linux/dentry.c patching file vmblock-only/linux/filesystem.c patching file vmblock-only/linux/module.c patching file vmci-only/linux/driver.c patching file vmmon-only/linux/driver.c patching file vmmon-only/linux/hostif.c patching file vmmon-only/linux/iommu.c patching file vmnet-only/driver.c patching file vmnet-only/filter.c patching file vmnet-only/hub.c patching file vsock-only/linux/af_vsock.c patching file vsock-only/linux/util.c tar cf vmblock.tar vmblock-only tar cf vmci.tar vmci-only tar cf vmmon.tar vmmon-only tar cf vmnet.tar vmnet-only tar cf vsock.tar vsock-only cp -vf *.tar /usr/lib/vmware/modules/source/ Tried to compile Vmwareworkstation manually again vmware-modconfig --console --install-all M3A78:/tmp/vmware/source # vmware-modconfig --console --install-all Stopping VMware services: VMware USB Arbitrator done VM communication interface socket family done Virtual machine communication interface done Virtual machine monitor done Blocking file system done Using 2.6.x kernel build system. make: Entering directory `/tmp/vmware-root/modules/vmmon-only' make -C /lib/modules/3.0.0-rc7-2-desktop/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. \ MODULEBUILDDIR= modules make[1]: Entering directory `/usr/src/linux-3.0.0-rc7-2-obj/i386/desktop' make -C ../../../linux-3.0.0-rc7-2 O=/usr/src/linux-3.0.0-rc7-2-obj/i386/desktop/. modules CC [M] /tmp/vmware-root/modules/vmmon-only/linux/driverLog.o CC [M] /tmp/vmware-root/modules/vmmon-only/linux/iommu.o /tmp/vmware-root/modules/vmmon-only/linux/iommu.c: In function ?IOMMU_SetupMMU?: /tmp/vmware-root/modules/vmmon-only/linux/iommu.c:103:28: warning: cast from pointer to integer of different size [-Wpointer-to-int-cast] /tmp/vmware-root/modules/vmmon-only/linux/iommu.c:113:17: warning: format ?%lx? expects argument of type ?long unsigned int?, but argument 3 has type ?long long unsigned int? [-Wformat] /tmp/vmware-root/modules/vmmon-only/linux/iommu.c:117:35: warning: cast to pointer from integer of different size [-Wint-to-pointer-cast] /tmp/vmware-root/modules/vmmon-only/linux/iommu.c:120:20: warning: format ?%lu? expects argument of type ?long unsigned int?, but argument 3 has type ?uint64? [-Wformat] CC [M] /tmp/vmware-root/modules/vmmon-only/linux/driver.o CC [M] /tmp/vmware-root/modules/vmmon-only/linux/hostif.o /tmp/vmware-root/modules/vmmon-only/linux/hostif.c: In function ?HostIFReadUptimeWork?: /tmp/vmware-root/modules/vmmon-only/linux/hostif.c:2048:10: warning: ?newUpBase? may be used uninitialized in this function [-Wuninitialized] CC [M] /tmp/vmware-root/modules/vmmon-only/common/memtrack.o CC [M] /tmp/vmware-root/modules/vmmon-only/common/hashFunc.o CC [M] /tmp/vmware-root/modules/vmmon-only/common/vmx86.o CC [M] /tmp/vmware-root/modules/vmmon-only/common/cpuid.o CC [M] /tmp/vmware-root/modules/vmmon-only/common/task.o CC [M] /tmp/vmware-root/modules/vmmon-only/common/comport.o CC [M] /tmp/vmware-root/modules/vmmon-only/common/phystrack.o CC [M] /tmp/vmware-root/modules/vmmon-only/vmcore/moduleloop.o LD [M] /tmp/vmware-root/modules/vmmon-only/vmmon.o Building modules, stage 2. MODPOST 1 modules CC /tmp/vmware-root/modules/vmmon-only/vmmon.mod.o LD [M] /tmp/vmware-root/modules/vmmon-only/vmmon.ko make[1]: Leaving directory `/usr/src/linux-3.0.0-rc7-2-obj/i386/desktop' make -C $PWD SRCROOT=$PWD/. \ MODULEBUILDDIR= postbuild make[1]: Entering directory `/tmp/vmware-root/modules/vmmon-only' make[1]: `postbuild' is up to date. make[1]: Leaving directory `/tmp/vmware-root/modules/vmmon-only' cp -f vmmon.ko ./../vmmon.o make: Leaving directory `/tmp/vmware-root/modules/vmmon-only' Built vmmon module Using 2.6.x kernel build system. make: Entering directory `/tmp/vmware-root/modules/vmnet-only' make -C /lib/modules/3.0.0-rc7-2-desktop/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. \ MODULEBUILDDIR= modules make[1]: Entering directory `/usr/src/linux-3.0.0-rc7-2-obj/i386/desktop' make -C ../../../linux-3.0.0-rc7-2 O=/usr/src/linux-3.0.0-rc7-2-obj/i386/desktop/. modules CC [M] /tmp/vmware-root/modules/vmnet-only/driver.o CC [M] /tmp/vmware-root/modules/vmnet-only/hub.o CC [M] /tmp/vmware-root/modules/vmnet-only/userif.o CC [M] /tmp/vmware-root/modules/vmnet-only/netif.o CC [M] /tmp/vmware-root/modules/vmnet-only/bridge.o CC [M] /tmp/vmware-root/modules/vmnet-only/filter.o CC [M] /tmp/vmware-root/modules/vmnet-only/procfs.o CC [M] /tmp/vmware-root/modules/vmnet-only/smac_compat.o CC [M] /tmp/vmware-root/modules/vmnet-only/smac.o CC [M] /tmp/vmware-root/modules/vmnet-only/vnetEvent.o CC [M] /tmp/vmware-root/modules/vmnet-only/vnetUserListener.o LD [M] /tmp/vmware-root/modules/vmnet-only/vmnet.o Building modules, stage 2. MODPOST 1 modules CC /tmp/vmware-root/modules/vmnet-only/vmnet.mod.o LD [M] /tmp/vmware-root/modules/vmnet-only/vmnet.ko make[1]: Leaving directory `/usr/src/linux-3.0.0-rc7-2-obj/i386/desktop' make -C $PWD SRCROOT=$PWD/. \ MODULEBUILDDIR= postbuild make[1]: Entering directory `/tmp/vmware-root/modules/vmnet-only' make[1]: `postbuild' is up to date. make[1]: Leaving directory `/tmp/vmware-root/modules/vmnet-only' cp -f vmnet.ko ./../vmnet.o make: Leaving directory `/tmp/vmware-root/modules/vmnet-only' Built vmnet module Using 2.6.x kernel build system. make: Entering directory `/tmp/vmware-root/modules/vmblock-only' make -C /lib/modules/3.0.0-rc7-2-desktop/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. \ MODULEBUILDDIR= modules make[1]: Entering directory `/usr/src/linux-3.0.0-rc7-2-obj/i386/desktop' make -C ../../../linux-3.0.0-rc7-2 O=/usr/src/linux-3.0.0-rc7-2-obj/i386/desktop/. modules CC [M] /tmp/vmware-root/modules/vmblock-only/linux/dbllnklst.o CC [M] /tmp/vmware-root/modules/vmblock-only/linux/dentry.o /tmp/vmware-root/modules/vmblock-only/linux/dentry.c: In function ?DentryOpRevalidate?: /tmp/vmware-root/modules/vmblock-only/linux/dentry.c:107:4: warning: passing argument 3 of ?kern_path? from incompatible pointer type [enabled by default] /usr/src/linux-3.0.0-rc7-2/include/linux/namei.h:76:12: note: expected ?struct path *? but argument is of type ?struct nameidata *? CC [M] /tmp/vmware-root/modules/vmblock-only/linux/file.o CC [M] /tmp/vmware-root/modules/vmblock-only/linux/block.o CC [M] /tmp/vmware-root/modules/vmblock-only/linux/inode.o CC [M] /tmp/vmware-root/modules/vmblock-only/linux/super.o CC [M] /tmp/vmware-root/modules/vmblock-only/linux/filesystem.o /tmp/vmware-root/modules/vmblock-only/linux/filesystem.c: In function ?Iget?: /tmp/vmware-root/modules/vmblock-only/linux/filesystem.c:348:4: warning: passing argument 3 of ?kern_path? from incompatible pointer type [enabled by default] /usr/src/linux-3.0.0-rc7-2/include/linux/namei.h:76:12: note: expected ?struct path *? but argument is of type ?struct nameidata *? CC [M] /tmp/vmware-root/modules/vmblock-only/linux/module.o CC [M] /tmp/vmware-root/modules/vmblock-only/linux/stubs.o CC [M] /tmp/vmware-root/modules/vmblock-only/linux/control.o LD [M] /tmp/vmware-root/modules/vmblock-only/vmblock.o Building modules, stage 2. MODPOST 1 modules CC /tmp/vmware-root/modules/vmblock-only/vmblock.mod.o LD [M] /tmp/vmware-root/modules/vmblock-only/vmblock.ko make[1]: Leaving directory `/usr/src/linux-3.0.0-rc7-2-obj/i386/desktop' make -C $PWD SRCROOT=$PWD/. \ MODULEBUILDDIR= postbuild make[1]: Entering directory `/tmp/vmware-root/modules/vmblock-only' make[1]: `postbuild' is up to date. make[1]: Leaving directory `/tmp/vmware-root/modules/vmblock-only' cp -f vmblock.ko ./../vmblock.o make: Leaving directory `/tmp/vmware-root/modules/vmblock-only' Built vmblock module Using 2.6.x kernel build system. make: Entering directory `/tmp/vmware-root/modules/vmci-only' make -C /lib/modules/3.0.0-rc7-2-desktop/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. \ MODULEBUILDDIR= modules make[1]: Entering directory `/usr/src/linux-3.0.0-rc7-2-obj/i386/desktop' make -C ../../../linux-3.0.0-rc7-2 O=/usr/src/linux-3.0.0-rc7-2-obj/i386/desktop/. modules CC [M] /tmp/vmware-root/modules/vmci-only/linux/driverLog.o CC [M] /tmp/vmware-root/modules/vmci-only/linux/driver.o CC [M] /tmp/vmware-root/modules/vmci-only/linux/vmciKernelIf.o CC [M] /tmp/vmware-root/modules/vmci-only/common/vmciProcess.o CC [M] /tmp/vmware-root/modules/vmci-only/common/vmciDriver.o CC [M] /tmp/vmware-root/modules/vmci-only/common/vmciResource.o CC [M] /tmp/vmware-root/modules/vmci-only/common/vmciContext.o CC [M] /tmp/vmware-root/modules/vmci-only/common/vmciDatagram.o CC [M] /tmp/vmware-root/modules/vmci-only/common/vmciHashtable.o CC [M] /tmp/vmware-root/modules/vmci-only/common/vmciEvent.o CC [M] /tmp/vmware-root/modules/vmci-only/common/vmciQueuePair.o CC [M] /tmp/vmware-root/modules/vmci-only/common/vmciGroup.o CC [M] /tmp/vmware-root/modules/vmci-only/common/vmciDs.o LD [M] /tmp/vmware-root/modules/vmci-only/vmci.o Building modules, stage 2. MODPOST 1 modules CC /tmp/vmware-root/modules/vmci-only/vmci.mod.o LD [M] /tmp/vmware-root/modules/vmci-only/vmci.ko make[1]: Leaving directory `/usr/src/linux-3.0.0-rc7-2-obj/i386/desktop' make -C $PWD SRCROOT=$PWD/. \ MODULEBUILDDIR= postbuild make[1]: Entering directory `/tmp/vmware-root/modules/vmci-only' make[1]: `postbuild' is up to date. make[1]: Leaving directory `/tmp/vmware-root/modules/vmci-only' cp -f vmci.ko ./../vmci.o make: Leaving directory `/tmp/vmware-root/modules/vmci-only' Built vmci module Using 2.6.x kernel build system. make: Entering directory `/tmp/vmware-root/modules/vsock-only' make -C /lib/modules/3.0.0-rc7-2-desktop/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. \ MODULEBUILDDIR= modules make[1]: Entering directory `/usr/src/linux-3.0.0-rc7-2-obj/i386/desktop' make -C ../../../linux-3.0.0-rc7-2 O=/usr/src/linux-3.0.0-rc7-2-obj/i386/desktop/. modules CC [M] /tmp/vmware-root/modules/vsock-only/linux/af_vsock.o CC [M] /tmp/vmware-root/modules/vsock-only/linux/vsockAddr.o CC [M] /tmp/vmware-root/modules/vsock-only/linux/util.o CC [M] /tmp/vmware-root/modules/vsock-only/linux/stats.o CC [M] /tmp/vmware-root/modules/vsock-only/linux/notify.o CC [M] /tmp/vmware-root/modules/vsock-only/driverLog.o LD [M] /tmp/vmware-root/modules/vsock-only/vsock.o Building modules, stage 2. MODPOST 1 modules CC /tmp/vmware-root/modules/vsock-only/vsock.mod.o LD [M] /tmp/vmware-root/modules/vsock-only/vsock.ko make[1]: Leaving directory `/usr/src/linux-3.0.0-rc7-2-obj/i386/desktop' make -C $PWD SRCROOT=$PWD/. \ MODULEBUILDDIR= postbuild make[1]: Entering directory `/tmp/vmware-root/modules/vsock-only' make[1]: `postbuild' is up to date. make[1]: Leaving directory `/tmp/vmware-root/modules/vsock-only' cp -f vsock.ko ./../vsock.o make: Leaving directory `/tmp/vmware-root/modules/vsock-only' Built vsock module Starting VMware services: VMware USB Arbitrator done Virtual machine monitor done Virtual machine communication interface done VM communication interface socket family done Blocking file system done Virtual ethernet done Shared Memory Available done Hope this helps someone. James -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
Hello On Sun, 28 Aug 2011 13:58:46 +0200 Andreas.C.Klein@physik.uni-wuerzburg.de wrote:
Then you can start vmware. I'm able to create, delete and modify virtual machines. But I'm able to start a virtual machine. Starting a virtual machine always fails with the error: *** VMware Workstation internal monitor error *** vcpu-0:ASSERT vmcore/vmm/main/irq.c:100 bugNr=2293
Haven't found a solution for this one.
I googled over the weekend but I have not had the time to follow up on what I found - see "VMware patch for 3.0 kernel" below... It appears that there are 2 patchs "to apply". The first one we both know about. It appears however that there is also another one for the 3.0 kernel "patch3031vmware741.patch" - see details below: wget http://weltall.heliohost.org/wordpress/wp-content/uploads/2011/08/patch3031v... ########################### VMware patch for 3.0 kernel ########################### SOURCE : http://aptosid.com/index.php?name=PNphpBB2&file=viewtopic&t=1629 dibl - 14.08.2011, 19:42 Post subject: VMware patch for 3.0 kernel PM me and I will share the procedure. VMware Player 3.1.4 64-bit is working correctly now on 3.0-x aptosid kernels. kris99 - 15.08.2011, 07:25 Post subject: RE: VMware patch for 3.0 kernel Why don't you share this information in the forum? dibl - 15.08.2011, 13:29 Post subject: Re: RE: VMware patch for 3.0 kernel kris99 wrote: Why don't you share this information in the forum? OK, since you asked. How to patch for kernel 3.0x: 0. Uninstall VMware Player or Workstation, and rm -rf /usr/lib/vmware/modules/source (or if you backed up the original source .tar files, restore them now and delete any patched xxx-only directories) 1. Install VMware Player 3.1.4 or Workstation 7.1x (unless you have restored original source .tar files and deleted the prior xxxx-only directories) 2. Fix the issue with the kernel nomenclature change from 2.6.x to 3.x as follows from the root prompt: # Code: sed 's/\x83\xe8\x03\x83\xf8\x01\x0f\x96\xc0/\x83\xe8\x02\x83\xf8\x01\x0f\x96\xc0/' -i /usr/lib/vmware/lib/libvmware-modconfig-console.so/libvmware-modconfig-console.so # Code: sed 's/\x83\xe8\x03\x83\xf8\x01\x0f\x96\xc0/\x83\xe8\x02\x83\xf8\x01\x0f\x96\xc0/' -i /usr/lib/vmware/lib/libvmware-modconfig.so/libvmware-modconfig.so 3. Download the vmware2.6.39patchv3.tar.bz2 patch from here, extract and untar it (disregard/delete the script "patch-modules_2.6.39.sh" -- we do not use it) 4. Download the patch3031vmware741.patch file (link named "vmware fix for 3.1") from here 5. Open terminal, become root, and change directory to /usr/lib/vmware/modules/source 6. Issue "ls". You should see the following 5 files (and nothing else): Code: vmblock.tar vmci.tar vmmon.tar vmnet.tar vsock.tar 7. Issue Code: for i in ./*.tar; do tar -xvf $i; done to untar the five .tar files. Each one will extract into a new directory with "-only" as the directory name suffix. When you are finished you should have, in addition to the original .tar files, the following new directories: Code: vmblock-only vmci-only vmmon-only vmnet-only vsock-only 8. Back up the original source .tar files with Code: for i in ./*.tar; do mv $i $i.orginal; done 9. Copy both downloaded patch files to the current directory /usr/lib/vmware/modules/source, and "chmod +x ..." each file to make it executable 10. Now issue the command (the character after "-p" is the numeral one, not the letter L) Code: patch -p1 < vmware2.6.39fixedv3.patch It should run to completion with no error output -- this replaces selected files in the -only directories. 11. Next issue the command Code: patch -p1 < patch3031vmware741.patch which patches vmnet-only/compat_netdevice.h and should return no error 12. Next, "tar cvf" all of the files in the vxxx-only subdirectories. So, for example, Code: tar cvf vmblock.tar vmblock-only/* and do this for each vxxx-only directory. 13. You are done -- you can launch VMware Player now and the 3.0 kernel modules will build. When you start a VM, you will see a warning about "this Linux kernel is too new", but it does not affect the running VM. p.s. This is put together from parts found in 3 different locations (Arch forum, VMware forum, & weltall.heliohost.org). Hope this helps James -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
On 08/29/2011 02:20 PM, pearson44j wrote:
13. You are done -- you can launch VMware Player now and the 3.0 kernel modules will build. When you start a VM, you will see a warning about "this Linux kernel is too new", but it does not affect the running VM. p.s. This is put together from parts found in 3 different locations (Arch forum, VMware forum,& weltall.heliohost.org).
Why is there so much work needed for VMware? VirtualBox's kernel module is already patched for kernel 3.1 in their latest release (4.1.2). All one needs is 'make' and 'sudo make install'. Larry -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
On Mon, 29 Aug 2011 14:50:54 -0500 Larry Finger <Larry.Finger@lwfinger.net> wrote:
On 08/29/2011 02:20 PM, pearson44j wrote:
13. You are done -- you can launch VMware Player now and the 3.0 kernel modules will build. When you start a VM, you will see a warning about "this Linux kernel is too new", but it does not affect the running VM. p.s. This is put together from parts found in 3 different locations (Arch forum, VMware forum,& weltall.heliohost.org).
Why is there so much work needed for VMware? VirtualBox's kernel module is already patched for kernel 3.1 in their latest release (4.1.2). All one needs is 'make' and 'sudo make install'.
Larry On Mon, 29 Aug 2011 14:50:54 -0500 Larry Finger <Larry.Finger@lwfinger.net> wrote:
On 08/29/2011 02:20 PM, pearson44j wrote:
13. You are done -- you can launch VMware Player now and the 3.0 kernel modules will build. When you start a VM, you will see a warning about "this Linux kernel is too new", but it does not affect the running VM. p.s. This is put together from parts found in 3 different locations (Arch forum, VMware forum,& weltall.heliohost.org).
Why is there so much work needed for VMware? VirtualBox's kernel module is already patched for kernel 3.1 in their latest release (4.1.2). All one needs is 'make' and 'sudo make install'.
Larry
Hello Your are right - currently it is neither easy or obvious to install VMware Workstation on kernel 3.0. Things change however.... On the other hand, I can think of several (off topic) reasons why I went back to using VMware Workstation - in no particular order: openoffice, java and android. @+ James -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
On 08/29/2011 09:50 PM, Larry Finger wrote:
On 08/29/2011 02:20 PM, pearson44j wrote:
13. You are done -- you can launch VMware Player now and the 3.0 kernel modules will build. When you start a VM, you will see a warning about "this Linux kernel is too new", but it does not affect the running VM. p.s. This is put together from parts found in 3 different locations (Arch forum, VMware forum,& weltall.heliohost.org).
Why is there so much work needed for VMware? VirtualBox's kernel module is already patched for kernel 3.1 in their latest release (4.1.2). All one needs is 'make' and 'sudo make install'.
Larry
It's even better with KVM, all inside the kernel :-) at least now we can have new kind of war, emacs versus vim start to be outdated :D -- Bruno Friedmann Ioda-Net Sàrl www.ioda-net.ch openSUSE Member & Ambassador GPG KEY : D5C9B751C4653227 irc: tigerfoot -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
On 08/30/2011 03:32 PM, Bruno Friedmann wrote:
On 08/29/2011 09:50 PM, Larry Finger wrote:
On 08/29/2011 02:20 PM, pearson44j wrote:
13. You are done -- you can launch VMware Player now and the 3.0 kernel modules will build. When you start a VM, you will see a warning about "this Linux kernel is too new", but it does not affect the running VM. p.s. This is put together from parts found in 3 different locations (Arch forum, VMware forum,& weltall.heliohost.org).
Why is there so much work needed for VMware? VirtualBox's kernel module is already patched for kernel 3.1 in their latest release (4.1.2). All one needs is 'make' and 'sudo make install'.
Larry
It's even better with KVM, all inside the kernel :-)
at least now we can have new kind of war, emacs versus vim start to be outdated :D
Will odd things like Windows XP work in KVM? I need it for 2 apps, but at least it is secure inside Linux. Larry -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
Am Tue, 30 Aug 2011 16:22:40 -0500 schrieb Larry Finger <Larry.Finger@lwfinger.net>:
Will odd things like Windows XP work in KVM?
Yes. Did not encounter a problem since years. -- Stefan Seyfried "Dispatch war rocket Ajax to bring back his body!" -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
Am 08/31/11, schrieb Stefan Seyfried <stefan.seyfried@googlemail.com>:
Am Tue, 30 Aug 2011 16:22:40 -0500 schrieb Larry Finger <Larry.Finger@lwfinger.net>:
Will odd things like Windows XP work in KVM?
Yes. Did not encounter a problem since years.
The only remaining reason (for me) to use VB/VMWare is missing virtualization support on my laptop - Core2 CULV SU4100. Cheers, Stefan -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
On Wed, Aug 31, 2011 at 08:29:42AM +0200, Stefan Seyfried wrote:
Am Tue, 30 Aug 2011 16:22:40 -0500 schrieb Larry Finger <Larry.Finger@lwfinger.net>:
Will odd things like Windows XP work in KVM?
Yes. Did not encounter a problem since years.
Well, depends on how you operate the guest OS. As I like to have it even with multiple guest OSs running reasonable fast I'm used to install the virtio drivers to accelrate network and disk IO. And here it can get hairy. Recently I made good experience with the drivers included with the kvm package as offered for openSUSE. They're packaged as /usr/share/qemu-kvm/win-virtio-drivers.iso One of my Samba colleagues prefers xen. He uses it since several years. And as I'm cheap I consider to run it with one of my older systems which has a lot of memory and multiple CPUs but no hardware virtualization support. Lars -- Lars Müller [ˈlaː(r)z ˈmʏlɐ] Samba Team SUSE Linux, Maxfeldstraße 5, 90409 Nürnberg, Germany
On 08/30/2011 11:22 PM, Larry Finger wrote:
On 08/30/2011 03:32 PM, Bruno Friedmann wrote:
On 08/29/2011 09:50 PM, Larry Finger wrote:
On 08/29/2011 02:20 PM, pearson44j wrote:
13. You are done -- you can launch VMware Player now and the 3.0 kernel modules will build. When you start a VM, you will see a warning about "this Linux kernel is too new", but it does not affect the running VM. p.s. This is put together from parts found in 3 different locations (Arch forum, VMware forum,& weltall.heliohost.org).
Why is there so much work needed for VMware? VirtualBox's kernel module is already patched for kernel 3.1 in their latest release (4.1.2). All one needs is 'make' and 'sudo make install'.
Larry
It's even better with KVM, all inside the kernel :-)
at least now we can have new kind of war, emacs versus vim start to be outdated :D
Will odd things like Windows XP work in KVM? I need it for 2 apps, but at least it is secure inside Linux.
Larry
I've several customers installed with low end server (or beefy workstation) Phenom X6 with plenty of ram and a good disk subsytem like 8 to 10 virtual XP/win7-64 running on. With virtio drivers installed under windows, they run perfectly well from almost 2 years now. -- Bruno Friedmann Ioda-Net Sàrl www.ioda-net.ch openSUSE Member & Ambassador GPG KEY : D5C9B751C4653227 irc: tigerfoot -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
Am Mon, 29 Aug 2011 14:50:54 -0500 schrieb Larry Finger <Larry.Finger@lwfinger.net>:
Why is there so much work needed for VMware? VirtualBox's kernel module is already patched for kernel 3.1 in their latest release (4.1.2). All one needs is 'make' and 'sudo make install'.
But kernel hackers consider VirtualBox "bad" while considering VMware "good". I never quite understood why. The code is probably equally crap and VBox is at least GPL (which VMware is not, IIRC). -- Stefan Seyfried "Dispatch war rocket Ajax to bring back his body!" -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
On Wed, Aug 31, 2011 at 08:28:30AM +0200, Stefan Seyfried wrote:
Am Mon, 29 Aug 2011 14:50:54 -0500 schrieb Larry Finger <Larry.Finger@lwfinger.net>:
Why is there so much work needed for VMware? VirtualBox's kernel module is already patched for kernel 3.1 in their latest release (4.1.2). All one needs is 'make' and 'sudo make install'.
But kernel hackers consider VirtualBox "bad" while considering VMware "good". I never quite understood why. The code is probably equally crap and VBox is at least GPL (which VMware is not, IIRC).
vmware has worked to get their code accepted into the main kernel.org repositories, while virtualbox refuses to get involved at all and the community is tired of seeing bug reports like "virtualbox doesn't compile on the latest kernel" when there is nothing that they can do about that at all. greg k-h -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
On 08/31/2011 10:41 AM, Greg KH wrote:
vmware has worked to get their code accepted into the main kernel.org repositories, while virtualbox refuses to get involved at all and the community is tired of seeing bug reports like "virtualbox doesn't compile on the latest kernel" when there is nothing that they can do about that at all.
Fair enough. That said, I always run VB on the latest kernels. In the 3.0-gitX stage, I found a small change that was needed for 3.1 kernels and sent it upstream to VB even before 3.1-rc1 was released. As I get my VB RPMs from VB and do not use the openSUSE repos, I suspect such changes are not getting into the codebase for most openSUSE users. Is there anything I can do to help? Larry -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
Hi Greg, Am Wed, 31 Aug 2011 08:41:42 -0700 schrieb Greg KH <gregkh@suse.de>:
vmware has worked to get their code accepted into the main kernel.org repositories, while virtualbox refuses to get involved at all and the community is tired of seeing bug reports like "virtualbox doesn't compile on the latest kernel" when there is nothing that they can do about that at all.
So why does vmware apparently not compile with every new kernel that's out there? Not that I'm using it, but every second week someone comes up and asks for help compiling some VMware modules, so there hast to be some problem :-) And apparently at least the latest vbox version is quickly fixed for new kernels. -- Stefan Seyfried "Dispatch war rocket Ajax to bring back his body!" -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
On Wed, Aug 31, 2011 at 07:49:14PM +0200, Stefan Seyfried wrote:
Hi Greg,
Am Wed, 31 Aug 2011 08:41:42 -0700 schrieb Greg KH <gregkh@suse.de>:
vmware has worked to get their code accepted into the main kernel.org repositories, while virtualbox refuses to get involved at all and the community is tired of seeing bug reports like "virtualbox doesn't compile on the latest kernel" when there is nothing that they can do about that at all.
So why does vmware apparently not compile with every new kernel that's out there? Not that I'm using it, but every second week someone comes up and asks for help compiling some VMware modules, so there hast to be some problem :-)
Because they are usually using an old set of the vmware out-of-tree modules for a different vmware product than the most recent one.
And apparently at least the latest vbox version is quickly fixed for new kernels.
Hopefully, but I've seen enough bug reports to know this isn't always the case :( Anyway, I was just trying to explain why the kernel developers like vmware more than virtual box. Oh, then there's the code base itself, don't get me started on what the virtualbox code looks like... thanks, greg k-h -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
On 08/31/2011 08:28 AM, Stefan Seyfried wrote:
Am Mon, 29 Aug 2011 14:50:54 -0500 schrieb Larry Finger <Larry.Finger@lwfinger.net>:
Why is there so much work needed for VMware? VirtualBox's kernel module is already patched for kernel 3.1 in their latest release (4.1.2). All one needs is 'make' and 'sudo make install'.
But kernel hackers consider VirtualBox "bad" while considering VMware "good". I never quite understood why. The code is probably equally crap and VBox is at least GPL (which VMware is not, IIRC).
Saying vbox is gpl is just overlooked, only the base is extract from oracle website The base package consists of all open-source components and is licensed under the GNU General Public License V2. -> So this one yes Additional extension packs can be downloaded which extend the functionality of the VirtualBox base package. Currently, Oracle provides the one extension pack, which can be found at http://www.virtualbox.org and provides the following added functionality: The virtual USB 2.0 (EHCI) device; see the section called “USB settings”. VirtualBox Remote Desktop Protocol (VRDP) support; see the section called “Remote display (VRDP support)”. Intel PXE boot ROM with support for the E1000 network card. Experimental support for PCI passthrough on Linux hosts; see the section called “PCI passthrough”. -> those nobody knows :D For me I've several times look at VB as alternative, to VMWare for example. But the licence never convince me, VMWare is proprio and work well with older kernel/distribution kvm and it's libvirtd companion propose a clear stack about the licence. -- Bruno Friedmann Ioda-Net Sàrl www.ioda-net.ch openSUSE Member & Ambassador GPG KEY : D5C9B751C4653227 irc: tigerfoot -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
Am Wed, 31 Aug 2011 18:08:27 +0200 schrieb Bruno Friedmann <bruno@ioda-net.ch>:
On 08/31/2011 08:28 AM, Stefan Seyfried wrote:
Am Mon, 29 Aug 2011 14:50:54 -0500 schrieb Larry Finger <Larry.Finger@lwfinger.net>:
Why is there so much work needed for VMware? VirtualBox's kernel module is already patched for kernel 3.1 in their latest release (4.1.2). All one needs is 'make' and 'sudo make install'.
But kernel hackers consider VirtualBox "bad" while considering VMware "good". I never quite understood why. The code is probably equally crap and VBox is at least GPL (which VMware is not, IIRC).
Saying vbox is gpl is just overlooked, only the base is
But I never needed anything but the base.
extract from oracle website The base package consists of all open-source components and is licensed under the GNU General Public License V2. -> So this one yes
Additional extension packs can be downloaded which extend the functionality of the VirtualBox base package. Currently, Oracle provides the one extension pack, which can be found at http://www.virtualbox.org and provides the following added functionality:
The virtual USB 2.0 (EHCI) device; see the section called “USB settings”. VirtualBox Remote Desktop Protocol (VRDP) support; see the section called “Remote display (VRDP support)”. Intel PXE boot ROM with support for the E1000 network card. Experimental support for PCI passthrough on Linux hosts; see the section called “PCI passthrough”.
Which I never had a need to use. But I have to admit that I run vbox on a windows host with openSUSE as a guest OS on my managed (by customer's IT) laptop. And for that (linux on Windows host), vbox beats vmware for almost every aspect. And it uses the same virtio drivers like every other virtualization does nowadays. The guest drivers (also GPL) are only needed for the shared folder thing, wich is useful but not essential.
-> those nobody knows :D For me I've several times look at VB as alternative, to VMWare for example. But the licence never convince me, VMWare is proprio and work well with older kernel/distribution
I prefer GPL versus proprietary, especially if the GPL software works better.
kvm and it's libvirtd companion propose a clear stack about the licence.
*If* you have a linux host and a VT capable processor. -- Stefan Seyfried "Dispatch war rocket Ajax to bring back his body!" -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
participants (9)
-
"Stefan Brüns" -
Andreas.C.Klein＠physik.uni-wuerzburg.de -
Bruno Friedmann -
Greg KH -
Larry Finger -
Lars Müller -
Malcolm -
pearson44j -
Stefan Seyfried