Installing and configuring app-emulation/vmware-player-1.0.1.19317-r1 on my x86 box went smoothly. The configure step informed me that it needed to build vmmon for my (custom) kernel, and that went without any apparent hitch (note this listing is from my second attempt to get vmware-player working, after a sync and upgrade to -r1 of the ebuild, so I'd already configured networking): ---------------start vmware-config.pl output # /opt/vmware/player/bin/vmware-config.pl Making sure services for VMware Player are stopped. * ERROR: "vmware" has not yet been started. Configuring fallback GTK+ 2.4 libraries. Trying to find a suitable vmmon module for your running kernel. None of the pre-built vmmon modules for VMware Player is suitable for your running kernel. Do you want this program to try to build the vmmon module for your system (you need to have a C compiler installed on your system)? [yes] Using compiler "/usr/bin/gcc". Use environment variable CC to override. What is the location of the directory of C header files that match your running kernel? [/lib/modules/2.6.6/build/include] Extracting the sources of the vmmon module. Building the vmmon module. Building for VMware Player 1.0.x or VMware Workstation 5.5.x. Using 2.6.x kernel build system. make: Entering directory `/tmp/vmware-config0/vmmon-only' make -C /lib/modules/2.6.6/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. modules make[1]: Entering directory `/usr/src/linux-2.6.6' CC [M] /tmp/vmware-config0/vmmon-only/linux/driver.o CC [M] /tmp/vmware-config0/vmmon-only/linux/hostif.o CC [M] /tmp/vmware-config0/vmmon-only/common/cpuid.o CC [M] /tmp/vmware-config0/vmmon-only/common/hash.o CC [M] /tmp/vmware-config0/vmmon-only/common/memtrack.o CC [M] /tmp/vmware-config0/vmmon-only/common/phystrack.o CC [M] /tmp/vmware-config0/vmmon-only/common/task.o cc1plus: warning: "-Wdeclaration-after-statement" is valid for C/ObjC but not for C++ CC [M] /tmp/vmware-config0/vmmon-only/common/vmx86.o CC [M] /tmp/vmware-config0/vmmon-only/vmcore/compat.o CC [M] /tmp/vmware-config0/vmmon-only/vmcore/moduleloop.o LD [M] /tmp/vmware-config0/vmmon-only/vmmon.o Building modules, stage 2. MODPOST CC /tmp/vmware-config0/vmmon-only/vmmon.mod.o LD [M] /tmp/vmware-config0/vmmon-only/vmmon.ko make[1]: Leaving directory `/usr/src/linux-2.6.6' cp -f vmmon.ko ./../vmmon.o make: Leaving directory `/tmp/vmware-config0/vmmon-only' The module loads perfectly in the running kernel. This program previously created the file /dev/vmmon, and was about to remove it. Somebody else apparently did it already. You have already setup networking. Would you like to skip networking setup and keep your old settings as they are? (yes/no) [yes] Extracting the sources of the vmnet module. Building the vmnet module. Building for VMware Player 1.0.x or VMware Workstation 5.5.x. Using 2.6.x kernel build system. make: Entering directory `/tmp/vmware-config0/vmnet-only' make -C /lib/modules/2.6.6/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. modules make[1]: Entering directory `/usr/src/linux-2.6.6' CC [M] /tmp/vmware-config0/vmnet-only/driver.o CC [M] /tmp/vmware-config0/vmnet-only/hub.o CC [M] /tmp/vmware-config0/vmnet-only/userif.o CC [M] /tmp/vmware-config0/vmnet-only/netif.o CC [M] /tmp/vmware-config0/vmnet-only/bridge.o CC [M] /tmp/vmware-config0/vmnet-only/procfs.o CC [M] /tmp/vmware-config0/vmnet-only/smac_compat.o CC [M] /tmp/vmware-config0/vmnet-only/smac_linux.x386.o LD [M] /tmp/vmware-config0/vmnet-only/vmnet.o Building modules, stage 2. MODPOST CC /tmp/vmware-config0/vmnet-only/vmnet.mod.o LD [M] /tmp/vmware-config0/vmnet-only/vmnet.ko make[1]: Leaving directory `/usr/src/linux-2.6.6' cp -f vmnet.ko ./../vmnet.o make: Leaving directory `/tmp/vmware-config0/vmnet-only' The module loads perfectly in the running kernel. * Starting VMware services: [ ok ] * Virtual machine monitor [ ok ] * Virtual ethernet [ ok ] * Bridged networking on /dev/vmnet0 [ ok ] * Host-only networking on /dev/vmnet1 (background) [ ok ] * Host-only networking on /dev/vmnet8 (background) [ ok ] * NAT service on /dev/vmnet8 [ ok ] The configuration of VMware Player 1.0.1 build-19317 for Linux for this running kernel completed successfully. You can now run VMware Player by invoking the following command: "/opt/vmware/player/bin/vmplayer". Enjoy, --the VMware team ---------------end vmware-config.pl output I then added myself to the vmware group, restarted the vmware service: ---------------start vmware restart output # /etc/init.d/vmware restart * Stopping VMware services: [ ok ] * Virtual machine monitor [ ok ] * Bridged networking on /dev/vmnet0 [ ok ] * DHCP server on /dev/vmnet1 [ ok ] * Host-only networking on /dev/vmnet1 [ ok ] * DHCP server on /dev/vmnet8 [ ok ] * NAT service on /dev/vmnet8 [ ok ] * Host-only networking on /dev/vmnet8 [ ok ] * Virtual ethernet [ ok ] * Starting VMware services: [ ok ] * Virtual machine monitor [ ok ] * Virtual ethernet [ ok ] * Bridged networking on /dev/vmnet0 [ ok ] * Host-only networking on /dev/vmnet1 (background) [ ok ] * Host-only networking on /dev/vmnet8 (background) [ ok ] * NAT service on /dev/vmnet8 [ ok ] ---------------start vmware restart output Then I launched vmplayer. Got the following warning to terminal, which looked harmless: $ vmplayer *** attempt to put segment in horiz list twice Up comes the GUI. I've already unzipped Browser-Appliance (downloaded 2006-03-25 from vmware's website). Picked Browser-Appliance.vmx from the file dialog. Up pops a little error dialog: "Error while powering on: Failed to launch peer process."
> location of the directory of C header files that match your running > kernel? [/lib/modules/2.6.6/build/include] We can't support custom kernels and especially not 2.6.6 version.
