Slackware64 multi-lib from AlienBOB 13.1 can't compile VMware Server 2.0.2 b-203138

SCerovec · 07-08-2010, 08:00 AM

Slackware64 multi-lib from AlienBOB 13.1 can't compile VMware Server 2.0.2 build-203138
1. It does run wine 32 bit version ( a package called "64" bit, but there ain't no 64bit wine, right?)
2. It runs 32 bit programs in that wine.
3. It is vanilla 2.6.33.4 kernel 64bit so far.

Shall I go for VirtualBox or can I get VMWare to work any soon?
I already did the
VMware-server-2.0.2-203138-update-2.patch
and got a bit further, but the build of the vmmon just "goes to pieces"?

Code:

make: Entering directory `/tmp/vmware-config3/vmmon-only'
make -C /lib/modules/2.6.33.4/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. modules
make[1]: Entering directory `/usr/src/linux-2.6.33.4'
  CC [M]  /tmp/vmware-config3/vmmon-only/linux/driver.o
In file included from /tmp/vmware-config3/vmmon-only/linux/driver.c:20:
/tmp/vmware-config3/vmmon-only/./include/driver-config.h:35:28: error: linux/autoconf.h: No such file or directory
In file included from /tmp/vmware-config3/vmmon-only/linux/driver.c:31:
/tmp/vmware-config3/vmmon-only/./include/compat_wait.h:78: error: conflicting types for 'poll_initwait'
include/linux/poll.h:70: note: previous declaration of 'poll_initwait' was here
/tmp/vmware-config3/vmmon-only/linux/driver.c: In function 'LinuxDriverSyncCallOnEachCPU':
/tmp/vmware-config3/vmmon-only/linux/driver.c:1424: error: too many arguments to function 'smp_call_function'
/tmp/vmware-config3/vmmon-only/linux/driver.c: In function 'LinuxDriver_Ioctl':
/tmp/vmware-config3/vmmon-only/linux/driver.c:2008: error: too many arguments to function 'smp_call_function'
make[2]: *** [/tmp/vmware-config3/vmmon-only/linux/driver.o] Error 1
make[1]: *** [_module_/tmp/vmware-config3/vmmon-only] Error 2
make[1]: Leaving directory `/usr/src/linux-2.6.33.4'
make: *** [vmmon.ko] Error 2
make: Leaving directory `/tmp/vmware-config3/vmmon-only'
Unable to build the vmmon module.

For more information on how to troubleshoot module-related problems, please 
visit our Web site at "http://www.vmware.com/go/unsup-linux-products" and 
"http://www.vmware.com/go/unsup-linux-tools".

Execution aborted.

bash-4.1#

business_kid · 07-08-2010, 11:01 AM

This appears to be it

Quote:

/tmp/vmware-config3/vmmon-only/./include/driver-config.h:35:28: error: linux/autoconf.h: No such file or directory

/usr/include/linux/autoconf.h sounds like a kernel header. Want to go and check that out?

adamk75 · 07-08-2010, 11:33 AM

In newer kernels, some headers were moved from include/linux/ to include/generated/ . Simply symlinking them to include/linux/ should work.

Adam

bgeddy · 07-08-2010, 02:24 PM

As adamk75 says, this is because certain headers have been moved in the newer kernels. I had this problem with some module building apps. To fix it run this as root:

Code:

cd /usr/src/linux/include/linux && ln -s ../generated/autoconf.h

SCerovec · 07-08-2010, 02:58 PM

the file has been moved since vmware is reldased. symlinkig won't do away with it (as it didn't, i tried that)
i hoped for something like that patch?
as i wrote, i got pretty far from vanilla vmware. the server seems to be falling behind the station package, which seems to be running on s64_13.1 ?

vik · 07-08-2010, 10:25 PM

Unless you have a specific reason for using VMWare server, try VMWare player 3.0.1. It will let you create virtual machines just like VMWare server does, but with a lot less overhead. I used it a few months back when I found out I couldn't run DirectX on a Windows virtual machine with VMWare server and had good luck with it.

Otherwise there should be a patch available somewhere to get it working with your newer kernel...

tallship · 07-09-2010, 05:57 AM

Quote:

Originally Posted by SCerovec

Shall I go for VirtualBox or can I get VMWare to work any soon?

Actually, the only times that Sun VirtualBox hasn't worked out for me is when trying to use it in virtualizing w/pfSense.

I looked and tried everything I could and ended up using VMware instead - problem solved, but wrt that particular BSD firewall system there were networking issues that I just could not overcome in VirtualBox, and at the urging of others, eventually caved and implemented as a VMware applicance.

But otherwise, I still kinda prefer VirtualBox in General.

If you use it I recommend the PUEL, not the OSE version, and also to compile from scratch instead of trying to use the OSE SlackBuild. Just my prefs, and pretty much the consensus I got from HERE

adamk75 · 07-09-2010, 06:04 AM

Maybe I'm missing something, but do either of these files exist?

/lib/modules/2.6.33.4/build/include/linux/autoconf.h
/lib/modules/2.6.33.4/build/include/generated/autoconf.h

Adam

Hangdog42 · 07-09-2010, 06:56 AM

Quote:

Originally Posted by SCerovec

Slackware64 multi-lib from AlienBOB 13.1 can't compile VMware Server 2.0.2 build-203138

At the risk of being obnoxious, you did get the VMware server 64 bit package, didn't you? I've got that build running on my Slackware64 13.1 system by using the same patch you found and making the symlinks in the kernel source (by the way, I followed the process here). Once those two things were done, it compiled fine against the stock hugesmp kernel.

SCerovec · 07-09-2010, 02:54 PM

Quote:

Originally Posted by adamk75

Maybe I'm missing something, but do either of these files exist?

/lib/modules/2.6.33.4/build/include/linux/autoconf.h
/lib/modules/2.6.33.4/build/include/generated/autoconf.h

Adam

To get the later, You have to

Code:

make && make modules && make bzImage

as the sources are made

Code:

make mrproper

so they are "clean"

The former is undergone development and migrated to the later.

The script can be modified to reflect this, but I'm no developer (tried and failed at this)

For the record:
I tried to install the i386 package on a 12.2 32bit system (same machine multi boot) and it wen *flawlessly* -one shot=one kill.

So what gives?
Stevan C.

SCerovec · 07-09-2010, 03:01 PM

Quote:

Originally Posted by Hangdog42

At the risk of being obnoxious, you did get the VMware server 64 bit package, didn't you? I've got that build running on my Slackware64 13.1 system by using the same patch you found and making the symlinks in the kernel source (by the way, I followed the process here). Once those two things were done, it compiled fine against the stock hugesmp kernel.

As far as I understand it, it's about some change in the delay structures of the kernel?

Yes I did download the 64bit version in the title (copy->pasted the build just in case)
And Yes i did "step by step" the HOWTO of the patch You referred to

And then i went even further and maybe (just maybe) i should make a clean start over?
Have no time until next weekend now

Meanwhile a patch or a script would be "life saver"
Do You had BOB's multilib on Your system too when You installed?

Will this require "do this before that" procedure in the end?

Stevan C.

Hangdog42 · 07-10-2010, 08:55 AM

Quote:

As far as I understand it, it's about some change in the delay structures of the kernel?

From VMware's point of view I'm not so sure it is a change in the way the kernel operates as a change in the location of some of the files in the kernel source tree.

Quote:

Do You had BOB's multilib on Your system too when You installed?

Yeah I did. Basically I upgraded 13.0 to 13.1, upgraded the video drivers and then upgraded the multilib packages. Then I re-installed vmware and it bombed out. After doing some research, I found that the move of several files from /usr/src/linux/include/linux to /usr/src/linux/include/generated was the most likely culprit. Making symlinks in /usr/src/linux/include/linux for /usr/src/linux/include/generated/autoconf.h and /usr/src/linux/include/generated/utsrelease.h allowed VMWare to compile (along with applying the patch).

Quote:

Will this require "do this before that" procedure in the end?

I think you have to have the patch applied and the autoconf.h/utsrelease.h links created before things go smoothly.

Quote:

And then i went even further and maybe (just maybe) i should make a clean start over?

I've found that when there is a kernel upgrade, re-installing seems to be the only way to go. That doesn't mean you have to re-create your virtual machines however. Running the vmware-uninstall.pl script and then the following the vmware install procedure does just fine in my case.