VMware Server es gratuito y esta basado en la tecnología de virtualización de VMware.  Con este software usted podrá:

• Acelerar los tiempos de despliegue de servidores, armando una máquina virtual y desplegándola múltiples veces.
• Evaluar software en forma simple utilizando máquinas virtuales listas para usar sin necesidad de realizar instalaciones o configuraciones.
• Simplificar el testeo de patching, nuevas aplicaciones y sistemas operativos permitiendo al administrador realizar las pruebas en un ambiente seguro y con la posibilidad de hacer un roll back a un estado anterior utilizando la funcionalidad de snapshot.
• Reubicar sistemas operativos viejos en hardware nuevo.

Como funciona:

Se instala y ejecuta VMware Server como una aplicación en el servidor.  Una delgada línea de virtualización particiona el servidor físico para que pueda ejecutar múltiples máquinas virtuales en simultáneo.  Los recursos del servidor físico son tratados como un pool uniforme de recursos que pueden ser tomados por las máquinas virtuales en forma controlada.

VMware Server aisla cada máquina virtual del anfitrión y otras máquinas virtuales, evitando que máquinas virtuales colgadas afecten a otras.  La información que transfieren las máquinas virtuales puede ser protegida en redes virtuales autocontenidas dentro del mismo anfitrión.  VMware encapsula las máquinas virtuales en archivos, lo que facilita el backup y copia de las mismas.

Sistemas Operativos Soportados:

Windows 64-Bit Operating Systems

• Windows Server 2008 x64 Standard Edition
• Windows Server 2008 x64 Enterprise Edition
• Windows Vista x64 Business Edition
• Windows Vista x64 Ultimate Edition
• Windows XP Professional x64
• Windows Server 2003 x64 Standard Edition
• Windows Server 2003 x64 Web Edition
• Windows Server 2003 x64 Enterprise Edition

Windows 32-Bit Guest Operating Systems

• Windows Server 2008 Standard Edition
• Windows Server 2008 Enterprise Edition
• Windows Vista Business Edition
• Windows Vista Ultimate Edition
• Windows XP Professional
• Windows Server 2003 Standard Edition
• Windows Server 2003 Web Edition
• Windows Server 2003 Enterprise Edition
• Windows Small Business Server 2003 Standard Edition
• Windows Small Business Server 2003 Premium Edition
• Windows 2000 Server
• Windows 2000 Advanced Server

Linux 64-Bit Guest Operating Systems

• Mandrake Linux
• Mandriva Linux
• Red Hat Enterprise Linux
• SUSE Linux
• SUSE Linux Enterprise Server
• openSUSE Linux
• Open Enterprise Server (OES)
• Ubuntu Linux

Linux 32-Bit Guest Operating Systems

• Mandrake Linux
• Mandriva Linux
• Red Hat Enterprise Linux
• SUSE Linux
• SUSE Linux Enterprise Server
• openSUSE Linux
• Open Enterprise Server (OES)
• Ubuntu Linux

Sun Solaris 64-Bit Guest Operating Systems

• Solaris x86

Sun Solaris 32-Bit Guest Operating Systems

• Solaris x86

Novell NetWare 32-Bit Guest Operating System

• NetWare

Procedimiento:

El primer paso a realizar es actualizar el sistema.

< sudo apt-get update
< sudo apt-get dist-upgrade

Se se actualizó el kernel, se debe reiniciar para iniciar el sistema con el kernel más nuevo.

Se deben instalar algunos paquetes para poder llevar adelante la instalación de VMware Server.

Se debe identificar el kernel que esta usando el equipo.

< @fatass:~$ uname -a
> Linux fatass 2.6.28-11-generic #42-Ubuntu SMP Fri Apr 17 01:57:59 UTC 2009 i686 GNU/Linux

Como estoy usando el kernel genérico en mi notebook, entonces voy a instalar "linux-headers-generic".  Las opciones son las siguientes (se puede instalar el header específico de cada kernel, pero con este, nos aseguramos que cada vez que se instale un kernel nuevo descarga los headers).

• linux-headers-generic
• linux-headers-server

Para instalar los paquetes se debe ejecutar el siguiente comando.

< sudo apt-get install build-essential xinetd linux-headers-generic

A continuación se debe descargar y descomprimir el .tar.gz del instalador.

La url de descarga es: https://www.vmware.com/freedownload/login.php?product=server20

Se debe estar registrado en VMware para poder hacer la descarga (tanto el registro del usuario como el producto son gratuitos).

Asumiendo que la descarga se realizó en el /var/tmp

< cd /var/tmp
< tar -xzf VMware-server-2.0.1-156745.x86_64.tar.gz

Finalizada la descompresión se debe proceder a ejecutar el instalador, este procedimiento se debe ejecutar con privilegios de administración.  Durante la instalación el programa nos preguntará por la definición de varios parámetros de configuración.

Durante este proceso se tiene el caso especial que el equipo anfitrión dispone de dos placas de red en redes distintas, entonces se crean dos interfaces "bridge" (puente) para que se puedan dar servicios a ambas redes.

Las redes host-only y nat son definidas en lugar de permitir la autodetección.

Se asigna al usuario "user" para administrar el VMware.

La ubicación de las VMwares es definida en "/var/vmwares"

< sudo ./vmware-install.pl
> [sudo] password for user:
> Creating a new VMware Server installer database using the tar4 format.
> 
> Installing VMware Server.
> 
> In which directory do you want to install the binary files?
> [/usr/bin]
> 
> What is the directory that contains the init directories (rc0.d/ to rc6.d/)?
> [/etc]
> 
> What is the directory that contains the init scripts?
> [/etc/init.d]
> 
> In which directory do you want to install the daemon files?
> [/usr/sbin]
> 
> In which directory do you want to install the library files?
> [/usr/lib/vmware]
> 
> The path "/usr/lib/vmware" does not exist currently. This program is going to
> create it, including needed parent directories. Is this what you want?
> [yes]
> 
> In which directory do you want to install the manual files?
> [/usr/share/man]
> 
> In which directory do you want to install the documentation files?
> [/usr/share/doc/vmware]
> 
> The path "/usr/share/doc/vmware" does not exist currently. This program is
> going to create it, including needed parent directories. Is this what you want?
> [yes]
> 
> The installation of VMware Server 2.0.1 build-156745 for Linux completed
> successfully. You can decide to remove this software from your system at any
> time by invoking the following command: "/usr/bin/vmware-uninstall.pl".
> 
> Before running VMware Server for the first time, you need to configure it by
> invoking the following command: "/usr/bin/vmware-config.pl". Do you want this
> program to invoke the command for you now? [yes]
> 
> Making sure services for VMware Server are stopped.
> 
> Stopping VMware autostart virtual machines:
>    Virtual machines                                                   failed
> Stopping VMware management services:
>    VMware Virtual Infrastructure Web Access
>    VMware Server Host Agent                                           failed
> Stopping VMware services:
>    VMware Authentication Daemon                                        done
>    Virtual machine monitor                                             done
> 
> You must read and accept the End User License Agreement to continue.
> Press enter to display it.
> 
> NOTICE: 
> Do you accept? (yes/no) yes
> 
> Thank you.
> 
> None of the pre-built vmmon modules for VMware Server 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.28-11-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.28-11-generic/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. modules
> make[1]: Entering directory `/usr/src/linux-headers-2.6.28-11-generic'
>   CC [M]  /tmp/vmware-config0/vmmon-only/linux/driver.o
>   CC [M]  /tmp/vmware-config0/vmmon-only/linux/driverLog.o
>   CC [M]  /tmp/vmware-config0/vmmon-only/linux/hostif.o
>   CC [M]  /tmp/vmware-config0/vmmon-only/common/comport.o
>   CC [M]  /tmp/vmware-config0/vmmon-only/common/cpuid.o
>   CC [M]  /tmp/vmware-config0/vmmon-only/common/hashFunc.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.28-11-generic'
> cp -f vmmon.ko ./../vmmon.o
> make: Leaving directory `/tmp/vmware-config0/vmmon-only'
> The vmmon module loads perfectly into the running kernel.
> 
> None of the pre-built vmci modules for VMware Server is suitable for your
> running kernel.  Do you want this program to try to build the vmci module for
> your system (you need to have a C compiler installed on your system)? [yes]
> 
> Extracting the sources of the vmci module.
> 
> Building the vmci module.
> 
> Using 2.6.x kernel build system.
> make: Entering directory `/tmp/vmware-config0/vmci-only'
> make -C /lib/modules/2.6.28-11-generic/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. modules
> make[1]: Entering directory `/usr/src/linux-headers-2.6.28-11-generic'
>   CC [M]  /tmp/vmware-config0/vmci-only/linux/driver.o
>   CC [M]  /tmp/vmware-config0/vmci-only/linux/driverLog.o
>   CC [M]  /tmp/vmware-config0/vmci-only/linux/vmciKernelIf.o
>   CC [M]  /tmp/vmware-config0/vmci-only/common/vmciContext.o
>   CC [M]  /tmp/vmware-config0/vmci-only/common/vmciDatagram.o
>   CC [M]  /tmp/vmware-config0/vmci-only/common/vmciDriver.o
>   CC [M]  /tmp/vmware-config0/vmci-only/common/vmciDs.o
>   CC [M]  /tmp/vmware-config0/vmci-only/common/vmciEvent.o
>   CC [M]  /tmp/vmware-config0/vmci-only/common/vmciGroup.o
>   CC [M]  /tmp/vmware-config0/vmci-only/common/vmciHashtable.o
>   CC [M]  /tmp/vmware-config0/vmci-only/common/vmciProcess.o
>   CC [M]  /tmp/vmware-config0/vmci-only/common/vmciQueuePair.o
>   CC [M]  /tmp/vmware-config0/vmci-only/common/vmciResource.o
>   LD [M]  /tmp/vmware-config0/vmci-only/vmci.o
>   Building modules, stage 2.
>   MODPOST 1 modules
>   CC      /tmp/vmware-config0/vmci-only/vmci.mod.o
>   LD [M]  /tmp/vmware-config0/vmci-only/vmci.ko
> make[1]: Leaving directory `/usr/src/linux-headers-2.6.28-11-generic'
> cp -f vmci.ko ./../vmci.o
> make: Leaving directory `/tmp/vmware-config0/vmci-only'
> The vmci module loads perfectly into the running kernel.
> 
> None of the pre-built vsock modules for VMware Server is suitable for your
> running kernel.  Do you want this program to try to build the vsock module for
> your system (you need to have a C compiler installed on your system)? [yes]
> 
> Extracting the sources of the vsock module.
> 
> Building the vsock module.
> 
> Using 2.6.x kernel build system.
> make: Entering directory `/tmp/vmware-config0/vsock-only'
> make -C /lib/modules/2.6.28-11-generic/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. modules
> make[1]: Entering directory `/usr/src/linux-headers-2.6.28-11-generic'
>   CC [M]  /tmp/vmware-config0/vsock-only/linux/af_vsock.o
>   CC [M]  /tmp/vmware-config0/vsock-only/linux/driverLog.o
>   CC [M]  /tmp/vmware-config0/vsock-only/linux/util.o
> /tmp/vmware-config0/vsock-only/linux/util.c: In function ‘VSockVmciLogPkt’:
> /tmp/vmware-config0/vsock-only/linux/util.c:157: warning: format not a string literal and no format arguments
>   CC [M]  /tmp/vmware-config0/vsock-only/linux/vsockAddr.o
>   LD [M]  /tmp/vmware-config0/vsock-only/vsock.o
>   Building modules, stage 2.
>   MODPOST 1 modules
> WARNING: "VMCIDatagram_CreateHnd" [/tmp/vmware-config0/vsock-only/vsock.ko] undefined!
> WARNING: "VMCIDatagram_DestroyHnd" [/tmp/vmware-config0/vsock-only/vsock.ko] undefined!
> WARNING: "VMCI_GetContextID" [/tmp/vmware-config0/vsock-only/vsock.ko] undefined!
> WARNING: "VMCIDatagram_Send" [/tmp/vmware-config0/vsock-only/vsock.ko] undefined!
>   CC      /tmp/vmware-config0/vsock-only/vsock.mod.o
>   LD [M]  /tmp/vmware-config0/vsock-only/vsock.ko
> make[1]: Leaving directory `/usr/src/linux-headers-2.6.28-11-generic'
> cp -f vsock.ko ./../vsock.o
> make: Leaving directory `/tmp/vmware-config0/vsock-only'
> Unable to make a vsock module that can be loaded in the running kernel:
> insmod: error inserting '/tmp/vmware-config0/vsock.o': -1 Unknown symbol in module
> There is probably a slight difference in the kernel configuration between the
> set of C header files you specified and your running kernel.  You may want to
> rebuild a kernel based on that directory, or specify another directory.
> 
> The VM communication interface socket family is used in conjunction with the VM
> communication interface to provide a new communication path among guests and
> host.  The rest of this software provided by VMware Server is designed to work
> independently of this feature.  If you wish to have the VSOCK feature  you can
> install the driver by running vmware-config.pl again after making sure that
> gcc, binutils, make and the kernel sources for your running kernel are
> installed on your machine. These packages are available on your distribution's
> installation CD.
> [ Press the Enter key to continue.]
> Do you want networking for your virtual machines? (yes/no/help) [yes]
> 
> Configuring a bridged network for vmnet0.
> 
Please specify a name for this network.
> [Bridged]
> 
> Your computer has multiple ethernet network interfaces available: eth0, eth1,
> pan0. Which one do you want to bridge to vmnet0? [eth0]
> 
> The following bridged networks have been defined:
> 
> . vmnet0 is bridged to eth0
> 
> Do you wish to configure another bridged network? (yes/no) [no] yes
> 
> Configuring a bridged network for vmnet2.
> 
> 
> 
> Which one do you want to bridge to vmnet2? [eth0] eth1
> 
> The following bridged networks have been defined:
> 
> . vmnet0 is bridged to eth0
> . vmnet2 is bridged to eth1
> 
> Do you wish to configure another bridged network? (yes/no) [no]
> 
> Do you want to be able to use NAT networking in your virtual machines? (yes/no)
> [yes]
> 
> Configuring a NAT network for vmnet8.
> 
> Please specify a name for this network. [NAT]
> 
> Do you want this program to probe for an unused private subnet? (yes/no/help)
> [yes] < no
> 
> What will be the IP address of your host on the private
> network? < 10.0.20.1
> 
> What will be the netmask of your private network? < 255.255.255.0
> 
> The following NAT networks have been defined:
> 
> . vmnet8 is a NAT network on private subnet 10.0.20.0.
> 
> Do you wish to configure another NAT network? (yes/no) [no]
> 
> Do you want to be able to use host-only networking in your virtual machines?
> [yes]
> 
> Configuring a host-only network for vmnet1.
> 
> Please specify a name for this network.
> [HostOnly]
> 
> Do you want this program to probe for an unused private subnet? (yes/no/help)
> [yes] no
> 
> What will be the IP address of your host on the private
> network? < 10.0.21.1
> 
> What will be the netmask of your private network? < 255.255.255.0
> 
> The following host-only networks have been defined:
> 
> . vmnet1 is a host-only network on private subnet 10.0.21.0.
> 
> Do you wish to configure another host-only network? (yes/no) [no]
> 
> Network name "Bridged" for vmnet2 is already in use by vmnet0 -- renaming to
> "Bridged (2)"
> None of the pre-built vmnet modules for VMware Server is suitable for your
> running kernel.  Do you want this program to try to build the vmnet module for
> your system (you need to have a C compiler installed on your system)? [yes]
> 
> Extracting the sources of the vmnet module.
> 
> Building the vmnet module.
> 
> Using 2.6.x kernel build system.
> make: Entering directory `/tmp/vmware-config1/vmnet-only'
> make -C /lib/modules/2.6.28-11-generic/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. modules
> make[1]: Entering directory `/usr/src/linux-headers-2.6.28-11-generic'
>   CC [M]  /tmp/vmware-config1/vmnet-only/driver.o
>   CC [M]  /tmp/vmware-config1/vmnet-only/hub.o
>   CC [M]  /tmp/vmware-config1/vmnet-only/userif.o
>   CC [M]  /tmp/vmware-config1/vmnet-only/netif.o
>   CC [M]  /tmp/vmware-config1/vmnet-only/bridge.o
>   CC [M]  /tmp/vmware-config1/vmnet-only/filter.o
>   CC [M]  /tmp/vmware-config1/vmnet-only/procfs.o
>   CC [M]  /tmp/vmware-config1/vmnet-only/smac_compat.o
>   CC [M]  /tmp/vmware-config1/vmnet-only/smac.o
>   CC [M]  /tmp/vmware-config1/vmnet-only/vnetEvent.o
>   CC [M]  /tmp/vmware-config1/vmnet-only/vnetUserListener.o
>   LD [M]  /tmp/vmware-config1/vmnet-only/vmnet.o
>   Building modules, stage 2.
>   MODPOST 1 modules
>   CC      /tmp/vmware-config1/vmnet-only/vmnet.mod.o
>   LD [M]  /tmp/vmware-config1/vmnet-only/vmnet.ko
> make[1]: Leaving directory `/usr/src/linux-headers-2.6.28-11-generic'
> cp -f vmnet.ko ./../vmnet.o
> make: Leaving directory `/tmp/vmware-config1/vmnet-only'
> The vmnet module loads perfectly into the running kernel.
> 
> Please specify a port for remote connections to use [902]
> 
> Please specify a port for standard http connections to use [8222]
> 
> Please specify a port for secure http (https) connections to use [8333]
> 
> The current administrative user for VMware Server  is ''.  Would you like to
> specify a different administrator? [no] < yes
> 
> Please specify the user whom you wish to be the VMware Server administrator
<  user
> 
> Using sismo as the VMware Server administrator.
> 
> In which directory do you want to keep your virtual machine files?
> [/var/lib/vmware/Virtual Machines] < /var/vmwares
> 
> The path "/var/vmwares" does not exist currently. This program is going to
> create it, including needed parent directories. Is this what you want?
> [yes]
> 
> Please enter your 20-character serial number.
> 
> Type XXXXX-XXXXX-XXXXX-XXXXX or 'Enter' to cancel:  < XXXXX-XXXXX-XXXXX-XXXXX
> 
> Creating a new VMware VIX API installer database using the tar4 format.
> 
> Installing VMware VIX API.
> 
> 
> In which directory do you want to install the VMware VIX API binary files?
> [/usr/bin]
> 
> In which directory do you want to install the VMware VIX API library files?
> [/usr/lib/vmware-vix/lib]
> 
> The path "/usr/lib/vmware-vix/lib" does not exist currently. This program is
> going to create it, including needed parent directories. Is this what you want?
> [yes]
> 
> In which directory do you want to install the VMware VIX API document pages?
> [/usr/share/doc/vmware-vix]
> 
> The path "/usr/share/doc/vmware-vix" does not exist currently. This program is
> going to create it, including needed parent directories. Is this what you want?
> [yes]
> 
> The installation of VMware VIX API 1.6.2 build-156745 for Linux completed
> successfully. You can decide to remove this software from your system at any
> time by invoking the following command: "/usr/bin/vmware-uninstall-vix.pl".
> 
> Enjoy,
> 
> --the VMware team
> 
> Starting VMware services:
>    Virtual machine monitor                                             done
>    Virtual machine communication interface                             done
>    Virtual ethernet                                                    done
>    Bridged networking on /dev/vmnet0                                   done
>    Host-only networking on /dev/vmnet1 (background)                    done
>    DHCP server on /dev/vmnet1                                          done
>    Bridged networking on /dev/vmnet2                                   done
>    Host-only networking on /dev/vmnet8 (background)                    done
>    DHCP server on /dev/vmnet8                                          done
>    NAT service on /dev/vmnet8                                          done
>    VMware Server Authentication Daemon (background)                    done
>    Shared Memory Available                                             done
> Starting VMware management services:
>    VMware Server Host Agent (background)                               done
>    VMware Virtual Infrastructure Web Access
> Starting VMware autostart virtual machines:
>    Virtual machines                                                    done
> 
> The configuration of VMware Server 2.0.1 build-156745 for Linux for this
> running kernel completed successfully.

La interface de administración es web.  Se debe acceder por conexión segura si es un equipo remoto.

• http://127.0.0.1:8222 (si la instalación se realizó en el equipo local).
• https://192.168.0.1:8333 (si la instalación se realizó en un equipo remoto y 192.168.0.1 es la dirección ip del mismo).

La pantalla de inicio del VMware es la siguiente.  En algunas ocasiones falla la carga de la misma y se debe presionar ctrl+F5 para recargar la página y solucionar el problema.

Se deben ingresar los datos del usuario habilitado a administrar VMware (definido durante la instalación).

Se presentará la siguiente pantalla de administración.