[Solved] VMWare Player 4.0.0 and kernel 3.1.4-1-ARCH

Hi,
i followed the instructions here https://wiki.archlinux.org/index.php/VM … n.2FPlayer
while running the modconfig command i get this error.
Stopping VMware services:
VMware Authentication Daemon 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.1.4-1-ARCH/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. \
MODULEBUILDDIR= modules
make[1]: Entering directory `/usr/src/linux-3.1.4-1-ARCH'
CC [M] /tmp/vmware-root/modules/vmmon-only/linux/driver.o
CC [M] /tmp/vmware-root/modules/vmmon-only/linux/iommu.o
CC [M] /tmp/vmware-root/modules/vmmon-only/linux/hostif.o
CC [M] /tmp/vmware-root/modules/vmmon-only/linux/driverLog.o
CC [M] /tmp/vmware-root/modules/vmmon-only/common/memtrack.o
CC [M] /tmp/vmware-root/modules/vmmon-only/common/vmx86.o
CC [M] /tmp/vmware-root/modules/vmmon-only/common/apic.o
CC [M] /tmp/vmware-root/modules/vmmon-only/common/task.o
CC [M] /tmp/vmware-root/modules/vmmon-only/common/cpuid.o
CC [M] /tmp/vmware-root/modules/vmmon-only/common/comport.o
CC [M] /tmp/vmware-root/modules/vmmon-only/common/hashFunc.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.1.4-1-ARCH'
make -C $PWD SRCROOT=$PWD/. \
MODULEBUILDDIR= postbuild
make[1]: Entering directory `/tmp/vmware-root/modules/vmmon-only'
make[1]: »postbuild« ist bereits aktualisiert.
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'
No protocol specified
No protocol specified
Built vmmon module
Using 2.6.x kernel build system.
make: Entering directory `/tmp/vmware-root/modules/vmnet-only'
make -C /lib/modules/3.1.4-1-ARCH/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. \
MODULEBUILDDIR= modules
make[1]: Entering directory `/usr/src/linux-3.1.4-1-ARCH'
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/smac.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/vnetEvent.o
CC [M] /tmp/vmware-root/modules/vmnet-only/vnetUserListener.o
In file included from /tmp/vmware-root/modules/vmnet-only/bridge.c:51:0:
/tmp/vmware-root/modules/vmnet-only/compat_netdevice.h:186:0: Warnung: »alloc_netdev« redefiniert [standardmäßig aktiviert]
include/linux/netdevice.h:2438:0: Anmerkung: dies ist die Stelle der vorherigen Definition
/tmp/vmware-root/modules/vmnet-only/compat_netdevice.h:187:0: Warnung: »alloc_etherdev« redefiniert [standardmäßig aktiviert]
include/linux/etherdevice.h:53:0: Anmerkung: dies ist die Stelle der vorherigen Definition
/tmp/vmware-root/modules/vmnet-only/compat_netdevice.h:208:1: Fehler: In Konflikt stehende Typen für »netif_start_queue«
include/linux/netdevice.h:1804:20: Anmerkung: Vorherige Definition von »netif_start_queue« war hier
/tmp/vmware-root/modules/vmnet-only/compat_netdevice.h: In Funktion »netif_start_queue«:
/tmp/vmware-root/modules/vmnet-only/compat_netdevice.h:210:21: Fehler: »struct device« hat kein Element namens »tbusy«
/tmp/vmware-root/modules/vmnet-only/compat_netdevice.h: Auf höchster Ebene:
/tmp/vmware-root/modules/vmnet-only/compat_netdevice.h:214:1: Fehler: In Konflikt stehende Typen für »netif_stop_queue«
include/linux/netdevice.h:1869:20: Anmerkung: Vorherige Definition von »netif_stop_queue« war hier
/tmp/vmware-root/modules/vmnet-only/compat_netdevice.h: In Funktion »netif_stop_queue«:
/tmp/vmware-root/modules/vmnet-only/compat_netdevice.h:216:19: Fehler: »struct device« hat kein Element namens »tbusy«
/tmp/vmware-root/modules/vmnet-only/compat_netdevice.h: Auf höchster Ebene:
/tmp/vmware-root/modules/vmnet-only/compat_netdevice.h:220:1: Fehler: In Konflikt stehende Typen für »netif_queue_stopped«
include/linux/netdevice.h:1895:19: Anmerkung: Vorherige Definition von »netif_queue_stopped« war hier
/tmp/vmware-root/modules/vmnet-only/compat_netdevice.h: In Funktion »netif_queue_stopped«:
/tmp/vmware-root/modules/vmnet-only/compat_netdevice.h:222:11: Fehler: »struct device« hat kein Element namens »tbusy«
/tmp/vmware-root/modules/vmnet-only/compat_netdevice.h:222:11: Fehler: »struct device« hat kein Element namens »tbusy«
/tmp/vmware-root/modules/vmnet-only/compat_netdevice.h: Auf höchster Ebene:
/tmp/vmware-root/modules/vmnet-only/compat_netdevice.h:226:1: Fehler: In Konflikt stehende Typen für »netif_wake_queue«
include/linux/netdevice.h:1838:20: Anmerkung: Vorherige Definition von »netif_wake_queue« war hier
/tmp/vmware-root/modules/vmnet-only/compat_netdevice.h: In Funktion »netif_wake_queue«:
/tmp/vmware-root/modules/vmnet-only/compat_netdevice.h:228:21: Fehler: »struct device« hat kein Element namens »tbusy«
/tmp/vmware-root/modules/vmnet-only/compat_netdevice.h:229:4: Fehler: Implizite Deklaration der Funktion »mark_bh« [-Werror=implicit-function-declaration]
/tmp/vmware-root/modules/vmnet-only/compat_netdevice.h:229:12: Fehler: »NET_BH« nicht deklariert (erste Benutzung in dieser Funktion)
/tmp/vmware-root/modules/vmnet-only/compat_netdevice.h:229:12: Anmerkung: jeder nicht deklarierte Bezeichner wird nur einmal für jede Funktion, in der er vorkommt, gemeldet
/tmp/vmware-root/modules/vmnet-only/compat_netdevice.h: Auf höchster Ebene:
/tmp/vmware-root/modules/vmnet-only/compat_netdevice.h:233:1: Fehler: In Konflikt stehende Typen für »netif_running«
include/linux/netdevice.h:1911:19: Anmerkung: Vorherige Definition von »netif_running« war hier
/tmp/vmware-root/modules/vmnet-only/compat_netdevice.h: In Funktion »netif_running«:
/tmp/vmware-root/modules/vmnet-only/compat_netdevice.h:235:14: Fehler: »struct device« hat kein Element namens »start«
/tmp/vmware-root/modules/vmnet-only/compat_netdevice.h: Auf höchster Ebene:
/tmp/vmware-root/modules/vmnet-only/compat_netdevice.h:239:1: Fehler: In Konflikt stehende Typen für »netif_carrier_ok«
include/linux/netdevice.h:2145:19: Anmerkung: Vorherige Definition von »netif_carrier_ok« war hier
/tmp/vmware-root/modules/vmnet-only/compat_netdevice.h:245:1: Fehler: In Konflikt stehende Typen für »netif_carrier_on«
include/linux/netdevice.h:2154:13: Anmerkung: Vorherige Deklaration von »netif_carrier_on« war hier
/tmp/vmware-root/modules/vmnet-only/compat_netdevice.h:250:1: Fehler: In Konflikt stehende Typen für »netif_carrier_off«
include/linux/netdevice.h:2156:13: Anmerkung: Vorherige Deklaration von »netif_carrier_off« war hier
cc1: Einige Warnungen werden als Fehler behandelt
make[2]: *** [/tmp/vmware-root/modules/vmnet-only/bridge.o] Fehler 1
make[2]: *** Warte auf noch nicht beendete Prozesse...
In file included from /tmp/vmware-root/modules/vmnet-only/netif.c:43:0:
/tmp/vmware-root/modules/vmnet-only/compat_netdevice.h:186:0: Warnung: »alloc_netdev« redefiniert [standardmäßig aktiviert]
include/linux/netdevice.h:2438:0: Anmerkung: dies ist die Stelle der vorherigen Definition
/tmp/vmware-root/modules/vmnet-only/compat_netdevice.h:187:0: Warnung: »alloc_etherdev« redefiniert [standardmäßig aktiviert]
include/linux/etherdevice.h:53:0: Anmerkung: dies ist die Stelle der vorherigen Definition
/tmp/vmware-root/modules/vmnet-only/compat_netdevice.h:208:1: Fehler: In Konflikt stehende Typen für »netif_start_queue«
include/linux/netdevice.h:1804:20: Anmerkung: Vorherige Definition von »netif_start_queue« war hier
/tmp/vmware-root/modules/vmnet-only/compat_netdevice.h: In Funktion »netif_start_queue«:
/tmp/vmware-root/modules/vmnet-only/compat_netdevice.h:210:21: Fehler: »struct device« hat kein Element namens »tbusy«
/tmp/vmware-root/modules/vmnet-only/compat_netdevice.h: Auf höchster Ebene:
/tmp/vmware-root/modules/vmnet-only/compat_netdevice.h:214:1: Fehler: In Konflikt stehende Typen für »netif_stop_queue«
include/linux/netdevice.h:1869:20: Anmerkung: Vorherige Definition von »netif_stop_queue« war hier
/tmp/vmware-root/modules/vmnet-only/compat_netdevice.h: In Funktion »netif_stop_queue«:
/tmp/vmware-root/modules/vmnet-only/compat_netdevice.h:216:19: Fehler: »struct device« hat kein Element namens »tbusy«
/tmp/vmware-root/modules/vmnet-only/compat_netdevice.h: Auf höchster Ebene:
/tmp/vmware-root/modules/vmnet-only/compat_netdevice.h:220:1: Fehler: In Konflikt stehende Typen für »netif_queue_stopped«
include/linux/netdevice.h:1895:19: Anmerkung: Vorherige Definition von »netif_queue_stopped« war hier
/tmp/vmware-root/modules/vmnet-only/compat_netdevice.h: In Funktion »netif_queue_stopped«:
/tmp/vmware-root/modules/vmnet-only/compat_netdevice.h:222:11: Fehler: »struct device« hat kein Element namens »tbusy«
/tmp/vmware-root/modules/vmnet-only/compat_netdevice.h:222:11: Fehler: »struct device« hat kein Element namens »tbusy«
/tmp/vmware-root/modules/vmnet-only/compat_netdevice.h: Auf höchster Ebene:
/tmp/vmware-root/modules/vmnet-only/compat_netdevice.h:226:1: Fehler: In Konflikt stehende Typen für »netif_wake_queue«
include/linux/netdevice.h:1838:20: Anmerkung: Vorherige Definition von »netif_wake_queue« war hier
/tmp/vmware-root/modules/vmnet-only/compat_netdevice.h: In Funktion »netif_wake_queue«:
/tmp/vmware-root/modules/vmnet-only/compat_netdevice.h:228:21: Fehler: »struct device« hat kein Element namens »tbusy«
/tmp/vmware-root/modules/vmnet-only/compat_netdevice.h:229:4: Fehler: Implizite Deklaration der Funktion »mark_bh« [-Werror=implicit-function-declaration]
/tmp/vmware-root/modules/vmnet-only/compat_netdevice.h:229:12: Fehler: »NET_BH« nicht deklariert (erste Benutzung in dieser Funktion)
/tmp/vmware-root/modules/vmnet-only/compat_netdevice.h:229:12: Anmerkung: jeder nicht deklarierte Bezeichner wird nur einmal für jede Funktion, in der er vorkommt, gemeldet
/tmp/vmware-root/modules/vmnet-only/compat_netdevice.h: Auf höchster Ebene:
/tmp/vmware-root/modules/vmnet-only/compat_netdevice.h:233:1: Fehler: In Konflikt stehende Typen für »netif_running«
include/linux/netdevice.h:1911:19: Anmerkung: Vorherige Definition von »netif_running« war hier
/tmp/vmware-root/modules/vmnet-only/compat_netdevice.h: In Funktion »netif_running«:
/tmp/vmware-root/modules/vmnet-only/compat_netdevice.h:235:14: Fehler: »struct device« hat kein Element namens »start«
/tmp/vmware-root/modules/vmnet-only/compat_netdevice.h: Auf höchster Ebene:
/tmp/vmware-root/modules/vmnet-only/compat_netdevice.h:239:1: Fehler: In Konflikt stehende Typen für »netif_carrier_ok«
include/linux/netdevice.h:2145:19: Anmerkung: Vorherige Definition von »netif_carrier_ok« war hier
/tmp/vmware-root/modules/vmnet-only/compat_netdevice.h:245:1: Fehler: In Konflikt stehende Typen für »netif_carrier_on«
include/linux/netdevice.h:2154:13: Anmerkung: Vorherige Deklaration von »netif_carrier_on« war hier
/tmp/vmware-root/modules/vmnet-only/compat_netdevice.h:250:1: Fehler: In Konflikt stehende Typen für »netif_carrier_off«
include/linux/netdevice.h:2156:13: Anmerkung: Vorherige Deklaration von »netif_carrier_off« war hier
/tmp/vmware-root/modules/vmnet-only/netif.c: In Funktion »VNetNetIfSetup«:
/tmp/vmware-root/modules/vmnet-only/netif.c:149:7: Fehler: »struct net_device« hat kein Element namens »init«
/tmp/vmware-root/modules/vmnet-only/netif.c:150:7: Fehler: »struct net_device« hat kein Element namens »open«
/tmp/vmware-root/modules/vmnet-only/netif.c:151:7: Fehler: »struct net_device« hat kein Element namens »hard_start_xmit«
/tmp/vmware-root/modules/vmnet-only/netif.c:152:7: Fehler: »struct net_device« hat kein Element namens »stop«
/tmp/vmware-root/modules/vmnet-only/netif.c:153:7: Fehler: »struct net_device« hat kein Element namens »get_stats«
/tmp/vmware-root/modules/vmnet-only/netif.c:154:7: Fehler: »struct net_device« hat kein Element namens »set_mac_address«
/tmp/vmware-root/modules/vmnet-only/netif.c:155:7: Fehler: »struct net_device« hat kein Element namens »set_multicast_list«
/tmp/vmware-root/modules/vmnet-only/netif.c: In Funktion »VNetNetIfNetDeviceToNetIf«:
/tmp/vmware-root/modules/vmnet-only/netif.c:196:14: Fehler: »struct net_device« hat kein Element namens »priv«
/tmp/vmware-root/modules/vmnet-only/netif.c: In Funktion »VNetNetIf_Create«:
/tmp/vmware-root/modules/vmnet-only/netif.c:311:4: Fehler: Implizite Deklaration der Funktion »compat_alloc_netdev« [-Werror=implicit-function-declaration]
/tmp/vmware-root/modules/vmnet-only/netif.c:311:8: Warnung: Zuweisung erzeugt Zeiger von Ganzzahl ohne Typkonvertierung [standardmäßig aktiviert]
/tmp/vmware-root/modules/vmnet-only/netif.c:316:7: Fehler: »struct net_device« hat kein Element namens »priv«
/tmp/vmware-root/modules/vmnet-only/netif.c: In Funktion »VNetNetIfReceive«:
/tmp/vmware-root/modules/vmnet-only/netif.c:397:4: Warnung: Übergabe des Arguments 1 von »netif_running« von inkompatiblem Zeigertyp [standardmäßig aktiviert]
/tmp/vmware-root/modules/vmnet-only/compat_netdevice.h:233:1: Anmerkung: »struct device *« erwartet, aber Argument hat Typ »struct net_device *«
/tmp/vmware-root/modules/vmnet-only/netif.c: In Funktion »VNetNetifOpen«:
/tmp/vmware-root/modules/vmnet-only/netif.c:477:4: Warnung: Übergabe des Arguments 1 von »netif_start_queue« von inkompatiblem Zeigertyp [standardmäßig aktiviert]
/tmp/vmware-root/modules/vmnet-only/compat_netdevice.h:208:1: Anmerkung: »struct device *« erwartet, aber Argument hat Typ »struct net_device *«
/tmp/vmware-root/modules/vmnet-only/netif.c: In Funktion »VNetNetifClose«:
/tmp/vmware-root/modules/vmnet-only/netif.c:525:4: Warnung: Übergabe des Arguments 1 von »netif_stop_queue« von inkompatiblem Zeigertyp [standardmäßig aktiviert]
/tmp/vmware-root/modules/vmnet-only/compat_netdevice.h:214:1: Anmerkung: »struct device *« erwartet, aber Argument hat Typ »struct net_device *«
/tmp/vmware-root/modules/vmnet-only/netif.c: In Funktion »netif_running«:
/tmp/vmware-root/modules/vmnet-only/compat_netdevice.h:236:1: Warnung: Kontrollfluss erreicht Ende von Nicht-void-Funktion [-Wreturn-type]
cc1: Einige Warnungen werden als Fehler behandelt
make[2]: *** [/tmp/vmware-root/modules/vmnet-only/netif.o] Fehler 1
make[1]: *** [_module_/tmp/vmware-root/modules/vmnet-only] Fehler 2
make[1]: Leaving directory `/usr/src/linux-3.1.4-1-ARCH'
make: *** [vmnet.ko] Fehler 2
make: Leaving directory `/tmp/vmware-root/modules/vmnet-only'
Unable to install vmnet
Maybe someone has an idea whats going wrong ?
stubb
Last edited by stubb (2011-12-01 23:45:44)

rm /usr/lib/vmware/modules/source/.patched
fixed it

Similar Messages

[SOLVED] VMWare Player won't install

Hello,
I have a problem installing VMWare player on arch. (disclaimer: I have RTFM *and* searched and googled hehe)
I'm trying to install VMware-Player-2.5.1-126130.x86_64.bundle on the following machine:
Linux 2.6.29-ARCH #1 SMP PREEMPT x86_64 AMD Phenom(tm) 9850 Quad-Core Processor AuthenticAMD GNU/Linux
I was following the guide here: http://wiki.archlinux.org/index.php/Installing_VMware
and somewhat here: http://forums.fedoraforum.org/showthread.php?p=1126993
My problem is though when i run /usr/bin/vmplayer it complains that
Unable to build kernel module
See log file /tmp/vmware-root/setup-12218.log for details
and wont do anything else. I've basicly followed the guide I listed above in its steps so I'm a little lost now.
Any advice would be greatly appriciated as its for a university assigment im rapidly running out of time on heheh.
Regards,
Mike.
Last edited by DrMikeDuke (2009-04-05 16:50:59)

Thanks for your help so far, awesome!
I got it to work but a little differently since it still wouldnt patch for me
Anyhow Il post my solution here since i know I always hate visiting a
SOLVED thread only to find noone said HOW
So I move my file from binary to binary old
(mv /usr/lib/vmware/modules/binary /usr/lib/vmware/modules/binary.old)
then i go to my source directory
(cd /usr/lib/vmware/modules/source)
i untar everything in sight (:P)
[root@TOMATO source]# ls
vmblock-only vmci.tar vmnet-only vmppuser.tar
vmblock.tar vmmon-only vmnet.tar vmware-workstation-2.6.29-v2.patch
vmci-only vmmon.tar vmppuser-only vsock.tar
then I used the scripts from here http://communities.vmware.com//thread/203231
Finally I run step 6). vmware-modconfig --console --install-all
And done!:D

[Solved]Vmware Player - Blocking File System not fails to load

All the mods load fine, except Vmblock.
this is what i get when i run vmplayer.
make: *** /tmp/modconfig-NtGU4D/vmblock-only: No such file or directory. Stop.
Starting VMware Services:
Virtual machine monitor....
(finishes loading without problems)
i suspect this has to do with the fact that i couldn't patch it following the wiki's guide (vmnet patched fine).
I have the latest vmware player and the current arch linux kernel (3.10.7-1)
The patch doesn't seem to find the file it's meant to patch.
I'd also like to know if i can safely ignore this.
Edit: I suspect i just made a failure during the installation, i reinstalled it and it loaded this time... i think.
Last edited by rabcor (2013-08-23 09:10:09)

andy_v wrote:Make sure you create a 'compiz.desktop' file under /usr/share/applications.
And that fixed it! Don't know how I overlooked that. Thanks!

VMware player won't start after kernel update

Hi,
today I've updated to 3.9.6-1 kernel and all went good. So I wanted to start my vmware player to start a vm. Of course I've done the needed steps in the vmplayer wiki page to setup the new headers and stuff after kernel update for vmplayer. Also I've ran "vmware-patch -f" and ran trough. But still get an error when I wanted to start the player in the "/tmp/vmware-root/vmware-modconfig-11986.log":
2013-06-16T13:03:51.680+01:00| vthread-3| I120: Log for VMware Workstation pid=11986 version=9.0.2 build=build-1031769 option=Release
2013-06-16T13:03:51.680+01:00| vthread-3| I120: The process is 64-bit.
2013-06-16T13:03:51.680+01:00| vthread-3| I120: Host codepage=UTF-8 encoding=UTF-8
2013-06-16T13:03:51.680+01:00| vthread-3| I120: Host is Linux 3.9.6-1-ARCH 2013.04.01
2013-06-16T13:03:51.680+01:00| vthread-3| I120: Msg_Reset:
2013-06-16T13:03:51.680+01:00| vthread-3| I120: [msg.dictionary.load.openFailed] Cannot open file "/usr/lib/vmware/settings": No such file or directory.
2013-06-16T13:03:51.680+01:00| vthread-3| I120: ----------------------------------------
2013-06-16T13:03:51.680+01:00| vthread-3| I120: PREF Optional preferences file not found at /usr/lib/vmware/settings. Using default values.
2013-06-16T13:03:51.680+01:00| vthread-3| I120: Msg_Reset:
2013-06-16T13:03:51.680+01:00| vthread-3| I120: [msg.dictionary.load.openFailed] Cannot open file "/root/.vmware/config": No such file or directory.
2013-06-16T13:03:51.680+01:00| vthread-3| I120: ----------------------------------------
2013-06-16T13:03:51.680+01:00| vthread-3| I120: PREF Optional preferences file not found at /root/.vmware/config. Using default values.
2013-06-16T13:03:51.680+01:00| vthread-3| I120: Msg_Reset:
2013-06-16T13:03:51.680+01:00| vthread-3| I120: [msg.dictionary.load.openFailed] Cannot open file "/root/.vmware/preferences": No such file or directory.
2013-06-16T13:03:51.680+01:00| vthread-3| I120: ----------------------------------------
2013-06-16T13:03:51.680+01:00| vthread-3| I120: PREF Failed to load user preferences.
2013-06-16T13:03:51.680+01:00| vthread-3| W110: Logging to /tmp/vmware-root/vmware-modconfig-11986.log
2013-06-16T13:03:51.687+01:00| vthread-3| I120: Reading in info for the vmmon module.
2013-06-16T13:03:51.687+01:00| vthread-3| I120: Reading in info for the vmnet module.
2013-06-16T13:03:51.687+01:00| vthread-3| I120: Reading in info for the vmblock module.
2013-06-16T13:03:51.687+01:00| vthread-3| I120: Reading in info for the vmci module.
2013-06-16T13:03:51.687+01:00| vthread-3| I120: Reading in info for the vsock module.
2013-06-16T13:03:51.687+01:00| vthread-3| I120: Setting vsock to depend on vmci.
2013-06-16T13:03:51.687+01:00| vthread-3| I120: Created new pathsHash.
2013-06-16T13:03:51.687+01:00| vthread-3| I120: Invoking modinfo on "vmmon".
2013-06-16T13:03:51.689+01:00| vthread-3| I120: "/sbin/modinfo" exited with status 0.
2013-06-16T13:03:51.689+01:00| vthread-3| I120: Invoking modinfo on "vmnet".
2013-06-16T13:03:51.690+01:00| vthread-3| I120: "/sbin/modinfo" exited with status 0.
2013-06-16T13:03:51.690+01:00| vthread-3| I120: Invoking modinfo on "vmblock".
2013-06-16T13:03:51.691+01:00| vthread-3| I120: "/sbin/modinfo" exited with status 0.
2013-06-16T13:03:51.691+01:00| vthread-3| I120: Invoking modinfo on "vmci".
2013-06-16T13:03:51.693+01:00| vthread-3| I120: "/sbin/modinfo" exited with status 0.
2013-06-16T13:03:51.693+01:00| vthread-3| I120: Invoking modinfo on "vsock".
2013-06-16T13:03:51.696+01:00| vthread-3| I120: "/sbin/modinfo" exited with status 0.
Maybe it has something to do with the last filesystem update?
But I don't know what to do really and couldn't found anything on that.
thanks

sorry, found something now in another thread here. this fix works just fyi:
kokoko3k wrote:
Quick and dirty workaround to fully update your system
sudo pacman -Suy #update everything
sudo mkdir -p /usr/local/lib/gtkmm && cd /usr/local/lib/gtkmm
sudo wget http://arm.konnichi.com/2013/01/05/extra/os/x86_64/gtkmm-2.24.2-2-x86_64.pkg.tar.xz
#sudo wget http://arm.konnichi.com/2013/01/05/extra/os/i686/gtkmm-2.24.2-2-i686.pkg.tar.xz #The bug affects i686 too.
sudo tar -xvf ./gtkmm-2.24.2-2-x86_64.pkg.tar.xz
#sudo tar -xvf ./gtkmm-2.24.2-2-i686.pkg.tar.xz #The bug affects i686 too.
LD_LIBRARY_PATH=/usr/local/lib/gtkmm/usr/lib/ vmplayer #start it with old libraries

[SOLVED] VMware player, network doesn't work

Hi!
I installed VMware player through AUR and it works well. But when I started my vm (Debian 4.0) it asked if I had copied or moved it. I chose "I copied it" because I copied it from my hdd to external hdd. I started my vm but network didn't work. I configured network using vmware-config.pl file like it recommended (vmnet0 as bridged with my wlan0 and vmnet8 as NAT. I also chose to use host-only networking in my vm's (wmaster0)). How did you guys configured your network succesfully?
I just want it to work like on my windows box. It has it's own IP and I can connect to it's IP directly from firefox. Yeah, I run webserver on that vm.
My ifconfig:
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:656 errors:0 dropped:0 overruns:0 frame:0
TX packets:656 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:24109 (23.5 Kb) TX bytes:24109 (23.5 Kb)
vmnet1 Link encap:Ethernet HWaddr 00:50:56:C0:00:01
inet addr:172.16.22.1 Bcast:172.16.22.255 Mask:255.255.255.0
inet6 addr: fe80::250:56ff:fec0:1/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:6 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
vmnet8 Link encap:Ethernet HWaddr 00:50:56:C0:00:08
inet addr:172.16.43.1 Bcast:172.16.43.255 Mask:255.255.255.0
inet6 addr: fe80::250:56ff:fec0:8/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:6 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
wlan0 Link encap:Ethernet HWaddr 00:1B:77:04:D4:D0
inet addr:192.168.0.20 Bcast:192.168.0.255 Mask:255.255.255.0
inet6 addr: fe80::21b:77ff:fe04:d4d0/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:22719 errors:0 dropped:0 overruns:0 frame:0
TX packets:14300 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:14584732 (13.9 Mb) TX bytes:2004755 (1.9 Mb)
wmaster0 Link encap:UNSPEC HWaddr 00-1B-77-04-D4-D0-00-00-00-00-00-00-00-00-00-00
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
Last edited by Nuck (2008-07-12 18:27:49)

Nuck wrote:
Hi!
I installed VMware player through AUR and it works well. But when I started my vm (Debian 4.0) it asked if I had copied or moved it. I chose "I copied it" because I copied it from my hdd to external hdd. I started my vm but network didn't work. I configured network using vmware-config.pl file like it recommended (vmnet0 as bridged with my wlan0 and vmnet8 as NAT. I also chose to use host-only networking in my vm's (wmaster0)). How did you guys configured your network succesfully?
I just want it to work like on my windows box. It has it's own IP and I can connect to it's IP directly from firefox. Yeah, I run webserver on that vm.
My ifconfig:
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:656 errors:0 dropped:0 overruns:0 frame:0
TX packets:656 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:24109 (23.5 Kb) TX bytes:24109 (23.5 Kb)
vmnet1 Link encap:Ethernet HWaddr 00:50:56:C0:00:01
inet addr:172.16.22.1 Bcast:172.16.22.255 Mask:255.255.255.0
inet6 addr: fe80::250:56ff:fec0:1/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:6 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
vmnet8 Link encap:Ethernet HWaddr 00:50:56:C0:00:08
inet addr:172.16.43.1 Bcast:172.16.43.255 Mask:255.255.255.0
inet6 addr: fe80::250:56ff:fec0:8/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:6 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
wlan0 Link encap:Ethernet HWaddr 00:1B:77:04:D4:D0
inet addr:192.168.0.20 Bcast:192.168.0.255 Mask:255.255.255.0
inet6 addr: fe80::21b:77ff:fe04:d4d0/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:22719 errors:0 dropped:0 overruns:0 frame:0
TX packets:14300 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:14584732 (13.9 Mb) TX bytes:2004755 (1.9 Mb)
wmaster0 Link encap:UNSPEC HWaddr 00-1B-77-04-D4-D0-00-00-00-00-00-00-00-00-00-00
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
set the network connection to NAT not BRIDGE (in the settings tab). i never got BRIDGE running, but i also haven't tried too hard.
Last edited by DonVla (2008-07-12 17:01:31)

Vmware Server 1.0.3 and kernel 2.6.22

Maybe this will be of help to anyone...
The modules for vmware server 1.0.3 don't compile under 2.6.22-ARCH kernel from testing, and as far as I know there is no patch to fix that automatically yet. I was able to to compile them successfully using the information from post 11 in this thread: http://www.vmware.com/community/thread. … adID=92709 - the specific file that I had to edit was "/usr/src/linux-2.6.22-ARCH/include/asm-i386/page.h".

To compile vmware workstation 6 for the new kernel check out this link.
http://npw.net/2007/05/17/vmware-workst … inux-2622/

Vmware-server 1.0.1 and kernel *.19 [solved]

Hi,
since I upgraded the kernel from 2.6.18 to .19 I cant get my vmware-server running. Has anybody else this problem?
I ran vmware-config.pl again but it always crashes with:
make[1]: Entering directory `/usr/src/linux-2.6.19-ARCH'
CC [M] /tmp/vmware-config2/vmnet-only/driver.o
CC [M] /tmp/vmware-config2/vmnet-only/hub.o
CC [M] /tmp/vmware-config2/vmnet-only/userif.o
/tmp/vmware-config2/vmnet-only/userif.c: In Funktion »VNetCopyDatagramToUser«:
/tmp/vmware-config2/vmnet-only/userif.c:629: Fehler: »CHECKSUM_HW« nicht deklariert (erste Benutzung in dieser Funktion)
/tmp/vmware-config2/vmnet-only/userif.c:629: Fehler: (Jeder nicht deklarierte Bezeichner wird nur einmal aufgeführt
/tmp/vmware-config2/vmnet-only/userif.c:629: Fehler: für jede Funktion in der er auftritt.)
make[2]: *** [/tmp/vmware-config2/vmnet-only/userif.o] Fehler 1
make[1]: *** [_module_/tmp/vmware-config2/vmnet-only] Fehler 2
make[1]: Leaving directory `/usr/src/linux-2.6.19-ARCH'
make: *** [vmnet.ko] Fehler 2
make: Leaving directory `/tmp/vmware-config2/vmnet-only'
Unable to build the vmnet module.
I try to create this error in english later, but maybe u know the problem already. I found sth about a any-any-patch but I couldnt find out if this is related to arch.
Would be great if somebody could give me a hint.
Btw, Merry Christmas [/i]

Merry Christmas to you too.
Yes. The problem is related to the any-any-patch.
Get the latest version of the patch and run it. That should solve the problem.
If for whatever reason it fails then, and only then, look for this file:
/lib/modules/2.6.18-ARCH/build/include/linux/version.h, and make sure it contains a line for the UTS_RELEASE, and if it does not, add at the end the following: define UTS_RELEASE "2.6.19-ARCH"
Then run the patch again.
Hope it helps.
R

[SOLVED] VMware player update error with kernel 2.6.35

I have WMware player 3.1, it was working fine until I upgrade to kernel 2.6.35. Here is WMware error message:
aoû 24 20:51:34.275: app-3076503232| Log for VMware Workstation pid=6643 version=7.1.0 build=build-261024 option=Release
aoû 24 20:51:34.275: app-3076503232| The process is 32-bit.
aoû 24 20:51:34.275: app-3076503232| Host codepage=UTF-8 encoding=UTF-8
aoû 24 20:51:34.275: app-3076503232| Logging to /tmp/vmware-root/setup-6643.log
aoû 24 20:51:34.377: app-3076503232| modconf query interface initialized
aoû 24 20:51:34.378: app-3076503232| modconf library initialized
aoû 24 20:51:34.468: app-3076503232| Your GCC version: 4.5
aoû 24 20:51:34.477: app-3076503232| Your GCC version: 4.5
aoû 24 20:51:34.509: app-3076503232| Your GCC version: 4.5
aoû 24 20:51:34.553: app-3076503232| Your GCC version: 4.5
aoû 24 20:51:34.585: app-3076503232| Your GCC version: 4.5
aoû 24 20:51:34.695: app-3076503232| Trying to find a suitable PBM set for kernel 2.6.35-ARCH.
aoû 24 20:51:34.700: app-3076503232| Trying to find a suitable PBM set for kernel 2.6.35-ARCH.
aoû 24 20:51:34.705: app-3076503232| Trying to find a suitable PBM set for kernel 2.6.35-ARCH.
aoû 24 20:51:34.710: app-3076503232| Trying to find a suitable PBM set for kernel 2.6.35-ARCH.
aoû 24 20:51:34.714: app-3076503232| Trying to find a suitable PBM set for kernel 2.6.35-ARCH.
aoû 24 20:51:34.779: app-3076503232| Trying to find a suitable PBM set for kernel 2.6.35-ARCH.
aoû 24 20:51:34.783: app-3076503232| Trying to find a suitable PBM set for kernel 2.6.35-ARCH.
aoû 24 20:51:34.788: app-3076503232| Trying to find a suitable PBM set for kernel 2.6.35-ARCH.
aoû 24 20:51:34.793: app-3076503232| Trying to find a suitable PBM set for kernel 2.6.35-ARCH.
aoû 24 20:51:34.797: app-3076503232| Trying to find a suitable PBM set for kernel 2.6.35-ARCH.
aoû 24 20:51:34.803: app-3076503232| Your GCC version: 4.5
aoû 24 20:51:34.837: app-3076503232| Your GCC version: 4.5
aoû 24 20:51:34.948: app-3076503232| Trying to find a suitable PBM set for kernel 2.6.35-ARCH.
aoû 24 20:51:34.953: app-3076503232| Trying to find a suitable PBM set for kernel 2.6.35-ARCH.
aoû 24 20:51:34.958: app-3076503232| Trying to find a suitable PBM set for kernel 2.6.35-ARCH.
aoû 24 20:51:34.962: app-3076503232| Trying to find a suitable PBM set for kernel 2.6.35-ARCH.
aoû 24 20:51:34.967: app-3076503232| Trying to find a suitable PBM set for kernel 2.6.35-ARCH.
aoû 24 20:51:34.973: app-3076503232| Your GCC version: 4.5
aoû 24 20:51:35.013: app-3076503232| Your GCC version: 4.5
aoû 24 20:51:35.187: app-3076503232| Trying to find a suitable PBM set for kernel 2.6.35-ARCH.
aoû 24 20:51:35.192: app-3076503232| Trying to find a suitable PBM set for kernel 2.6.35-ARCH.
aoû 24 20:51:35.198: app-3076503232| Trying to find a suitable PBM set for kernel 2.6.35-ARCH.
aoû 24 20:51:35.203: app-3076503232| Trying to find a suitable PBM set for kernel 2.6.35-ARCH.
aoû 24 20:51:35.208: app-3076503232| Trying to find a suitable PBM set for kernel 2.6.35-ARCH.
aoû 24 20:51:35.656: app-3076503232| Trying to find a suitable PBM set for kernel 2.6.35-ARCH.
aoû 24 20:51:35.657: app-3076503232| Building module vmmon.
aoû 24 20:51:35.657: app-3076503232| Extracting the sources of the vmmon module.
aoû 24 20:51:35.697: app-3076503232| Building module with command: /usr/bin/make -C /tmp/vmware-root/modules/vmmon-only auto-build SUPPORT_SMP=1 HEADER_DIR=/lib/modules/2.6.35-ARCH/build/include CC=/usr/bin/gcc GREP=/usr/bin/make IS_GCC_3=no VMCCVER=4.5.1
aoû 24 20:51:41.031: app-3076503232| Failed to compile module vmmon!
Thanks for help!
Last edited by srivo (2010-10-26 02:05:16)

I tried this it didn't work:
% wget http://www.sputnick-area.net/scripts/vm … .6.35.bash
--2011-06-15 11:18:03-- http://www.sputnick-area.net/scripts/vm … .6.35.bash
Resolving www.sputnick-area.net... 91.121.18.134
Connecting to www.sputnick-area.net|91.121.18.134|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 6992 (6.8K) [text/plain]
Saving to: “vmware7.1.1-patch-kernel-2.6.35.bash.1”
100%[======================================================================>] 6,992 --.-K/s in 0.07s
2011-06-15 11:18:06 (97.8 KB/s) - “vmware7.1.1-patch-kernel-2.6.35.bash.1” saved [6992/6992]
% ./vmware7.1.1-patch-kernel-2.6.35.bash
This script have been already applied !
% vmware-modconfig --console --install-all
Stopping vmware (via systemctl): [ OK ]
Using 2.6.x kernel build system.
make: Entering directory `/tmp/vmware-root-62598440/modules/vmmon-only'
make -C /lib/modules/2.6.38.7-30.fc15.x86_64/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. \
MODULEBUILDDIR= modules
make[1]: Entering directory `/usr/src/kernels/2.6.38.7-30.fc15.x86_64'
CC [M] /tmp/vmware-root-62598440/modules/vmmon-only/linux/driver.o
/tmp/vmware-root-62598440/modules/vmmon-only/linux/driver.c: In function ‘init_module’:
/tmp/vmware-root-62598440/modules/vmmon-only/linux/driver.c:425:15: error: ‘struct file_operations’ has no member named ‘ioctl’
/tmp/vmware-root-62598440/modules/vmmon-only/linux/driver.c: In function ‘LinuxDriver_Ioctl’:
/tmp/vmware-root-62598440/modules/vmmon-only/linux/driver.c:1736:7: error: implicit declaration of function ‘kernel_locked’ [-Werror=implicit-function-declaration]
cc1: some warnings being treated as errors
make[2]: *** [/tmp/vmware-root-62598440/modules/vmmon-only/linux/driver.o] Error 1
make[1]: *** [_module_/tmp/vmware-root-62598440/modules/vmmon-only] Error 2
make[1]: Leaving directory `/usr/src/kernels/2.6.38.7-30.fc15.x86_64'
make: *** [vmmon.ko] Error 2
make: Leaving directory `/tmp/vmware-root-62598440/modules/vmmon-only'
Unable to install vmmon

[Solved]vmware player crash with sound card ubuntu 14.04

hi people how are you
i'm new on this forum i need help...
i'm running OSX yosemite in Vmplayer 7.1.0 , osx run fine ..but when i will play a sound, the vmplayer go to crash
if disconnect the sound in emulator, this work fine without this but.. i need sound ..
how fix this crash ??
Fix: i have changed sound.virtualdev = "hdaudio" to sound.virtualdev = "es1371" in .vmx and downloaded EnsoniqAudioPCI_v1.0.3_Common_Installer.pkg and now work fine! no crashes.. .

Are you on kernel 3.10?
http://wireless.kernel.org/en/users/Drivers/iwlwifi
EDIT: Seems to work fine for the Debian folks.
W520: i7-2720QM, Q2000M at 1080/688/1376, 21GB RAM, 500GB + 750GB HDD, FHD screen
X61T: L7500, 3GB RAM, 500GB HDD, XGA screen, Ultrabase
Y3P: 5Y70, 8GB RAM, 256GB SSD, QHD+ screen

[Solved] Can not build modules for VMware Player after kernel updates

I have a problem generating the modules for VMware Player after kernel updates. I am using VMware Player version 5.02 (without patches) and the softlink according to the Wiki.
When I start the installation of the modules from the GUI, the program just closes. Running vmware-modconfig in the CLI generates the following log file:
2013-04-29T09:49:27.891+01:00| vthread-3| I120: Log for VMware Workstation pid=7478 version=9.0.2 build=build-1031769 option=Release
2013-04-29T09:49:27.891+01:00| vthread-3| I120: The process is 64-bit.
2013-04-29T09:49:27.891+01:00| vthread-3| I120: Host codepage=UTF-8 encoding=UTF-8
2013-04-29T09:49:27.891+01:00| vthread-3| I120: Host is Linux 3.8.10-1-ARCH 2012.11.29
2013-04-29T09:49:27.891+01:00| vthread-3| I120: Msg_Reset:
2013-04-29T09:49:27.891+01:00| vthread-3| I120: [msg.dictionary.load.openFailed] Cannot open file "/usr/lib/vmware/settings": Datei oder Verzeichnis nicht gefunden.
2013-04-29T09:49:27.891+01:00| vthread-3| I120: ----------------------------------------
2013-04-29T09:49:27.891+01:00| vthread-3| I120: PREF Optional preferences file not found at /usr/lib/vmware/settings. Using default values.
2013-04-29T09:49:27.891+01:00| vthread-3| I120: Msg_Reset:
2013-04-29T09:49:27.891+01:00| vthread-3| I120: [msg.dictionary.load.openFailed] Cannot open file "/root/.vmware/config": Datei oder Verzeichnis nicht gefunden.
2013-04-29T09:49:27.891+01:00| vthread-3| I120: ----------------------------------------
2013-04-29T09:49:27.891+01:00| vthread-3| I120: PREF Optional preferences file not found at /root/.vmware/config. Using default values.
2013-04-29T09:49:27.891+01:00| vthread-3| W110: Logging to /tmp/vmware-root/vmware-modconfig-7478.log
2013-04-29T09:49:27.892+01:00| vthread-3| W110: Icon name must be set.
Interestingly, after deinstallation and reinstallation the VMWare Player works fine.
Any hint, what's going wrong?
Last edited by Thomas_Do (2013-08-07 07:25:51)

Today, (Kernel 3.10.5-1, VMware Player version 5.02 with kernel patches) the modules could successful be generated from the CLI:
vmware-modconfig --console --install-all
Solved (somehow).

Kernel 2.6.22 and vmware-player-modules

Just for information:
If someone got problems reinstalling vmware-player-modules after the last Kernel update to 2.6.22, here's a workaround:
1. Get the package vmware-player-modules from the aur..
2. try building vmware-player-modules with makepkg (that's where the problem occurs)
3. download the file vmnet.tar from here, unpack it somewhere
4. copy the .tar and the unpacked folder to the vmware-player-modules source ( cp -r vmnet* /var/abs/local/vmware-player-modules/src/vmware-player-distrib/lib/modules/source )
5. build the package again with makepkg -e and install it
yay.

drfindley wrote:
That fixed my problem. I removed kvm-modules and re-synced my kernel, in case kvm-modules had trashed my kvm.ko files.
Also one thing that would really help would be to add the udev-rules from the kvm-modules and create the group kvm. I don't know if that's appropriate with the mainline kernel or not, though.
We'll have to re-add the rules and some other files in the qemu package (which includes the userspace kvm stuff).

VMWare Player Pro Central Management?

If we use VMWare Workstation software installed on a server to create VMWare Player Pro restricted VMs and then we distributed those VMs to user's workstations, how could we manage those VMs at a console level without having to log into each user's workstations?
By joining the VMs to a domain and connected network, we can do remote management of the VMs in Windows via AD Group Policy and other tools, but does VMWare Workstation allow you to remotely connect to them at the console level and shutdown, power on and reconfigure the VMWare Player Plus VM "hardware?"
This topic first appeared in the Spiceworks Community

reply above - please answer:
win 8.0 pro VM should be OFF to change/extend its hdd space?
another Q
I INSTALLED WIN 8.0 PRO TO VMWARE AS GUESS OS VM
If buy touch screen for my host win 7 pro PC - can this work as well in VM GUESS OSs like win 8.0 pro or Ubuntu 14.04?
Message was edited by: lse123

Trying to install Vmware Player on OEL 4-kernel 2.6.9-78.0.0.0.1.ELhugemem

All
I need to run a preconfigured Vmware VM on one of ours Enterprise Linux servers. I've already installed VMware-Player-3.1.2-301548.i386.bundle on the machine, no error message, but now when I try to run vmplayer I am getting the following message:
before you can run vmware, several modules must be compiled and loaded into the running kernel:
kernel headers 2.6.9-78.0.0.0.1.ELHugemem
kernel headers for version 2.6.9-78.0.0.0.1.ELHugemem were not found...
I've already searched both on google and on Oracle website for a package containing this version of kernel headers, but didn't find them.
I've did an up2date -i kernel-devel, some kernel headers got installed, but it seems they are at the wrong version:
[root@dscdap01 ~]# ls -la /usr/src/kernels/
total 24
drwxr-xr-x 4 root root 4096 Nov 2 06:59 .
drwxr-xr-x 4 root root 4096 Dec 4 2008 ..
drwxr-xr-x 17 root root 4096 Nov 1 09:42 2.6.9-89.31.1.0.1.EL-hugemem-i686
drwxr-xr-x 17 root root 4096 Nov 2 06:59 2.6.9-89.31.1.0.1.EL-i686
As far as I can see, I have two paths for solving this:
1: update the running kernel to 2.6.9-89.31.1.0.1.EL-hugemem-i686 - in order to do that I'll have to restart the machine, which is quite risky because this is an important machine used for many projects and I do not have physical access to it; in case something goes wrong I'll have to make an SR to the GIT guys, and pray for a quick resolution
2. find this particular version on kernel headers (2.6.9-78.0.0.0.1.ELHugemem), install them in a non-standard location and then point vmplayer installer to that location in order to compile and plug them into the running kernel
Questions:
- If I choose the 2nd path:
-- where can I find this particular kernel headers version?
-- after vmplayer compiles them, will it request a machine restart, or plugging them into the running kernel will be possible without restart?
-- I already did an up2date -u, so the entire system excepting the running kernel is updated to whatever is in Oracle's internal repositories. Will this conflict somehow with an older running kernel and modules?
-If I choose the 1th path (update the kernel itself and reboot the machine):
-- will then vmplayer be able to compile and install the kernel modules without asking for another restart?
Thanks a lot for your feedback.
Any idea is appreciated, even pointing me to someone in Oracle that might help (I am an Oracle employee) would be useful.
Regards
Serban

Thanks for your reply Joe. I did not realise that I shall search for the package name without "ELHugemem" part since the headers are probably the same. Please correct me if I'm wrong here.
So I downloaded the i686 package, but now I get this message:
[root@dscdap01 ~]# rpm -iv kernel-devel-2.6.9-78.0.1.EL.i686.rpm
warning: kernel-devel-2.6.9-78.0.1.EL.i686.rpm: V3 DSA signature: NOKEY, key ID 82fd17b2
Preparing packages for installation...
package kernel-devel-2.6.9-89.31.1.0.1.EL (which is newer than kernel-devel-2.6.9-78.0.1.EL) is already installed
I am not sure if I shall do a "rpm -ivf" for this package, forcing it to install. Will this command install the package alongside the existing one, or will it overwrite it? My guess is that it will install it alongside the existing one, but since this system is an important one I would prefer to ask before doing any stupid mistake...

Trying to install Vmware Player on OEL and running into an error

All
I need to run a preconfigured Vmware VM on one of ours Enterprise Linux servers. I've already installed VMware-Player-3.13.*.bundle on the machine, no error message, but now when I try to run vmplayer I am getting the following message :
before you can run vmware, several modules must be compiled and loaded into the running kernel:
kernel headers 2.6.9-89.0.0.0.1ELxenU
kernel headers for version 2.6.9-89.0.0.0.1ELxenU were not found...
Any help would be appreciated.
Thanks and regards
Anil

Thanks Avi for the pointer.
I did a 'sudo -su ' and ran 'rpm -ivh kernel-xenU-devel-2.6.9-89.0.0.0.1.EL.i686.rpm' and it went through successfully.
But then when I launched VMPlayer, a popup came up saying " Before you run VMWare, several modules must be compiled and loaded into the running kernel.". I clicked on 'Install' to continue.
Another popup came up saying "Failed to run /usr/bin/vmware-gksu '/usr/bin/vmware-modconfig' --icon='vmware-player' --appname='VMware' --gcc='/usr/bin/gcc' --headers='/lib/modules/2.6.9-89.0.0.0.1.ELxenU/build/include' --gcc-ignore-minor as user root. Failed to exec new process. No such file or directory."
And then I had to exit.
This is the log contents when VMPlayer was run :
Dec 01 18:27:11.567: app-3086636736| Log for VMware Workstation pid=11013 version=7.1.3 build=build-324285 option=Release
Dec 01 18:27:11.567: app-3086636736| The process is 32-bit.
Dec 01 18:27:11.567: app-3086636736| Host codepage=UTF-8 encoding=UTF-8
Dec 01 18:27:11.567: app-3086636736| Logging to /tmp/vmware-vmotamar/setup-11013.log
Dec 01 18:27:11.944: app-3086636736| modconf query interface initialized
Dec 01 18:27:11.945: app-3086636736| modconf library initialized
Dec 01 18:27:11.979: app-3086636736| Your GCC version: 3.4
Dec 01 18:27:11.989: app-3086636736| Your GCC version: 3.4
Dec 01 18:27:12.011: app-3086636736| Your GCC version: 3.4
Dec 01 18:27:12.036: app-3086636736| Your GCC version: 3.4
Dec 01 18:27:12.058: app-3086636736| Your GCC version: 3.4
Dec 01 18:27:12.104: app-3086636736| Trying to find a suitable PBM set for kernel 2.6.9-89.0.0.0.1.ELxenU.
Dec 01 18:27:12.108: app-3086636736| Trying to find a suitable PBM set for kernel 2.6.9-89.0.0.0.1.ELxenU.
Dec 01 18:27:12.113: app-3086636736| Trying to find a suitable PBM set for kernel 2.6.9-89.0.0.0.1.ELxenU.
Dec 01 18:27:12.117: app-3086636736| Trying to find a suitable PBM set for kernel 2.6.9-89.0.0.0.1.ELxenU.
Dec 01 18:27:12.121: app-3086636736| Trying to find a suitable PBM set for kernel 2.6.9-89.0.0.0.1.ELxenU.
Dec 01 18:27:12.146: app-3086636736| Trying to find a suitable PBM set for kernel 2.6.9-89.0.0.0.1.ELxenU.
Dec 01 18:27:12.150: app-3086636736| Trying to find a suitable PBM set for kernel 2.6.9-89.0.0.0.1.ELxenU.
Dec 01 18:27:12.154: app-3086636736| Trying to find a suitable PBM set for kernel 2.6.9-89.0.0.0.1.ELxenU.
Dec 01 18:27:12.158: app-3086636736| Trying to find a suitable PBM set for kernel 2.6.9-89.0.0.0.1.ELxenU.
Dec 01 18:27:12.162: app-3086636736| Trying to find a suitable PBM set for kernel 2.6.9-89.0.0.0.1.ELxenU.
Dec 01 18:27:12.168: app-3086636736| Your GCC version: 3.4
Dec 01 18:27:12.184: app-3086636736| Your GCC version: 3.4
Dec 01 18:27:19.720: app-3086636736| Trying to find a suitable PBM set for kernel 2.6.9-89.0.0.0.1.ELxenU.
Dec 01 18:27:19.725: app-3086636736| Trying to find a suitable PBM set for kernel 2.6.9-89.0.0.0.1.ELxenU.
Dec 01 18:27:19.729: app-3086636736| Trying to find a suitable PBM set for kernel 2.6.9-89.0.0.0.1.ELxenU.
Dec 01 18:27:19.733: app-3086636736| Trying to find a suitable PBM set for kernel 2.6.9-89.0.0.0.1.ELxenU.
Dec 01 18:27:19.738: app-3086636736| Trying to find a suitable PBM set for kernel 2.6.9-89.0.0.0.1.ELxenU.
Dec 01 18:27:19.745: app-3086636736| Your GCC version: 3.4
Dec 01 18:27:19.764: app-3086636736| Your GCC version: 3.4
Dec 01 18:27:19.807: app-3086636736| Trying to find a suitable PBM set for kernel 2.6.9-89.0.0.0.1.ELxenU.
Dec 01 18:27:19.812: app-3086636736| Trying to find a suitable PBM set for kernel 2.6.9-89.0.0.0.1.ELxenU.
Dec 01 18:27:19.817: app-3086636736| Trying to find a suitable PBM set for kernel 2.6.9-89.0.0.0.1.ELxenU.
Dec 01 18:27:19.822: app-3086636736| Trying to find a suitable PBM set for kernel 2.6.9-89.0.0.0.1.ELxenU.
Dec 01 18:27:19.827: app-3086636736| Trying to find a suitable PBM set for kernel 2.6.9-89.0.0.0.1.ELxenU.
Dec 01 18:27:19.827: app-3086636736| Relaunching with /usr/bin/vmware-gksu '/usr/bin/vmware-modconfig' icon='vmware-player' appname='VMware' gcc='/usr/bin/gcc' headers='/lib/modules/2.6.9-89.0.0.0.1.ELxenU/build/include' --gcc-ignore-minor
Could you please suggest?

Vmware Player in Arch Linux and RFKILL

Hi,
I am a newbie to Arch Linux, I have installed Vmware player in Arch but it doesn't seem to be running. I have followed the guide in the Arch Wiki. This is the output of the related commands.
[root@swallowed Desktop]# uname -r
2.6.35-ARCH
[root@swallowed Desktop]# vmware-installer -l
No protocol specified
No protocol specified
Product Name Product Version
====================== ====================
vmware-player 3.1.2.301548
[root@swallowed Desktop]# /etc/rc.d/vmware
vmware vmware.d/
[root@swallowed Desktop]# /etc/rc.d/vmware start
Starting VMware services:
VMware USB Arbitrator done
Virtual machine monitor failed
Virtual machine communication interface failed
VM communication interface socket family failed
Blocking file system failed
Virtual ethernet failed
[root@swallowed Desktop]# vmplayer
No protocol specified
xprop: unable to open display ':0.0'
GLib-GIO:ERROR:gdbusconnection.c:2270:initable_init: assertion failed: (connection->initialization_error == NULL)
No protocol specified
xprop: unable to open display ':0.0'
GLib-GIO:ERROR:gdbusconnection.c:2270:initable_init: assertion failed: (connection->initialization_error == NULL)
No protocol specified
(vmware-modconfig:5602): Gtk-WARNING **: cannot open display: :0.0
[root@swallowed Desktop]#
Does anyone know how to resolve this problem?
Besides, I installed Arch on Dell Studio XPS 1640 and I don't seem tobe able to remove the hard block on my Wifi card. I installed all the driver already. This is the output of commands.
[root@swallowed Desktop]# rfkill list
0: dell-wifi: Wireless LAN
Soft blocked: yes
Hard blocked: yes
1: phy0: Wireless LAN
Soft blocked: no
Hard blocked: yes
[root@swallowed Desktop]# rfkill unblock 0
[root@swallowed Desktop]# rfkill list
0: dell-wifi: Wireless LAN
Soft blocked: yes
Hard blocked: yes
1: phy0: Wireless LAN
Soft blocked: no
Hard blocked: yes
[root@swallowed Desktop]#
I even try to include this inside modprobe but it doesn't work.
[root@swallowed Desktop]# cat /etc/modprobe.d/modprobe.conf
# /etc/modprobe.d/modprobe.conf (for v2.6 kernels)
options ath_pci rfkill=0
options snd-pcsp index=2
options iwlcore led_mode=1
Thank you so much!

vmware products need patching for kernel 2.6.35 - you didn't mention if you did that or not, but if you didn't, that would explain why vmware is not starting.

[Solved] VMWare Player 4.0.0 and kernel 3.1.4-1-ARCH

Similar Messages

Maybe you are looking for