La conversión me la ha hecho bien, la máquina física convertida a virtual con Linux Fedora funciona bien. Pero ahora quiero instalar las VMware Tools y no sé cómo hacerlo. Esta máquina no tiene el modo gráfico.
Publicado:
Lun Mar 24, 2014 10:35 am
alonsojpd Administrador/Moderador
Registrado: Sep 16, 2003 Mensajes: 2687
Asunto: Re: Instalar VMware Tools en Linux Fedora Core 8
Anuncios
varios escribió:
Hola, tengo un servidor web con Linux Fedora Core 8, lo pasé de máquina física a virtual (F2V) siguiendo las indicaciones de vuestro tutorial:
La conversión me la ha hecho bien, la máquina física convertida a virtual con Linux Fedora funciona bien. Pero ahora quiero instalar las VMware Tools y no sé cómo hacerlo. Esta máquina no tiene el modo gráfico.
Hola, te indicamos los pasos a seguir desde la ventana de terminal para instalar las VMware Tools en Linux Fedora, también te indicamos cómo configurar la red y la conexión a Internet (por si acaso):
1. Primero comprueba que tienes Internet en el PC (haciendo un ping a alguna página web), si no tienes Internet verifica la configuración editando el fichero de configuración de red con:
Si tienes proxy en la red lo puedes habilitar con:
Código:
http_proxy="http://192.168.1.115:8080"
y:
Código:
export http_proxy
2. Es posible que tengas que actualizar Linux Fedora pues tienes una versión "antigua", para actualizarlo tal vez tengas que añadir algunos repositorios editando fichero /etc/yum.conf con:
Código:
nano /etc/yum.conf
Algunos repositorios para la versión 8 de Linux Fedora:
Guardar cambios en fichero pulsando Control + O y cerrar con Control + X.
Ahora ya podrás actualizar Fedora con el comando:
Código:
yum update
3. Una vez actualizado Fedora, es neceario actualizamos las cabeceras del kernel con:
Código:
yum install kernel-devel kernel-headers gcc make
Devolverá algo así:
Setting up Install Process
Parsing package install arguments
Package kernel-devel-2.6.26.8-57.fc8.i686 already installed and latest version
Package kernel-headers-2.6.26.8-57.fc8.i386 already installed and latest version
Package gcc-4.1.2-33.i386 already installed and latest version
Package 1:make-3.81-11.fc8.i386 already installed and latest version
Nothing to do
4. Desde VMware vSphere Client seleccionaremos la máquina virtual, pulsaremos con el botón derecho sobre ella y en el menú emergente elegiremos ""Guest" - "Install/Upgrade VMware Tools", es posible que nos
muestre un warning indicando:
Installing the VMware Tools package will greatly enhance graphics and mouse performance in your virtual machine. WARNING: You cannto install the VMware Tools package until the guest operating system is
running. If you guest operating system is not running, choose Cancel and install the VMware Tools package later.
Pulsaremos OK en el mensaje.
Si todo es correcto habrá montado una unidad de CD con las VMware Tools en la máquina virtual con Linux Fedora. Si no la ha montado la montaremos con:
Código:
mkdir cdrom
Código:
mount /dev/cdrom cdrom
Nos devolverá el mensaje:
mount: dispositivo de bloques /dev/sr0 está protegido contra escritura; se monta como sólo lectura
A continuación ya podremos acceder al CD con la VMware Tools:
Código:
cd cdrom
Haciendo un:
Código:
ls -lah
Obtendremos los ficheros de instalación de las VMware Tools:
dr-xr-xr-x 2 root root 2,0K ago 17 2013 .
drwxr-xr-x 3 root root 4,0K mar 24 12:19 ..
-r-xr-xr-x 1 root root 2,0K ago 17 2013 manifest.txt
-r--r--r-- 1 root root 1,9K ago 17 2013 run_upgrader.sh
-r--r--r-- 1 root root 60M ago 17 2013 VMwareTools-9.4.0-1280544.tar.gz
-r-xr-xr-x 1 root root 678K ago 17 2013 vmware-tools-upgrader-32
-r-xr-xr-x 1 root root 686K ago 17 2013 vmware-tools-upgrader-64
Copiaremos el fichero VMwareTools-9.4.0-1280544.tar.gz a la carpeta temporal del sistema con:
Código:
cp VMwareTools-9.4.0-1280544.tar.gz /tmp/
Descomprimiremos el fichero VMwareTools-9.4.0-1280544.tar.gz con:
Código:
tar xzvf VMwareTools-9.4.0-1280544.tar.gz
5. Por último lanzaremos el instalador de las VMware Tools con el siguiente comando (indicaremos el parámetro --default para que no nos pregunte nada e instale las VMware Tools con las opciones por defecto).
Antes de nada accederemos a la carpeta descomprimida anteriormente con:
Código:
cd vmware-tools-distrib/
Y lanzaremos el instalador con:
Código:
./vmware-install.pl --default
Publicado:
Lun Mar 24, 2014 10:43 am
alonsojpd Administrador/Moderador
Registrado: Sep 16, 2003 Mensajes: 2687
Asunto: Re: Instalar VMware Tools en Linux Fedora Core 8
Anuncios
Ten en cuenta que a veces no es necesario actualizar pues con la versión actual ya se instalan correctamente las VMware Tools, anteriormente te hemos mostrado todos los pasos (en el peor de los casos).
Te mostramos el resultado típico de la ejecución de la instalación de las VMware Tools:
[root@pclinuxfedora vmware-tools-distrib]# ./vmware-install.pl --default
Creating a new VMware Tools installer database using the tar4 format.
Installing VMware Tools.
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-tools]
The path "/usr/lib/vmware-tools" 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 documentation files?
[/usr/share/doc/vmware-tools]
The path "/usr/share/doc/vmware-tools" 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 Tools 9.4.0 build-1280544 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-tools.pl".
Before running VMware Tools for the first time, you need to configure it by
invoking the following command: "/usr/bin/vmware-config-tools.pl". Do you want
this program to invoke the command for you now? [yes]
Initializing...
Making sure services for VMware Tools are stopped.
Stopping VMware Tools services in the virtual machine:
Guest operating system daemon: [ OK ]
Unmounting HGFS shares: [ OK ]
Guest filesystem driver: [ OK ]
The VMware FileSystem Sync Driver (vmsync) allows external third-party backup
software that is integrated with vSphere to create backups of the virtual
machine. Do you wish to enable this feature? [no]
Using 2.6.x kernel build system.
make: se ingresa al directorio `/tmp/modconfig-FwGlia/vmci-only'
/usr/bin/make -C /lib/modules/2.6.26.8-57.fc8/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. \
MODULEBUILDDIR= modules
make[1]: se ingresa al directorio `/usr/src/kernels/2.6.26.8-57.fc8-i686'
CC [M] /tmp/modconfig-FwGlia/vmci-only/linux/driver.o
CC [M] /tmp/modconfig-FwGlia/vmci-only/linux/vmciKernelIf.o
CC [M] /tmp/modconfig-FwGlia/vmci-only/common/vmciContext.o
CC [M] /tmp/modconfig-FwGlia/vmci-only/common/vmciDatagram.o
CC [M] /tmp/modconfig-FwGlia/vmci-only/common/vmciDoorbell.o
CC [M] /tmp/modconfig-FwGlia/vmci-only/common/vmciDriver.o
CC [M] /tmp/modconfig-FwGlia/vmci-only/common/vmciEvent.o
CC [M] /tmp/modconfig-FwGlia/vmci-only/common/vmciHashtable.o
CC [M] /tmp/modconfig-FwGlia/vmci-only/common/vmciPageChannel.o
CC [M] /tmp/modconfig-FwGlia/vmci-only/common/vmciQPair.o
CC [M] /tmp/modconfig-FwGlia/vmci-only/common/vmciQueuePair.o
CC [M] /tmp/modconfig-FwGlia/vmci-only/common/vmciResource.o
CC [M] /tmp/modconfig-FwGlia/vmci-only/common/vmciRoute.o
CC [M] /tmp/modconfig-FwGlia/vmci-only/driverLog.o
LD [M] /tmp/modconfig-FwGlia/vmci-only/vmci.o
Building modules, stage 2.
MODPOST 1 modules
CC /tmp/modconfig-FwGlia/vmci-only/vmci.mod.o
LD [M] /tmp/modconfig-FwGlia/vmci-only/vmci.ko
make[1]: se sale del directorio `/usr/src/kernels/2.6.26.8-57.fc8-i686'
/usr/bin/make -C $PWD SRCROOT=$PWD/. \
MODULEBUILDDIR= postbuild
make[1]: se ingresa al directorio `/tmp/modconfig-FwGlia/vmci-only'
make[1]: `postbuild' está actualizado.
make[1]: se sale del directorio `/tmp/modconfig-FwGlia/vmci-only'
cp -f vmci.ko ./../vmci.o
make: se sale del directorio `/tmp/modconfig-FwGlia/vmci-only'
Using 2.6.x kernel build system.
make: se ingresa al directorio `/tmp/modconfig-mOlp94/vmci-only'
/usr/bin/make -C /lib/modules/2.6.26.8-57.fc8/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. \
MODULEBUILDDIR= modules
make[1]: se ingresa al directorio `/usr/src/kernels/2.6.26.8-57.fc8-i686'
CC [M] /tmp/modconfig-mOlp94/vmci-only/linux/driver.o
CC [M] /tmp/modconfig-mOlp94/vmci-only/linux/vmciKernelIf.o
CC [M] /tmp/modconfig-mOlp94/vmci-only/common/vmciContext.o
CC [M] /tmp/modconfig-mOlp94/vmci-only/common/vmciDatagram.o
CC [M] /tmp/modconfig-mOlp94/vmci-only/common/vmciDoorbell.o
CC [M] /tmp/modconfig-mOlp94/vmci-only/common/vmciDriver.o
CC [M] /tmp/modconfig-mOlp94/vmci-only/common/vmciEvent.o
CC [M] /tmp/modconfig-mOlp94/vmci-only/common/vmciHashtable.o
CC [M] /tmp/modconfig-mOlp94/vmci-only/common/vmciPageChannel.o
CC [M] /tmp/modconfig-mOlp94/vmci-only/common/vmciQPair.o
CC [M] /tmp/modconfig-mOlp94/vmci-only/common/vmciQueuePair.o
CC [M] /tmp/modconfig-mOlp94/vmci-only/common/vmciResource.o
CC [M] /tmp/modconfig-mOlp94/vmci-only/common/vmciRoute.o
CC [M] /tmp/modconfig-mOlp94/vmci-only/driverLog.o
LD [M] /tmp/modconfig-mOlp94/vmci-only/vmci.o
Building modules, stage 2.
MODPOST 1 modules
CC /tmp/modconfig-mOlp94/vmci-only/vmci.mod.o
LD [M] /tmp/modconfig-mOlp94/vmci-only/vmci.ko
make[1]: se sale del directorio `/usr/src/kernels/2.6.26.8-57.fc8-i686'
/usr/bin/make -C $PWD SRCROOT=$PWD/. \
MODULEBUILDDIR= postbuild
make[1]: se ingresa al directorio `/tmp/modconfig-mOlp94/vmci-only'
make[1]: `postbuild' está actualizado.
make[1]: se sale del directorio `/tmp/modconfig-mOlp94/vmci-only'
cp -f vmci.ko ./../vmci.o
make: se sale del directorio `/tmp/modconfig-mOlp94/vmci-only'
Using 2.6.x kernel build system.
make: se ingresa al directorio `/tmp/modconfig-mOlp94/vsock-only'
/usr/bin/make -C /lib/modules/2.6.26.8-57.fc8/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. \
MODULEBUILDDIR= modules
make[1]: se ingresa al directorio `/usr/src/kernels/2.6.26.8-57.fc8-i686'
CC [M] /tmp/modconfig-mOlp94/vsock-only/linux/af_vsock.o
CC [M] /tmp/modconfig-mOlp94/vsock-only/linux/notify.o
CC [M] /tmp/modconfig-mOlp94/vsock-only/linux/notifyQState.o
CC [M] /tmp/modconfig-mOlp94/vsock-only/linux/stats.o
CC [M] /tmp/modconfig-mOlp94/vsock-only/linux/util.o
CC [M] /tmp/modconfig-mOlp94/vsock-only/linux/vsockAddr.o
CC [M] /tmp/modconfig-mOlp94/vsock-only/driverLog.o
LD [M] /tmp/modconfig-mOlp94/vsock-only/vsock.o
Building modules, stage 2.
MODPOST 1 modules
CC /tmp/modconfig-mOlp94/vsock-only/vsock.mod.o
LD [M] /tmp/modconfig-mOlp94/vsock-only/vsock.ko
make[1]: se sale del directorio `/usr/src/kernels/2.6.26.8-57.fc8-i686'
/usr/bin/make -C $PWD SRCROOT=$PWD/. \
MODULEBUILDDIR= postbuild
make[1]: se ingresa al directorio `/tmp/modconfig-mOlp94/vsock-only'
make[1]: `postbuild' está actualizado.
make[1]: se sale del directorio `/tmp/modconfig-mOlp94/vsock-only'
cp -f vsock.ko ./../vsock.o
make: se sale del directorio `/tmp/modconfig-mOlp94/vsock-only'
Using 2.6.x kernel build system.
make: se ingresa al directorio `/tmp/modconfig-sLOdVG/vmxnet3-only'
/usr/bin/make -C /lib/modules/2.6.26.8-57.fc8/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. \
MODULEBUILDDIR= modules
make[1]: se ingresa al directorio `/usr/src/kernels/2.6.26.8-57.fc8-i686'
CC [M] /tmp/modconfig-sLOdVG/vmxnet3-only/vmxnet3_drv.o
CC [M] /tmp/modconfig-sLOdVG/vmxnet3-only/vmxnet3_ethtool.o
CC [M] /tmp/modconfig-sLOdVG/vmxnet3-only/vmxnet3_shm.o
LD [M] /tmp/modconfig-sLOdVG/vmxnet3-only/vmxnet3.o
Building modules, stage 2.
MODPOST 1 modules
CC /tmp/modconfig-sLOdVG/vmxnet3-only/vmxnet3.mod.o
LD [M] /tmp/modconfig-sLOdVG/vmxnet3-only/vmxnet3.ko
make[1]: se sale del directorio `/usr/src/kernels/2.6.26.8-57.fc8-i686'
/usr/bin/make -C $PWD SRCROOT=$PWD/. \
MODULEBUILDDIR= postbuild
make[1]: se ingresa al directorio `/tmp/modconfig-sLOdVG/vmxnet3-only'
make[1]: `postbuild' está actualizado.
make[1]: se sale del directorio `/tmp/modconfig-sLOdVG/vmxnet3-only'
cp -f vmxnet3.ko ./../vmxnet3.o
make: se sale del directorio `/tmp/modconfig-sLOdVG/vmxnet3-only'
The VMware pvscsi module is only supported on kernel version 2.6.32 and newer,
or rhel5 distributions.
Using 2.6.x kernel build system.
make: se ingresa al directorio `/tmp/modconfig-K7EQuK/vmmemctl-only'
/usr/bin/make -C /lib/modules/2.6.26.8-57.fc8/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. \
MODULEBUILDDIR= modules
make[1]: se ingresa al directorio `/usr/src/kernels/2.6.26.8-57.fc8-i686'
CC [M] /tmp/modconfig-K7EQuK/vmmemctl-only/backdoor_balloon.o
CC [M] /tmp/modconfig-K7EQuK/vmmemctl-only/backdoorGcc32.o
CC [M] /tmp/modconfig-K7EQuK/vmmemctl-only/kernelStubsLinux.o
CC [M] /tmp/modconfig-K7EQuK/vmmemctl-only/os.o
CC [M] /tmp/modconfig-K7EQuK/vmmemctl-only/vmballoon.o
LD [M] /tmp/modconfig-K7EQuK/vmmemctl-only/vmmemctl.o
Building modules, stage 2.
MODPOST 1 modules
CC /tmp/modconfig-K7EQuK/vmmemctl-only/vmmemctl.mod.o
LD [M] /tmp/modconfig-K7EQuK/vmmemctl-only/vmmemctl.ko
make[1]: se sale del directorio `/usr/src/kernels/2.6.26.8-57.fc8-i686'
/usr/bin/make -C $PWD SRCROOT=$PWD/. \
MODULEBUILDDIR= postbuild
make[1]: se ingresa al directorio `/tmp/modconfig-K7EQuK/vmmemctl-only'
make[1]: `postbuild' está actualizado.
make[1]: se sale del directorio `/tmp/modconfig-K7EQuK/vmmemctl-only'
cp -f vmmemctl.ko ./../vmmemctl.o
make: se sale del directorio `/tmp/modconfig-K7EQuK/vmmemctl-only'
The VMware Host-Guest Filesystem allows for shared folders between the host OS
and the guest OS in a Fusion or Workstation virtual environment. Do you wish
to enable this feature? [no]
Using 2.6.x kernel build system.
make: se ingresa al directorio `/tmp/modconfig-G4At1U/vmxnet-only'
/usr/bin/make -C /lib/modules/2.6.26.8-57.fc8/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. \
MODULEBUILDDIR= modules
make[1]: se ingresa al directorio `/usr/src/kernels/2.6.26.8-57.fc8-i686'
CC [M] /tmp/modconfig-G4At1U/vmxnet-only/vmxnet.o
Building modules, stage 2.
MODPOST 1 modules
CC /tmp/modconfig-G4At1U/vmxnet-only/vmxnet.mod.o
LD [M] /tmp/modconfig-G4At1U/vmxnet-only/vmxnet.ko
make[1]: se sale del directorio `/usr/src/kernels/2.6.26.8-57.fc8-i686'
/usr/bin/make -C $PWD SRCROOT=$PWD/. \
MODULEBUILDDIR= postbuild
make[1]: se ingresa al directorio `/tmp/modconfig-G4At1U/vmxnet-only'
make[1]: `postbuild' está actualizado.
make[1]: se sale del directorio `/tmp/modconfig-G4At1U/vmxnet-only'
cp -f vmxnet.ko ./../vmxnet.o
make: se sale del directorio `/tmp/modconfig-G4At1U/vmxnet-only'
The vmblock enables dragging or copying files between host and guest in a
Fusion or Workstation virtual environment. Do you wish to enable this feature?
[no]
VMware automatic kernel modules enables automatic building and installation of
VMware kernel modules at boot that are not already present. This feature can be
enabled/disabled by re-running vmware-config-tools.pl.
Would you like to enable VMware automatic kernel modules?
[no]
Detected X version 7.2.0
Unable to detect guest resolution.
Please choose one of the following display sizes that X will start with:
[1]< 640x480
[2] 800x600
[3] 1024x768
[4] 1280x800
Please enter a number between 1 and 4:
[1]
X is running fine with the new config file.
Creating a new initrd boot image for the kernel.
Checking acpi hot plug [ OK ]
Starting VMware Tools services in the virtual machine:
Switching to guest configuration: [ OK ]
Guest memory manager: [ OK ]
Guest vmxnet fast network device: [ OK ]
VM communication interface: [ OK ]
VM communication interface socket family: [ OK ]
Guest operating system daemon: [ OK ]
The configuration of VMware Tools 9.4.0 build-1280544 for Linux for this
running kernel completed successfully.
You must restart your X session before any mouse or graphics changes take
effect.
You can now run VMware Tools by invoking "/usr/bin/vmware-toolbox-cmd" from the
command line.
To enable advanced X features (e.g., guest resolution fit, drag and drop, and
file and text copy/paste), you will need to do one (or more) of the following:
1. Manually start /usr/bin/vmware-user
2. Log out and log back into your desktop session; and,
3. Restart your X session.
to use the vmxnet driver, either reboot or
1. stop networking or stop any interface using the vmxnet or pcnet32 driver
2. remove the pcnet32 module with 'rmmod pcnet32'
3. remove the vmxnet module with 'rmmod vmxnet'
4. load the vmxnet module with 'modprobe -v vmxnet'
5. and restart networking or restart the stopped network interfaces
Enjoy,
--the VMware team
Found VMware Tools CDROM mounted at /mnt/cdrom. Ejecting device /dev/sr0 ...
Puede publicar nuevos temas en este foro No puede responder a temas en este foro No puede editar sus mensajes en este foro No puede borrar sus mensajes en este foro No puede votar en encuestas en este foro
Visita nuestro nuevo sitio web con programas y contenidos actualizados: Proyecto A
