VMware Communities
birdie
Expert
Expert

VMWare 6.5 modules do not compile for Linux Kernel 2.6.27

VMWare 6.5 modules do not compile under host with Linux Kernel 2.6.27[/b].

Are patches already available?

There are too many compilation problems like:

In file included from /tmp/vmware-root/modules/vmmon-only/linux/vmhost.h:27,

from /tmp/vmware-root/modules/vmmon-only/linux/driver.c:121:

/tmp/vmware-root/modules/vmmon-only/./include/compat_semaphore.h:23:27: error: asm/semaphore.h: No such file or directory

/tmp/vmware-root/modules/vmmon-only/./include/x86paging.h:76:1: warning: "PTE_PFN_MASK" redefined

/tmp/vmware-root/modules/vmmon-only/linux/hostif.c: In function ‘HostIF_SetFastClockRate’:

/tmp/vmware-root/modules/vmmon-only/linux/hostif.c:3580: error: implicit declaration of function ‘kill_proc’

Of course, VMWare modules do not compile under kernel 2.6.27 (Has ever been a new kernel release which didn't break VMWare modules? Smiley Wink ).

Message was edited by: birdie

Reply
0 Kudos
16 Replies
birdie
Expert
Expert

Up.

Reply
0 Kudos
wila
Immortal
Immortal

Hi,

Have a look here for a work around and background info (VMware is working on it)

--

Wil

| Author of Vimalin. The virtual machine Backup app for VMware Fusion, VMware Workstation and Player |
| More info at vimalin.com | Twitter @wilva
Reply
0 Kudos
birdie
Expert
Expert

That problem is unrelated.

VMWare modules do not compile under 2.6.27 kernel - that's all.

Reply
0 Kudos
wila
Immortal
Immortal

Hmm.. Ok, in that case i guess your only alternative is using the open VMware Tools as those are usually ahead of the normal tools version or you could try to patch it yourself.

--

Wil

| Author of Vimalin. The virtual machine Backup app for VMware Fusion, VMware Workstation and Player |
| More info at vimalin.com | Twitter @wilva
Reply
0 Kudos
birdie
Expert
Expert

I was talking about host, not guest.

Reply
0 Kudos
BugMeNot22222
Contributor
Contributor

Reply
0 Kudos
birdie
Expert
Expert

Thanks for 5.5.x and 6.0.x but the question as for 6.5.0 remains Smiley Sad

Reply
0 Kudos
Richard_Fish
Enthusiast
Enthusiast

I just let workstation do it's thing for 2.6.27. Even though this is with Gentoo's patchset, there is nothing in there that modifies semaphore.h or adds a kill_proc declaration. Are you sure you have the correct kernel headers installed for 2.6.27? For reference, my setup.log contains:

Extracting the sources of the vmmon module.

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.27-gentoo/build/include CC=/usr/bin/gcc GREP=/usr/bin/make IS_GCC_3=no VMCCVER=4.3.2

The vmmon module loads perfectly in the running kernel.

HTH

Edit: FYI, this is on x86_64.

Reply
0 Kudos
bofh_wannabe
Contributor
Contributor

Modules for WS-6.5 compile fine here, kernel 2.6.27.2.

I tried to recompile them with :

"/usr/lib/vmware/bin/vmware-modconfig-console --build-mod"

and I got this error:

"Unable to initialize installer database."

So, I just ran vmware as root, it compiled and inserted the modules, and started Vmware services and Workstation.

lsmod | grep vm

vmnet 39040 13

vmblock 12772 3

vmci 50452 0

vmmon 68976 0

It compiled vsock module too, but it didn't insert it into the kernel.

Reply
0 Kudos
birdie
Expert
Expert

Answering your question:

cd /usr/src/linux-2.6.27/include

grep -R kill_proc .

./linux/sched.h:extern int kill_proc_info(int, struct siginfo *, pid_t);

Linux kernel 2.6.27 does not have a definition for the kill_proc function. I'm not even sure if you are using a vanilla 2.6.27 kernel or/and building against it.

vmmon/linux/hostif.c depends on that function:

} else {

if (linuxState.fastClockThread) {

kill_proc(linuxState.fastClockThread, SIGKILL, 1);

linuxState.fastClockThread = 0;

compat_wait_for_completion(&fastClockExited);

}

}

Reply
0 Kudos
Richard_Fish
Enthusiast
Enthusiast

Oops, sorry for the misdirection. What do you get from:

# locate vmmon.tar
/usr/lib64/vmware/modules/source/vmmon.tar
# strings /usr/lib64/vmware/modules/source/vmmon.tar | grep kill_proc
* Since 2.6.27-rc2 kill_proc() is gone... Replacement (GPL-only!)
#define compat_kill_pid(pid, sig, flag) kill_proc(pid, sig, flag)

This is with workstation build -118166, installed from the .bundle.

birdie
Expert
Expert

$ strings /usr/lib/vmware/modules/source/vmmon.tar | grep kill_proc

kill_proc(linuxState.fastClockThread, SIGKILL, 1);

... VMware-Workstation-6.5.0-110068.i386

Damn, I am running VMWare RC!

It's all working now, I'm terribly sorry for this цhole misleading topic.

Reply
0 Kudos
rgallovarese
Contributor
Contributor

i am running slackware

root@mamma:~# vmware

Logging to /tmp/vmware-root/setup-4251.log

Unable to initialize installer database

trings /usr/lib/vmware/modules/source/vmmon.tar | grep kill_proc

  • Since 2.6.27-rc2 kill_proc() is gone... Replacement (GPL-only!)

#define compat_kill_pid(pid, sig, flag) kill_proc(pid, sig, flag)

root@mamma:~#

root@mamma:~# cat /tmp/vmware-root/setup-4251.log

Dec 04 11:26:53.578: app| Log for VMware Workstation pid=4251 version=6.5.0 build=build-118166 option=Release

Dec 04 11:26:53.578: app| Host codepage=ISO-8859-1 encoding=ISO-8859-1

Dec 04 11:26:53.578: app| Logging to /tmp/vmware-root/setup-4251.log

root@mamma:~# uname -a

Linux mamma 2.6.27.7 #3 SMP PREEMPT Sun Nov 30 10:36:09 CET 2008 i686 Intel(R) Core(TM)2 CPU 6400 @ 2.13GHz GenuineIntel GNU/Linux

root@mamma:~# ls Desktop/download2.vmware.com/VMware-Workstation-6.5.0-118166.i386.bundle

Desktop/download2.vmware.com/VMware-Workstation-6.5.0-118166.i386.bundle*

the same happens with VMware-Workstation-6.5.1-126130.i386.bundle

please I beg you

help

Reply
0 Kudos
h2-2
Contributor
Contributor

Yes, I hit the same problem[/url], to solve: rm -rf /etc/vmware

Then try starting vmware again, you might need to remove that after you uninstall it, then reinstall vmware, and it's all fine.

Reply
0 Kudos
angthuonimo
Contributor
Contributor

This is PATHETIC. This bug has been known for at least at year and it's still happening in the very latest Vmware Player. Are these guys passing their bugs around on sticky notes or what? If you can't organise yourselves any better than this, get the hell out of the industry.

Adrian.

Reply
0 Kudos
angthuonimo
Contributor
Contributor

Look:

http://www.insecure.ws/2008/10/20/vmware-specific-specific-55x-and-kernel-2627

Even independant bloggers are further ahead at developing your product than your own staff and you're still charging money for it. Isn't that embarrassing?

Adrian.

Reply
0 Kudos