VMWARE not working after latest kernel upgrade [SOLVED]

Question

I've done a kernel update and after rebooting VMWare was not working. That's "standard", I figured, because I have a new kernel.
So, I run the any_any patch (as usual) to re-configure the VM to the new kernel but this time no joy
Is there anyone else having the same problem?
The error seems to be here:
In file included from /tmp/vmware-config0/vmmon-only/common/hostKernel.h:56,
from /tmp/vmware-config0/vmmon-only/common/task.c:24:
include/asm/page.h: In function 'pte_t native_make_pte(long unsigned int)':
include/asm/page.h:112: error: expected primary-expression before ')' token
include/asm/page.h:112: error: expected ';' before '{' token
include/asm/page.h:112: error: expected primary-expression before '.' token
include/asm/page.h:112: error: expected `;' before '}' token
make[2]: *** [/tmp/vmware-config0/vmmon-only/common/task.o] Error 1
make[1]: *** [_module_/tmp/vmware-config0/vmmon-only] Error 2
make[1]: Leaving directory `/usr/src/linux-2.6.22-ARCH'
make: *** [vmmon.ko] Error 2
make: Leaving directory `/tmp/vmware-config0/vmmon-only'
Unable to build the vmmon module.
R.
Note: Running /usr/bin/vmware-config.pl is of no help either (same error).
Last edited by ralvez (2007-07-28 13:58:06)

Answer 1

stonecrest wrote:Yes, and the PKGBUILD works;
You'd rather say "I, myself, me, thinks it works".
Because it does not work for many people, including me.
The modules do build with kernel 2.6.22.X, but the network behaviour using bridged networking is extremely clumsy (used to work fine with 2.6.21.X), and shared folders are a pain in the butt- for example whenever I try to copy a file from the guest to a host shared folder, the guest OS (winXP) comes close to totally freezing, and I have to kill explorer to stop the transaction.
Do you call THAT "works"?
IMO the issues with kernel 2.6.22 won't be addressed before a new VMWare version is out... Until then, yeah... the old version/PKGBUILD works...
I'm close to ditching VMWare in favour of VirtualBox, but a couple of VMWare features (mainly related to low level hardware access) still prevent me from doing so.
Last edited by scarecrow (2007-07-29 13:31:51)