Recientemente ha salido VMWare Server 2, la nueva versión del producto gratuito de virtualización de VMWare. Esta nueva versión incorpora varias mejoras incluyendo la administración vía web a través de VMware Infrastructure Web Access (parecido al VMWare Management services de la versión anterior pero más completo), es decir, que ahora instalando el plugin de VMWare en el navegador podemos ejecutar nuestras máquinas virtuales.
En este artículo vamos a tratar estos dos temas:
- Instalación de VMWare Server 2 sobre linux, en concreto sobre Fedora Core 8
- Migración de las máquinas virtuales de VMWare Server 1.0.X a la nueva versión VMWare Server 2.
En este caso el host que vamos a utilizar tiene instalado un Fedora Core 8 como sistema operativo, que previamente tenía instalada la versión anterior del producto.
El motivo para pasar a la nueva versión (que quizá sea tu caso) es el siguiente: En una de las últimas actualizaciones del sistema operativo, tras actualizar el equipo al último kernel de la distribución las máquinas virtuales dejaron de funcionar, y volviendo a ejecutar la configuración de vmware, aparecía un mensaje de error de que el kernel no está soportado por esa distribución de VMWare. El momento de migrar a la nueva versión había llegado, y las dudas de si funcionaría la nueva instalación y podría seguir utilizando las máquinas virtuales de la versión anterior se despejarían muy pronto.
Instalación de VMWare Server 2
Debes registrarte en la web previamente a descargar el software, pero en este caso solicitan muy pocos datos y lo harás rápidamente, no es como otros registros que te piden infinidad de datos. También te es necesario para obtener el código de la Licencia (o los códigos de licencia si quieres pedir más, según las instalaciones que tengas pensado).
Descargar el producto de la web de VMWare aquí: http://www.vmware.com/products/server
Tras descargar el fichero procedemos a su instalación. En este caso elegimos la versión para linux ya que queremos instalarlo sobre una máquina con Fedora Core 8 como sistema operativo. Para windows la instalación es más sencilla, basta con seguir el asistente de instalacion y confirmar los pasos, amenos que queramos modificar alguna ruta del sistema de ficheros (como por ejemplo la ruta a nuestro almacén de máquinas virtuales).
Tras descargarlo, abrimos una consola y nos posicionamos en el directorio donde lo hemos descargado. Copiamos el fichero descargado al directorio /tmp (si es que no lo hemos descargado directamente aquí) con el siguiente comando:
cp VMware-server-2.0.0-122956.x86_64.tar.gz /tmp
Nos movemos a ese directorio para descomprir y desempaquetar la aplicación:
cd /tmp
tar -zxvf VMware-server-2.0.0-122956.x86_64.tar.gz
Tras ejecutar este comando se crea un directorio, vmware-server-distrib, nos metemos dentro del directorio para buscar el fichero de instalación de VMWare Server, y lo invocamos para comenzar la instalación como root:
cd vmware-server-distrib
./vmware-install.pl
Abajo se muestra el la salida de la consola de la instalación completa, la mayoría de los pasos basta con confirmar la opción por defecto. Dado que inicialmente tenía instalada la versión anterior del producto, lo primero que hará es desinstalarla.
A previous installation of VMware Server has been detected.
The previous installation was made by the tar installer (version 3).
Keeping the tar3 installer database format.
You have a product that conflicts with VMware Server installed. Continuing
this install will first uninstall this product. Do you wish to continue?
(yes/no) [yes]
Uninstalling the tar installation of VMware Server.
Parando xinetd: [ OK ]
Iniciando xinetd: [ OK ]
Stopping VMware services:
Virtual machine monitor [ OK ]
The removal of VMware Server 1.0.8 build-126538 for Linux completed
successfully. Thank you for having tried this software.
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/rc.d]
What is the directory that contains the init scripts?
[/etc/rc.d/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]
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.0 build-122956 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 [FALLÓ]
Stopping VMware management services:
VMware Virtual Infrastructure Web Access
VMware Server Host Agent [FALLÓ]
Stopping VMware services:
VMware Authentication Daemon [ OK ]
Virtual machine monitor [ OK ]
You must read and accept the End User License Agreement to continue.
Press enter to display it.
NOTICE: BY DOWNLOADING AND INSTALLING, .................
.........................................................
(he ocultado el texto de la licencia)
.........................................................
Do you accept? (yes/no) y
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.26.6-49.fc8/build/include]
Extracting the sources of the vmmon module.
Building the vmmon module.
Using 2.6.x kernel build system.
make: se ingresa al directorio `/tmp/vmware-config4/vmmon-only'
make -C /lib/modules/2.6.26.6-49.fc8/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. modules
make[1]: se ingresa al directorio `/usr/src/kernels/2.6.26.6-49.fc8-x86_64'
CC [M] /tmp/vmware-config4/vmmon-only/linux/driver.o
CC [M] /tmp/vmware-config4/vmmon-only/linux/driverLog.o
CC [M] /tmp/vmware-config4/vmmon-only/linux/hostif.o
CC [M] /tmp/vmware-config4/vmmon-only/common/comport.o
CC [M] /tmp/vmware-config4/vmmon-only/common/cpuid.o
CC [M] /tmp/vmware-config4/vmmon-only/common/hashFunc.o
CC [M] /tmp/vmware-config4/vmmon-only/common/memtrack.o
CC [M] /tmp/vmware-config4/vmmon-only/common/phystrack.o
CC [M] /tmp/vmware-config4/vmmon-only/common/task.o
CC [M] /tmp/vmware-config4/vmmon-only/common/vmx86.o
CC [M] /tmp/vmware-config4/vmmon-only/vmcore/moduleloop.o
LD [M] /tmp/vmware-config4/vmmon-only/vmmon.o
Building modules, stage 2.
MODPOST 1 modules
CC /tmp/vmware-config4/vmmon-only/vmmon.mod.o
LD [M] /tmp/vmware-config4/vmmon-only/vmmon.ko
make[1]: se sale del directorio `/usr/src/kernels/2.6.26.6-49.fc8-x86_64'
cp -f vmmon.ko ./../vmmon.o
make: se sale del directorio `/tmp/vmware-config4/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: se ingresa al directorio `/tmp/vmware-config4/vmci-only'
make -C /lib/modules/2.6.26.6-49.fc8/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. modules
make[1]: se ingresa al directorio `/usr/src/kernels/2.6.26.6-49.fc8-x86_64'
CC [M] /tmp/vmware-config4/vmci-only/linux/driver.o
CC [M] /tmp/vmware-config4/vmci-only/linux/driverLog.o
CC [M] /tmp/vmware-config4/vmci-only/linux/vmciKernelIf.o
CC [M] /tmp/vmware-config4/vmci-only/common/vmciContext.o
CC [M] /tmp/vmware-config4/vmci-only/common/vmciDatagram.o
CC [M] /tmp/vmware-config4/vmci-only/common/vmciDriver.o
CC [M] /tmp/vmware-config4/vmci-only/common/vmciDs.o
CC [M] /tmp/vmware-config4/vmci-only/common/vmciEvent.o
CC [M] /tmp/vmware-config4/vmci-only/common/vmciGroup.o
CC [M] /tmp/vmware-config4/vmci-only/common/vmciHashtable.o
CC [M] /tmp/vmware-config4/vmci-only/common/vmciProcess.o
CC [M] /tmp/vmware-config4/vmci-only/common/vmciQueuePair.o
CC [M] /tmp/vmware-config4/vmci-only/common/vmciResource.o
LD [M] /tmp/vmware-config4/vmci-only/vmci.o
Building modules, stage 2.
MODPOST 1 modules
CC /tmp/vmware-config4/vmci-only/vmci.mod.o
LD [M] /tmp/vmware-config4/vmci-only/vmci.ko
make[1]: se sale del directorio `/usr/src/kernels/2.6.26.6-49.fc8-x86_64'
cp -f vmci.ko ./../vmci.o
make: se sale del directorio `/tmp/vmware-config4/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: se ingresa al directorio `/tmp/vmware-config4/vsock-only'
make -C /lib/modules/2.6.26.6-49.fc8/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. modules
make[1]: se ingresa al directorio `/usr/src/kernels/2.6.26.6-49.fc8-x86_64'
CC [M] /tmp/vmware-config4/vsock-only/linux/af_vsock.o
CC [M] /tmp/vmware-config4/vsock-only/linux/driverLog.o
CC [M] /tmp/vmware-config4/vsock-only/linux/util.o
CC [M] /tmp/vmware-config4/vsock-only/linux/vsockAddr.o
LD [M] /tmp/vmware-config4/vsock-only/vsock.o
Building modules, stage 2.
MODPOST 1 modules
WARNING: "VMCIDatagram_CreateHnd" [/tmp/vmware-config4/vsock-only/vsock.ko] undefined!
WARNING: "VMCIDatagram_DestroyHnd" [/tmp/vmware-config4/vsock-only/vsock.ko] undefined!
WARNING: "VMCI_GetContextID" [/tmp/vmware-config4/vsock-only/vsock.ko] undefined!
WARNING: "VMCIDatagram_Send" [/tmp/vmware-config4/vsock-only/vsock.ko] undefined!
CC /tmp/vmware-config4/vsock-only/vsock.mod.o
LD [M] /tmp/vmware-config4/vsock-only/vsock.ko
make[1]: se sale del directorio `/usr/src/kernels/2.6.26.6-49.fc8-x86_64'
cp -f vsock.ko ./../vsock.o
make: se sale del directorio `/tmp/vmware-config4/vsock-only'
The vsock module loads perfectly into the running kernel.
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, 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]
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]
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 NAT networks have been defined:
. vmnet8 is a NAT network on private subnet 192.168.43.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]
Probing for an unused private subnet (this can take some time)...
The subnet 192.168.49.0/255.255.255.0 appears to be unused.
The following host-only networks have been defined:
. vmnet1 is a host-only network on private subnet 192.168.49.0.
Do you wish to configure another host-only network? (yes/no) [no]
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: se ingresa al directorio `/tmp/vmware-config4/vmnet-only'
make -C /lib/modules/2.6.26.6-49.fc8/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. modules
make[1]: se ingresa al directorio `/usr/src/kernels/2.6.26.6-49.fc8-x86_64'
CC [M] /tmp/vmware-config4/vmnet-only/driver.o
CC [M] /tmp/vmware-config4/vmnet-only/hub.o
CC [M] /tmp/vmware-config4/vmnet-only/userif.o
CC [M] /tmp/vmware-config4/vmnet-only/netif.o
CC [M] /tmp/vmware-config4/vmnet-only/bridge.o
CC [M] /tmp/vmware-config4/vmnet-only/filter.o
CC [M] /tmp/vmware-config4/vmnet-only/procfs.o
CC [M] /tmp/vmware-config4/vmnet-only/smac_compat.o
CC [M] /tmp/vmware-config4/vmnet-only/smac.o
CC [M] /tmp/vmware-config4/vmnet-only/vnetEvent.o
CC [M] /tmp/vmware-config4/vmnet-only/vnetUserListener.o
LD [M] /tmp/vmware-config4/vmnet-only/vmnet.o
Building modules, stage 2.
MODPOST 1 modules
CC /tmp/vmware-config4/vmnet-only/vmnet.mod.o
LD [M] /tmp/vmware-config4/vmnet-only/vmnet.ko
make[1]: se sale del directorio `/usr/src/kernels/2.6.26.6-49.fc8-x86_64'
cp -f vmnet.ko ./../vmnet.o
make: se sale del directorio `/tmp/vmware-config4/vmnet-only'
The vmnet module loads perfectly into the running kernel.
Please specify a port for remote connections to use [902]
Do you want this program to set up permissions for your registered virtual
machines? This will be done by setting new permissions on all files found in
the "/etc/vmware/vm-list" file. [no]
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
root
Using root as the VMware Server administrator.
In which directory do you want to keep your virtual machine files?
[/var/lib/vmware/Virtual Machines]
The path "/var/lib/vmware/Virtual Machines" does not exist currently. This
program is going to create it, including needed parent directories. Is this
what you want? [yes]
Do you want to enter a serial number now? (yes/no/help) [no] y
Please enter your 20-character serial number.
Type XXXXX-XXXXX-XXXXX-XXXXX or 'Enter' to cancel: NNNNN-NNNNN-NNNNN-NNNNN
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.0 build-122956 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 [ OK ]
Virtual machine communication interface [ OK ]
VM communication interface socket family: [ OK ]
Virtual ethernet [ OK ]
Bridged networking on /dev/vmnet0 [ OK ]
Host-only networking on /dev/vmnet1 (background) [ OK ]
DHCP server on /dev/vmnet1 [ OK ]
Host-only networking on /dev/vmnet8 (background) [ OK ]
DHCP server on /dev/vmnet8 [ OK ]
NAT service on /dev/vmnet8 [ OK ]
VMware Server Authentication Daemon (background) [ OK ]
Shared Memory Available [ OK ]
Starting VMware management services:
VMware Server Host Agent (background) [ OK ]
VMware Virtual Infrastructure Web Access
Starting VMware autostart virtual machines:
Virtual machines [ OK ]
The configuration of VMware Server 2.0.0 build-122956 for Linux for this
running kernel completed successfully.
Desde nuestro navegador accedemos a una de estas dos direcciones (la diferencia es que una va por https):
http://localhost:8222
https://localhost:8333
 |
Intoducimos el usuario de administración que indicamos en la instalación y accedemos a la pantalla principal de administración.
|
En la parte izquierda de la pantalla podemos ver nuestro inventario de máquinas virtuales. En este caso nos ha reconocido las máquinas virtuales que teníamos anteriormente creadas con VMWare server 1.0.X. Ahora procederemos a migrar las maquinas virtuales a la nueva versión 2.
Migración de las máquinas virtuales de VMWare Server 1.0.X a la nueva versión VMWare Server 2
Ya hemos instalado la nueva versión, pero ¿qué pasa con nuestras máquinas virtuales de la versión 1.0.X?
La migración de las máquinas virtuales básicamente se reduce a dos pasos que tendremos que realizar por cada máquina virtual que queramos migrar. Estos son los pasos:
Actualizar los ficheros de la máquina virtual: Upgrade Virtual Machine
Seleccionamos una de las máquinas virtuales del inventario, y en la parte derecha dentro de el panel de Status veremos que en apartado Virtual Hardware Version tenemos un enlace para actualizar nuestra máquina virtual, Upgrade Virtual Machine:
 |
Con esto hemos completado el primer paso, ahora nuestra máquina virtual puede aprovechar todas las novedades de la versión 2.
Actualizar las herramientas de VMWare (VMWare Tools)
Ahora tenemos que actualizar las herramientas de VMWare en el sistema operativo de la máquina virtual. Para hacer esto la máquina virtual debe estar arrancada, por tanto procedemos a arrancarla y así comprobaremos que funciona tras actualizarla.
En la parte derecha una vez arrancada, se mostrará dentro del panel de Status en apartado VMWare Tools un enlace para actualizar las herramientas de VMWare. Pinchamos e instalamos las herramientas aceptando la opción por defecto (luego podremos modificarlo).
 |
Y yá está actualizada la máquina virtual. Repetimos el proceso con el resto de máquinas virtuales y ya tenemos toda nuestra instalación de VMWare Server 2 funcionando.
 |
Problema: Si reinicias la máquina e intentas entrar de nuevo al VMware Infrastructure Web Access no podrás acceder. ¿Qué ha fallado en la instalación?
 |
Esto es debido a un bug que provoca que no arranquen correctamente los servicios, la solución temporal para corregir esto es volver arrancar el servicio de vmware desde línea de comandos, tras hacerlo podrás entrar de nuevo a administrar tus máquinas virtuales.
Debes ejecutar el siguiente comando como root:
/sbin/service vmware restart
o bien hacer un sudo de esta forma:
sudo /sbin/service vmware restart
Aquí tienes la salida de la consola de este último:
[usuario3@f8 ~]$ sudo /sbin/service vmware restart
Stopping VMware autostart virtual machines:
Virtual machines [ OK ]
Stopping VMware management services:
VMware Virtual Infrastructure Web Access
VMware Server Host Agent [ OK ]
Stopping VMware services:
VMware Authentication Daemon [ OK ]
VM communication interface socket family: [ OK ]
Virtual machine communication interface [ OK ]
Virtual machine monitor [ OK ]
Bridged networking on /dev/vmnet0 [ OK ]
Host network detection [ 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:
Virtual machine monitor [ OK ]
Virtual machine communication interface [ OK ]
VM communication interface socket family: [ OK ]
Virtual ethernet [ OK ]
Bridged networking on /dev/vmnet0 [ OK ]
Host-only networking on /dev/vmnet1 (background) [ OK ]
DHCP server on /dev/vmnet1 [ OK ]
Host-only networking on /dev/vmnet8 (background) [ OK ]
DHCP server on /dev/vmnet8 [ OK ]
NAT service on /dev/vmnet8 [ OK ]
VMware Server Authentication Daemon (background) [ OK ]
Shared Memory Available [ OK ]
Starting VMware management services:
VMware Server Host Agent (background) [ OK ]
VMware Virtual Infrastructure Web Access
Starting VMware autostart virtual machines:
Virtual machines [ OK ]
[usuario3@f8 ~]$
Ahora basta con intentar entrar de nuevo volviendo a introducir las claves de root y ya estamos dentro.
 |
Este problema parece heradado de la versión anterior, lo mismo ocurría con los VMWare Management services, pero en este caso buscando por la red había un parche que tras ejecutarlo solucionaba el problema, en la nueva versión estaremos al tanto a ver si alguien lo publica.
Seguiré mirando en los foros a ver si se publica el parche para este problema, si lo encuentro actualizaré el artículo para incluirlo, mientras tanto, disfruta de tus máquinas virtuales!!
Fuente:
- BitHoy
- Foros de Fedora Core
- How To Install VMware Server 2 On Ubuntu 8.10
| Comentarios |
|
