VMware 4.0.1 fails to build on SuSE -329 kernels
hi I have come across this problem on my SuSE 8.1 system.l. I have not got it fixed yet but can tell you its related to the latest SuSE kernel or kernel source. I have the following kernel installed: k_deflt-2.4.19-329 matching kernel source should be kernel-source-2.4.19.SuSE-308 with vmware 4.0.1 build 5289 With glibc-2.2.5-184 installed for tests on both kernels. and this combination fails during the build of vmon (see below) but the module reports that it loads pefectly. The end result is that the VMware GUi starts but if you attempt to start a guest OS it will hang. If I install the older kernel k_deflt-2.4.19-274 VMware 4.0 will work ok but I then break NFS between multilple SuSE 8.1 systems which affects other application systems I need. any further suggestions would be most helpful. ------------------------------ Building the vmmon module. make: Entering directory `/tmp/vmware-config0/vmmon-only' make[1]: Entering directory `/tmp/vmware-config0/vmmon-only' make[2]: Entering directory `/tmp/vmware-config0/vmmon-only/driver-2.4.19-4GB' make[2]: Leaving directory `/tmp/vmware-config0/vmmon-only/driver-2.4.19-4GB' make[2]: Entering directory `/tmp/vmware-config0/vmmon-only/driver-2.4.19-4GB' ../linux/hostif.c: In function `HostIF_SemaphoreWait': ../linux/hostif.c:1818: warning: passing arg 1 of `poll_initwait' from incompatible pointer type ../linux/hostif.c:1835: warning: passing arg 1 of `poll_freewait' from incompatible pointer type make[2]: Leaving directory `/tmp/vmware-config0/vmmon-only/driver-2.4.19-4GB' make[1]: Leaving directory `/tmp/vmware-config0/vmmon-only' make: Leaving directory `/tmp/vmware-config0/vmmon-only' The module loads perfectly in the running kernel. Extracting the sources of the vmnet module. Building the vmnet module. make: Entering directory `/tmp/vmware-config0/vmnet-only' make: Leaving directory `/tmp/vmware-config0/vmnet-only' The module loads perfectly in the running kernel. -- Jim Hamilton Perth, Australia
On Fri August 1 2003 1:33 am, Jim Hamilton wrote:
hi
I have come across this problem on my SuSE 8.1 system.l. I have not got it fixed yet but can tell you its related to the latest SuSE kernel or kernel source. I have the following kernel installed:
k_deflt-2.4.19-329
matching kernel source should be
kernel-source-2.4.19.SuSE-308
with vmware 4.0.1 build 5289
With glibc-2.2.5-184 installed for tests on both kernels.
and this combination fails during the build of vmon (see below) but the module reports that it loads pefectly. The end result is that the VMware GUi starts but if you attempt to start a guest OS it will hang.
If I install the older kernel k_deflt-2.4.19-274 VMware 4.0 will work ok but I then break NFS between multilple SuSE 8.1 systems which affects other application systems I need.
any further suggestions would be most helpful.
------------------------------
Building the vmmon module.
make: Entering directory `/tmp/vmware-config0/vmmon-only' make[1]: Entering directory `/tmp/vmware-config0/vmmon-only' make[2]: Entering directory `/tmp/vmware-config0/vmmon-only/driver-2.4.19-4GB' make[2]: Leaving directory `/tmp/vmware-config0/vmmon-only/driver-2.4.19-4GB' make[2]: Entering directory `/tmp/vmware-config0/vmmon-only/driver-2.4.19-4GB' ../linux/hostif.c: In function `HostIF_SemaphoreWait': ../linux/hostif.c:1818: warning: passing arg 1 of `poll_initwait' from incompatible pointer type ../linux/hostif.c:1835: warning: passing arg 1 of `poll_freewait' from incompatible pointer type make[2]: Leaving directory `/tmp/vmware-config0/vmmon-only/driver-2.4.19-4GB' make[1]: Leaving directory `/tmp/vmware-config0/vmmon-only' make: Leaving directory `/tmp/vmware-config0/vmmon-only' The module loads perfectly in the running kernel.
Extracting the sources of the vmnet module.
Building the vmnet module.
make: Entering directory `/tmp/vmware-config0/vmnet-only' make: Leaving directory `/tmp/vmware-config0/vmnet-only' The module loads perfectly in the running kernel.
-- Jim Hamilton Perth, Australia
Jim, I pass on this quote from a response I received to a similar question maybe a week and a half ago, maybe it will assist you. It handled stuff for me trying to get VMWare to recognize my athlon kernel: <quote> cp /boot/vmlinuz.version.h /usr/src/linux/include/linux/version.h cp /boot/vmlinuz.autoconf.h /usr/src/linux/include/linux/autoconf.h Then run the vmware config.pl to compile. All you are doing is getting the header names to match whats running... _____________________________________ John Andersen <endquote> Richard
Richard <rick47@adelphia.net> [Fri, 1 Aug 2003 08:54:47 -0700]:
maybe a week and a half ago, maybe it will assist you. It handled stuff for me trying to get VMWare to recognize my athlon kernel: <quote> cp /boot/vmlinuz.version.h /usr/src/linux/include/linux/version.h cp /boot/vmlinuz.autoconf.h /usr/src/linux/include/linux/autoconf.h
The better way is: - install kernel_source - cd /usr/src/linux - make cloneconfig - make dep And then:
Then run the vmware config.pl to compile.
Philipp
hi All, Thanks for the feedback. the suggestions are not sufficent to bring VMware back up. With the help of some foks on the vmware newsgroups you will need a modified vmon module to compile. These can be found here: ftp://platan.vc.cvut.cz/pub/vmware and pick vmware-any-any-update38 or later. i have used this new code and the vmware now buzzes along nicely once again. SuSE backported epoll patches from 2.5.x to 2.4.x, and while this caused only warning, really bad things happened. The result in vmon is memory corruptions. Hope this helps some others. BR Jim On Sat, 2 Aug 2003 04:20 am, Philipp Thomas wrote:
Richard <rick47@adelphia.net> [Fri, 1 Aug 2003 08:54:47 -0700]:
maybe a week and a half ago, maybe it will assist you. It handled stuff for me trying to get VMWare to recognize my athlon kernel: <quote> cp /boot/vmlinuz.version.h /usr/src/linux/include/linux/version.h cp /boot/vmlinuz.autoconf.h /usr/src/linux/include/linux/autoconf.h
The better way is:
- install kernel_source - cd /usr/src/linux - make cloneconfig - make dep
And then:
Then run the vmware config.pl to compile.
Philipp
-- Jim Hamilton Perth, Australia
participants (3)
-
Jim Hamilton -
Philipp Thomas -
Richard