Palaco, essa dica foi quente! Valeu!
Agora está tudo funcionando!
Aqui está o meu bash para os que tiverem o mesmo problema:
edson@edson:~/Downloads$ sudo /usr/bin/vmware-config.pl
Password:
Making sure services for VMware Player are stopped.
Stopping VMware services:
Virtual machine monitor done
Blocking file system: done
Bridged networking on /dev/vmnet0 done
Host network detection done
Bridged networking on /dev/vmnet2 done
Virtual ethernet done
Configuring fallback GTK+ 2.4 libraries.
In which directory do you want to install the theme icons?
[/usr/share/icons] /usr/share/icons
What directory contains your desktop menu entry files? These files have a
.desktop file extension. [/usr/share/applications] /usr/share/applications
In which directory do you want to install the application's icon?
[/usr/share/pixmaps] /usr/share/pixmaps
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] 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.20-16-generic/build/include] /lib/modules/2.6.20-16-generic/build/include
Extracting the sources of the vmmon module.
Building the vmmon module.
Using 2.6.x kernel build system.
make: Entering directory `/tmp/vmware-config0/vmmon-only'
make -C /lib/modules/2.6.20-16-generic/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. modules
make[1]: Entering directory `/usr/src/linux-headers-2.6.20-16-generic'
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
CC [M] /tmp/vmware-config0/vmmon-only/common/vmx86.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 1 modules
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-headers-2.6.20-16-generic'
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.
Extracting the sources of the vmblock module.
Building the vmblock module.
Using 2.6.x kernel build system.
make: Entering directory `/tmp/vmware-config0/vmblock-only'
make -C /lib/modules/2.6.20-16-generic/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. modules
make[1]: Entering directory `/usr/src/linux-headers-2.6.20-16-generic'
CC [M] /tmp/vmware-config0/vmblock-only/linux/block.o
CC [M] /tmp/vmware-config0/vmblock-only/linux/control.o
CC [M] /tmp/vmware-config0/vmblock-only/linux/dbllnklst.o
CC [M] /tmp/vmware-config0/vmblock-only/linux/dentry.o
CC [M] /tmp/vmware-config0/vmblock-only/linux/file.o
CC [M] /tmp/vmware-config0/vmblock-only/linux/filesystem.o
CC [M] /tmp/vmware-config0/vmblock-only/linux/inode.o
CC [M] /tmp/vmware-config0/vmblock-only/linux/module.o
CC [M] /tmp/vmware-config0/vmblock-only/linux/stubs.o
CC [M] /tmp/vmware-config0/vmblock-only/linux/super.o
LD [M] /tmp/vmware-config0/vmblock-only/vmblock.o
Building modules, stage 2.
MODPOST 1 modules
CC /tmp/vmware-config0/vmblock-only/vmblock.mod.o
LD [M] /tmp/vmware-config0/vmblock-only/vmblock.ko
make[1]: Leaving directory `/usr/src/linux-headers-2.6.20-16-generic'
cp -f vmblock.ko ./../vmblock.o
make: Leaving directory `/tmp/vmware-config0/vmblock-only'
The module loads perfectly in the running kernel.
This program previously created the file /dev/parport1, and was about to remove
it. Somebody else apparently did it already.
This program previously created the file /dev/parport2, and was about to remove
it. Somebody else apparently did it already.
This program previously created the file /dev/parport3, and was about to remove
it. Somebody else apparently did it already.
This program previously created the file /dev/vmnet0, and was about to remove
it. Somebody else apparently did it already.
This program previously created the file /dev/vmnet2, 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) [no] no
Do you want networking for your virtual machines? (yes/no/help) [yes] yes
This program previously created the file /dev/vmnet1, and was about to remove
it. Somebody else apparently did it already.
This program previously created the file /dev/vmnet3, and was about to remove
it. Somebody else apparently did it already.
This program previously created the file /dev/vmnet4, and was about to remove
it. Somebody else apparently did it already.
This program previously created the file /dev/vmnet5, and was about to remove
it. Somebody else apparently did it already.
This program previously created the file /dev/vmnet6, and was about to remove
it. Somebody else apparently did it already.
This program previously created the file /dev/vmnet7, and was about to remove
it. Somebody else apparently did it already.
This program previously created the file /dev/vmnet8, and was about to remove
it. Somebody else apparently did it already.
This program previously created the file /dev/vmnet9, and was about to remove
it. Somebody else apparently did it already.
Would you prefer to modify your existing networking configuration using the
wizard or the editor? (wizard/editor/help) [wizard] editor
The following virtual networks have been defined:
. vmnet0 is bridged to ath0
. vmnet2 is bridged to eth0
Do you wish to make any changes to the current virtual networks settings?
(yes/no) [no] yes
Which virtual network do you wish to configure? (0-99) 0
The network vmnet0 has been reserved for a bridged network. You may change it,
but it is highly recommended that you use it as a bridged network. Are you
sure you want to modify it? (yes/no) [no] yes
What type of virtual network do you wish to set vmnet0?
(bridged,hostonly,nat,none) [bridged] nat
Removing a bridged network for vmnet0.
Configuring a NAT network for vmnet0.
Do you want this program to probe for an unused private subnet? (yes/no/help)
[yes] yes
Probing for an unused private subnet (this can take some time)...
The subnet 192.168.43.0/255.255.255.0 appears to be unused.
The following virtual networks have been defined:
. vmnet0 is a NAT network on private subnet 192.168.43.0.
. vmnet2 is bridged to eth0
Do you wish to make additional changes to the current virtual networks
settings? (yes/no) [yes] yes
Which virtual network do you wish to configure? (0-99) 2
What type of virtual network do you wish to set vmnet2?
(bridged,hostonly,nat,none) [bridged] nat
Removing a bridged network for vmnet2.
Configuring a NAT network for vmnet2.
Do you want this program to probe for an unused private subnet? (yes/no/help)
[yes] yes
Probing for an unused private subnet (this can take some time)...
The subnet 172.16.218.0/255.255.255.0 appears to be unused.
The following virtual networks have been defined:
. vmnet0 is a NAT network on private subnet 192.168.43.0.
. vmnet2 is a NAT network on private subnet 172.16.218.0.
Do you wish to make additional changes to the current virtual networks
settings? (yes/no) [yes] no
Extracting the sources of the vmnet module.
Building the vmnet module.
Using 2.6.x kernel build system.
make: Entering directory `/tmp/vmware-config0/vmnet-only'
make -C /lib/modules/2.6.20-16-generic/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. modules
make[1]: Entering directory `/usr/src/linux-headers-2.6.20-16-generic'
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
SHIPPED /tmp/vmware-config0/vmnet-only/smac_linux.x386.o
LD [M] /tmp/vmware-config0/vmnet-only/vmnet.o
Building modules, stage 2.
MODPOST 1 modules
WARNING: could not find /tmp/vmware-config0/vmnet-only/.smac_linux.x386.o.cmd for /tmp/vmware-config0/vmnet-only/smac_linux.x386.o
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-headers-2.6.20-16-generic'
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:
Virtual machine monitor done
Blocking file system: done
Virtual ethernet done
Host-only networking on /dev/vmnet0 (background) done
DHCP server on /dev/vmnet0 done
NAT service on /dev/vmnet0 done
Host network detection done
Host-only networking on /dev/vmnet2 (background) done
DHCP server on /dev/vmnet2 done
NAT service on /dev/vmnet2 done
The configuration of VMware Player 2.0.0 build-45731 for Linux for this running
kernel completed successfully.
You can now run VMware Player by invoking the following command:
"/usr/bin/vmplayer".
Enjoy,
--the VMware team
Abraços!
Edson