* The alsasound initscript is now provided by alsa-utils
* instead of alsa-driver for compatibility with kernel-sources
* which provide ALSA internally.
* To take advantage of this, and automate the process of
* loading and unloading the ALSA sound drivers as well as
* storing and restoring sound-card mixer levels you should
* add alsasound to the boot runlevel. You can do this as
* root like so:
* # rc-update add alsasound boot
* You will also need to edit the file /etc/modules.d/alsa
* and run modules-update. You can do this like so:
* # nano -w /etc/modules.d/alsa && modules-update
Making sure services for VMware Workstation are stopped.
* Caching service dependencies ... [ ok ] * WARNING: vmware has not yet been started.
You must read and accept the End User License Agreement to continue.
Press enter to display it.
Do you accept? (yes/no) y
Thank you.
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 Workstation 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] y
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.16-gentoo-r9/build/include]
Extracting the sources of the vmmon module.
Building the vmmon module.
Building for 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.16-gentoo-r9/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. modules
make[1]: Entering directory `/usr/src/linux-2.6.16-gentoo-r9'
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: command line option "-Wstrict-prototypes" is valid for C/ObjC but not for C++
cc1plus: warning: command line option "-Wdeclaration-after-statement" is valid for C/ObjC but not for C++
cc1plus: warning: command line option "-Wstrict-prototypes" is valid for C/ObjC but not for C++
cc1plus: warning: command line option "-ffreestanding" 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.16-gentoo-r9'
cp -f vmmon.ko ./../vmmon.o
make: Leaving directory `/tmp/vmware-config0/vmmon-only'
The module loads perfectly in the running kernel.
Do you want networking for your virtual machines? (yes/no/help) [yes] y
Configuring a bridged network for vmnet0.
The following bridged networks have been defined:
All your ethernet interfaces are already bridged.
Do you want to be able to use NAT networking in your virtual machines? (yes/no)
[yes] y
Configuring a NAT network for vmnet8.
Do you want this program to probe for an unused private subnet? (yes/no/help)
[yes] y
Probing for an unused private subnet (this can take some time)...
The subnet 192.168.118.0/255.255.255.0 appears to be unused.
The following NAT networks have been defined:
Do you wish to configure another NAT network? (yes/no) [no] n
Do you want to be able to use host-only networking in your virtual machines?
[yes] y
Configuring a host-only network for vmnet1.
Do you want this program to probe for an unused private subnet? (yes/no/help)
[yes] y
Probing for an unused private subnet (this can take some time)...
The subnet 172.16.33.0/255.255.255.0 appears to be unused.
The following host-only networks have been defined:
Do you wish to configure another host-only network? (yes/no) [no] n
Extracting the sources of the vmnet module.
Building the vmnet module.
Building for 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.16-gentoo-r9/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. modules
make[1]: Entering directory `/usr/src/linux-2.6.16-gentoo-r9'
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.16-gentoo-r9'
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 [ !! ] * Virtual ethernet [ !! ] * 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 Workstation 5.5.1 build-19175 for Linux for this
running kernel completed successfully.
You can now run VMware Workstation by invoking the following command:
"/opt/vmware/workstation/bin/vmware".
Enjoy,
--the VMware team
remove all traces of vmware you will need to remove the files
* in /etc/vmware/, /etc/init.d/vmware, /lib/modules/*/misc/vm*.o,
* and .vmware/ in each users home directory. Don't forget to rmmod the
* vm* modules, either.