[opensuse-factory] Kernel 2.6.36 & VMware
Hi everybody, Just a heads up in case somebody relies on VMware and is 'toying' with Factory: Kernel 2.6.36-rc3 hit Factory these days and VMware is not yet able to cope with the latest changes; the various modules fail to build (again). So in case you require vmware to work, better stay a few more days with the 2.6.34 kernel. Probably not too long to wait until an update appears. Dominique -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
On 20/09/10 11:25, Dominique Leuenberger wrote:
Hi everybody,
Just a heads up in case somebody relies on VMware and is 'toying' with Factory:
Kernel 2.6.36-rc3 hit Factory these days and VMware is not yet able to cope with the latest changes; the various modules fail to build (again).
So in case you require vmware to work, better stay a few more days with the 2.6.34 kernel. Probably not too long to wait until an update appears.
Dominique
The only change ioctl is now unlocked_ioctl in 2.6.36-rc3 onwards. slipstream:/usr/src/vboxdrv-3.2.8 # grep -rn unlocked_ioctl * linux/SUPDrv-linux.c:207: unlocked_ioctl: VBoxDrvLinuxIOCtl, # lsmod|grep vbox vboxnetadp 4915 0 vboxnetflt 14241 0 vboxdrv 1786307 2 vboxnetadp,vboxnetflt Regards Sid. -- Sid Boyce ... Hamradio License G3VBV, Licensed Private Pilot Emeritus IBM/Amdahl Mainframes and Sun/Fujitsu Servers Tech Support Senior Staff Specialist, Cricket Coach Microsoft Windows Free Zone - Linux used for all Computing Tasks -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
On 21/09/10 11:16, Sid Boyce wrote:
On 20/09/10 11:25, Dominique Leuenberger wrote:
Hi everybody,
Just a heads up in case somebody relies on VMware and is 'toying' with Factory:
Kernel 2.6.36-rc3 hit Factory these days and VMware is not yet able to cope with the latest changes; the various modules fail to build (again).
So in case you require vmware to work, better stay a few more days with the 2.6.34 kernel. Probably not too long to wait until an update appears.
Dominique
The only change ioctl is now unlocked_ioctl in 2.6.36-rc3 onwards. slipstream:/usr/src/vboxdrv-3.2.8 # grep -rn unlocked_ioctl * linux/SUPDrv-linux.c:207: unlocked_ioctl: VBoxDrvLinuxIOCtl, # lsmod|grep vbox vboxnetadp 4915 0 vboxnetflt 14241 0 vboxdrv 1786307 2 vboxnetadp,vboxnetflt
Regards Sid.
For VirtualBox, after the change "/etc/init.d/vboxdrv setup" builds and installs the kernel modules. The NVidia driver is fixed in the Beta 260.19.06, 256.xx will not be fixed. I couldn't find out why the module build in 256.xx failed as nv.c has #if defined(HAVE_UNLOCKED_IOCTL) .unlocked_ioctl = nv_kern_unlocked_ioctl, #endif I had to change the preceding line to .unlocked_ioctl = nv_kern_ioctl, Then "./nvidia-installer" in the NVIDIA-Linux-x86_64-256.52 directory or "make install in the "NVIDIA-Linux-x86_64-256.52/kernel" directory builds and install the module. Regards Sid. -- Sid Boyce ... Hamradio License G3VBV, Licensed Private Pilot Emeritus IBM/Amdahl Mainframes and Sun/Fujitsu Servers Tech Support Senior Staff Specialist, Cricket Coach Microsoft Windows Free Zone - Linux used for all Computing Tasks -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
On Mon, 2010-09-20 at 12:25 +0200, Dominique Leuenberger wrote:
Hi everybody,
Just a heads up in case somebody relies on VMware and is 'toying' with Factory:
Kernel 2.6.36-rc3 hit Factory these days and VMware is not yet able to cope with the latest changes; the various modules fail to build (again).
So in case you require vmware to work, better stay a few more days with the 2.6.34 kernel. Probably not too long to wait until an update appears.
I just started my first virtual machine in vmware 7.1.1 running on a 2.6.36 kernel. attached the patch I just spun up. It does not fully work backwards compatible, but is good enough for us now I think. How to apply (as root) cd /usr/lib/vmware/modules/source tar xf vmware.tar cd vmware-only patch -p1 < ~/patch/to/my/file.patch cd .. tar cf vmmon.tar vmmon-only Then start vmware 7.1.1, provide the root pass and it will succeed building the vmmon module and allow you to start the machine. (vsock.ko seems not to build yet... but it's not mandatory to start a machine... i'll have a look at that later on). Dominique
participants (2)
-
Dominique Leuenberger -
Sid Boyce