Trying to install vmware on my amd64 workstation, ebuild is vmware-workstation-4.0.2-5592-r1.ebuild. After emerging it, and running the /opt/vmware/bin/vmware-config.pl script, it gives me an error as such: 'The kernel defined by this directory of header files does not have the same address space size as your running kernel'. I modified the perl script so it would get past this point, and I get the following compile errors: Building for VMware Workstation 4.x.x make: Entering directory `/tmp/vmware-config5/vmmon-only' make -C /lib/modules/2.6.0-test10-gentoo-r1/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. modules make[1]: Entering directory `/usr/src/linux-2.6.0-test10-gentoo-r1' *** Warning: Overriding SUBDIRS on the command line can cause *** inconsistencies make[2]: `arch/x86_64/kernel/asm-offsets.s' is up to date. CHK include/asm-x86_64/offset.h CC [M] /tmp/vmware-config5/vmmon-only/linux/driver.o /tmp/vmware-config5/vmmon-only/linux/driver.c: In function `register_ioctl32_handlers': /tmp/vmware-config5/vmmon-only/linux/driver.c:195: error: `IOCTLCMD_DO_MEM_MAP' undeclared (first use in this function) /tmp/vmware-config5/vmmon-only/linux/driver.c:195: error: (Each undeclared identifier is reported only once /tmp/vmware-config5/vmmon-only/linux/driver.c:195: error: for each function it appears in.) /tmp/vmware-config5/vmmon-only/linux/driver.c:196: warning: implicit declaration of function `register_ioctl32_conversion' /tmp/vmware-config5/vmmon-only/linux/driver.c: In function `unregister_ioctl32_handlers': /tmp/vmware-config5/vmmon-only/linux/driver.c:217: error: `IOCTLCMD_DO_MEM_MAP' undeclared (first use in this function) /tmp/vmware-config5/vmmon-only/linux/driver.c:218: warning: implicit declaration of function `unregister_ioctl32_conversion' /tmp/vmware-config5/vmmon-only/linux/driver.c: In function `LinuxDriverCheckPadding': /tmp/vmware-config5/vmmon-only/linux/driver.c:3022: warning: unsigned int format, different type arg (arg 2) /tmp/vmware-config5/vmmon-only/linux/driver.c:3022: warning: unsigned int format, different type arg (arg 4) /tmp/vmware-config5/vmmon-only/linux/driver.c:3032: warning: unsigned int format, different type arg (arg 2) /tmp/vmware-config5/vmmon-only/linux/driver.c:3032: warning: unsigned int format, different type arg (arg 4) /tmp/vmware-config5/vmmon-only/linux/driver.c:3040: warning: unsigned int format, different type arg (arg 2) /tmp/vmware-config5/vmmon-only/linux/driver.c:3040: warning: unsigned int format, different type arg (arg 4) /tmp/vmware-config5/vmmon-only/linux/driver.c:3048: warning: unsigned int format, different type arg (arg 2) /tmp/vmware-config5/vmmon-only/linux/driver.c:3048: warning: unsigned int format, different type arg (arg 4) /tmp/vmware-config5/vmmon-only/linux/driver.c:3056: warning: unsigned int format, different type arg (arg 2) /tmp/vmware-config5/vmmon-only/linux/driver.c:3056: warning: unsigned int format, different type arg (arg 4) /tmp/vmware-config5/vmmon-only/linux/driver.c:3064: warning: unsigned int format, different type arg (arg 2) /tmp/vmware-config5/vmmon-only/linux/driver.c:3064: warning: unsigned int format, different type arg (arg 4) /tmp/vmware-config5/vmmon-only/linux/driver.c:3072: warning: unsigned int format, different type arg (arg 2) /tmp/vmware-config5/vmmon-only/linux/driver.c:3072: warning: unsigned int format, different type arg (arg 4) make[2]: *** [/tmp/vmware-config5/vmmon-only/linux/driver.o] Error 1 make[1]: *** [/tmp/vmware-config5/vmmon-only] Error 2 make[1]: Leaving directory `/usr/src/linux-2.6.0-test10-gentoo-r1' make: *** [vmmon.ko] Error 2 make: Leaving directory `/tmp/vmware-config5/vmmon-only' Unable to build the vmmon module. Reproducible: Always Steps to Reproduce: 1. 2. 3.
Uhh, VMware is not an emulator ... don't expect it to work on amd64 unless vmware specifically releases an amd64 version. Since it does require kernel modules, I seriously doubt you'll see this working anytime soon.
theres a reason KEYWORDS is set to "-* x86" :)
For some reason, since the amd64 can do 32bit emulation, I figured vmware would work. Maybe making a chroot would work? Or having to have a module loaded with the kernel is a big deal?
I do not know the internals of Vmware, but if the kernel module has any closed-source portions, or does anything that assumes 32bit (assuming the module is necessary), it's not going to be possible, because you can't load a 32bit object into a 64bit object. But vmware should run in 32bit mode if it didn't require that module...
Quite simply, AMD64 is not a supported platform for VMWare. VMWare's kernel modules are not writtent o be 64-bit clean. You *can* run VMWare on AMD64, provided you're using a 32-bit x86 kernel.
