You are not logged in.
After Upgrade to Kernel 2.6.35.6-1 the vsock Module don't load anymore.
Recompiling the modules shows this Message.
Using 2.6.x kernel build system.
make: Entering directory `/tmp/vmware-root/modules/vsock-only'
make -C /lib/modules/2.6.35-ARCH/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. \
MODULEBUILDDIR= modules
make[1]: Entering directory `/usr/src/linux-2.6.35-ARCH'
CC [M] /tmp/vmware-root/modules/vsock-only/linux/af_vsock.o
/tmp/vmware-root/modules/vsock-only/linux/af_vsock.c:312:4: Warnung: Initialisierung von inkompatiblem Zeigertyp
/tmp/vmware-root/modules/vsock-only/linux/af_vsock.c:359:4: Warnung: Initialisierung von inkompatiblem Zeigertyp
/tmp/vmware-root/modules/vsock-only/linux/af_vsock.c: In Funktion »VSockVmciStreamConnect«:
/tmp/vmware-root/modules/vsock-only/linux/af_vsock.c:3163:4: Warnung: case value »255« not in enumerated type »socket_state«
CC [M] /tmp/vmware-root/modules/vsock-only/linux/notify.o
CC [M] /tmp/vmware-root/modules/vsock-only/linux/stats.o
CC [M] /tmp/vmware-root/modules/vsock-only/linux/util.o
CC [M] /tmp/vmware-root/modules/vsock-only/linux/vsockAddr.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-2.6.35-ARCH'
make -C $PWD SRCROOT=$PWD/. \
MODULEBUILDDIR= postbuild
make[1]: Entering directory `/tmp/vmware-root/modules/vsock-only'
make[1]: »postbuild« ist bereits aktualisiert.
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
When starting " VM communication interface socket family" insmod wants to load the vsock module and do this and do this ...
With Kernel 2.6.35 there was also a problem with compiling vmware modules. I found this Patch and fixed the problem.
Anyone this problem or a soulution?
"Man kann ein Problem nicht mit den gleichen Denkstrukturen lösen, die zu seiner Entstehung beigetragen haben." (Albert Einstein)
"A problem cannot be solve at the same level of thinking at which it was created." (Albert Einstein)
Offline
I hit the same problem today. When the VMware modules build got stuck at:
Starting VMware services:
VMware USB Arbitrator done
Virtual machine monitor done
Virtual machine communication interface done
VM communication interface socket family
I opened a console and ran "top". I saw insmod apparently looping (100% CPU), and couldn't kill it. This also happened during boot, hanging the boot process. I used single user mode to disable vmware in /etc/rc.conf and was then able to boot.
Offline
I don't use VMWare but there is apparently a problem with the 2.6.35.6 kernel26-headers package that is also affecting VirtualBox and catalyst.
Offline
As I just reported in flyspray, installing the -2 version of kernel26-headers and recompiling the vmware modules fixes this issue for the VMware modules:
https://bugs.archlinux.org/task/20972
Last edited by nogoma (2010-09-28 19:30:31)
-nogoma
---
Code Happy, Code Ruby!
http://www.last.fm/user/nogoma/
Offline
Confirmed. I no longer get the insmod loop, and VMware works.
Offline
With kernel 2.6.35.6-2 from testing repo VMWare is working fine.
Offline
Fix confirmed here to, although now its 2.6.35.7
This affected Virtualbox as well I believe, though the error was a but less clean.
Froze the whole system
Last edited by zhentar (2010-09-30 00:31:02)
Offline