Guenadi N Jilevski's Oracle BLOG

Oracle RAC, DG, EBS, DR and HA DBA BLOG

Installing VMware Workstation 9.0.1 on Windows and creating OEL 6.3 x86_64 guest VM

Installing VMware Workstation 9.0.1 on Windows and creating OEL 6.3 x86_64 guest VM

In the article you will have a look at the steps to install VMware Workstation 9.0.1 on MS Windows and create an OEL 6.3 x86_64 guest VM. The following software will e used:

  • Oracle Enterprise Linux 6.3 x86_64 : download from edelivery.oracle.com
  • VMware® Workstation 9.0.1: Download trial from VMware.

The article will cover:

  1. VMware® Workstation 9.0.1 installation
  2. Creating OEL 6.3 VM

In the article I will install the latest version of VMware workstation for windows and will create a guest VM running OEL 6.3 x86_64.

  1. VMware® Workstation 9.0.1 installation

After downloading the software start VMware® Workstation installation.

If there are installed VMware server the installation will start with de-installing the VMware Server.


Continue with VMware workstation installation.


Select a Custom installation.


Specify the installation location.


Select the option to check for product upgrades.


Check help improve check box.



Press Continue to begin the process.


Wait for the installation to complete.



Exit the installation.


Start the VMware workstation


  1. Creating OEL 6.3 VM

Let’s create an OEL 6.3 VM by starting the VM wizard. Select Custom.


Select Hardware compatibility.


Specify the location for the downloaded OEL 6.4 iso file.


Specify a name for the virtual Machine and disk location folder.


Specify the number of processors.


Specify a memory


Specify a network type. Late you can add more network adapters.


Select controller type.


Select create a new virtual disk.


Select a disk type


Select size and type of the virtual disk


Specify the location of the virtual disk.


Use customize hardware to add more hardware.


Use the Add button to add hardware from the left pan.


I will add a network adapter.


I added the following network adapters as follows:


Start the VM


Press Continue.


Wait for the OEL screen to pop up and press Next.


Select language


Move Next


Select storage devices.


Discard the data


Specify the hostname


Select a time zone.


Specify the root password


Use the whole space from the disk.


Write changes to disk.


Select a database server and select customize now.


Select all the packages


Wait for the installation to complete.


Reboot


Press Forward


Agree to the agreement and press Forward.


Opt for a registration at a later time.


Connect later.


Press Fporward.


Enter additional user credentials.


Set date and time and configure NTP


Skip the kdump configuration and press Finish.


Wait to reboot.


Install VMware tools


Run the ./vmware-install.pl

[root@zeus u01]# cd vmware-tools-distrib

[root@zeus vmware-tools-distrib]# pwd

/u01/vmware-tools-distrib

[root@zeus vmware-tools-distrib]# ls

bin doc etc FILES INSTALL installer lib vmware-install.pl

[root@zeus vmware-tools-distrib]# ./vmware-install.pl

[root@zeus vmware-tools-distrib]# ./vmware-install.pl

A previous installation of VMware Tools has been detected.

The previous installation was made by the tar installer (version 4).

Keeping the tar4 installer database format.

You have a version of VMware Tools installed. Continuing this install will

first uninstall the currently installed version. Do you wish to continue?

(yes/no) [yes]

Uninstalling the tar installation of VMware Tools.

Stopping services for VMware Tools

Stopping VMware Tools services in the virtual machine:

Guest operating system daemon: [ OK ]

VMware User Agent (vmware-user): [ OK ]

Blocking file system: [ OK ]

Unmounting HGFS shares: [ OK ]

Guest filesystem driver: [ OK ]

VM communication interface socket family: [ OK ]

VM communication interface: [ OK ]

Stopping Thinprint services in the virtual machine:

Stopping Virtual Printing daemon: done

This program previously created the file

/usr/lib/vmware-tools/lib64/libconf/etc/pango/pango.modules, and was about to

remove it. Somebody else apparently did it already.

File /etc/vmware-tools/vmware-user.desktop is backed up to

/etc/vmware-tools/vmware-user.desktop.old.0.

File /usr/lib/vmware-tools/lib64/libconf/etc/gtk-2.0/gtk.immodules is backed up

to /usr/lib/vmware-tools/lib64/libconf/etc/gtk-2.0/gtk.immodules.old.0.

File /usr/lib/vmware-tools/lib64/libconf/etc/fonts/fonts.conf is backed up to

/usr/lib/vmware-tools/lib64/libconf/etc/fonts/fonts.conf.old.0.

File /usr/lib/vmware-tools/lib64/libconf/etc/gtk-2.0/gdk-pixbuf.loaders is

backed up to

/usr/lib/vmware-tools/lib64/libconf/etc/gtk-2.0/gdk-pixbuf.loaders.old.0.

This program previously created the file

/usr/lib/vmware-tools/libconf/etc/gtk-2.0/gdk-pixbuf.loaders, and was about to

remove it. Somebody else apparently did it already.

This program previously created the file

/usr/lib/vmware-tools/lib64/libconf/etc/pango/pangorc, and was about to remove

it. Somebody else apparently did it already.

This program previously created the file

/usr/lib/vmware-tools/libconf/etc/gtk-2.0/gtk.immodules, and was about to

remove it. Somebody else apparently did it already.

This program previously created the file

/usr/lib/vmware-tools/lib64/libconf/etc/pango/pangox.aliases, and was about to

remove it. Somebody else apparently did it already.

This program previously created the directory

/usr/lib/vmware-tools/lib64/libconf/etc/gtk-2.0, and was about to remove it.

Since there are files in that directory that this program did not create, it

will not be removed.

This program previously created the directory

/usr/lib/vmware-tools/lib64/libconf/etc/fonts, and was about to remove it.

Since there are files in that directory that this program did not create, it

will not be removed.

This program previously created the directory

/usr/lib/vmware-tools/lib/libtpvmlpd2.so, and was about to remove it. Somebody

else apparently did it already.

This program previously created the directory

/usr/lib/vmware-tools/lib64/libconf/etc, and was about to remove it. Since

there are files in that directory that this program did not create, it will not

be removed.

This program previously created the directory

/usr/lib/vmware-tools/lib/libtpvmgp.so, and was about to remove it. Somebody

else apparently did it already.

This program previously created the directory

/usr/lib/vmware-tools/lib64/libconf, and was about to remove it. Since there

are files in that directory that this program did not create, it will not be

removed.

This program previously created the directory /usr/lib/vmware-tools/lib64, and

was about to remove it. Since there are files in that directory that this

program did not create, it will not be removed.

This program previously created the directory /usr/lib/vmware-tools, and was

about to remove it. Since there are files in that directory that this program

did not create, it will not be removed.

File /etc/pulse/default.pa is backed up to /etc/pulse/default.pa.old.0.

The removal of VMware Tools 9.2.2 build-893683 for Linux completed

successfully.

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]

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.2.2 build-893683 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 Thinprint services in the virtual machine:

Stopping Virtual Printing daemon: done

Stopping VMware Tools services in the virtual machine:

Guest operating system daemon: [ OK ]

VMware User Agent (vmware-user): [ OK ]

Blocking file system: [ OK ]

Unmounting HGFS shares: [ OK ]

Guest filesystem driver: [ OK ]

VM communication interface socket family: [ OK ]

VM communication interface: [ 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]

Before you can compile modules, you need to have the following installed…

make

gcc

kernel headers of the running kernel

Searching for GCC…

Detected GCC binary at “/usr/bin/gcc”.

The path “/usr/bin/gcc” appears to be a valid path to the gcc binary.

Would you like to change it? [no]

Searching for a valid kernel header path…

Detected the kernel headers at

“/lib/modules/2.6.39-200.24.1.el6uek.x86_64/build/include”.

The path “/lib/modules/2.6.39-200.24.1.el6uek.x86_64/build/include” appears to

be a valid path to the 2.6.39-200.24.1.el6uek.x86_64 kernel headers.

Would you like to change it? [no]

Using 2.6.x kernel build system.

make: Entering directory `/tmp/modconfig-ipqWDR/vmci-only’

/usr/bin/make -C /lib/modules/2.6.39-200.24.1.el6uek.x86_64/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. \

     MODULEBUILDDIR= modules

make[1]: Entering directory `/usr/src/kernels/2.6.39-200.24.1.el6uek.x86_64′

CC [M] /tmp/modconfig-ipqWDR/vmci-only/linux/driver.o

CC [M] /tmp/modconfig-ipqWDR/vmci-only/linux/vmciKernelIf.o

CC [M] /tmp/modconfig-ipqWDR/vmci-only/common/vmciContext.o

CC [M] /tmp/modconfig-ipqWDR/vmci-only/common/vmciDatagram.o

CC [M] /tmp/modconfig-ipqWDR/vmci-only/common/vmciDoorbell.o

CC [M] /tmp/modconfig-ipqWDR/vmci-only/common/vmciDriver.o

CC [M] /tmp/modconfig-ipqWDR/vmci-only/common/vmciEvent.o

CC [M] /tmp/modconfig-ipqWDR/vmci-only/common/vmciHashtable.o

CC [M] /tmp/modconfig-ipqWDR/vmci-only/common/vmciQPair.o

CC [M] /tmp/modconfig-ipqWDR/vmci-only/common/vmciQueuePair.o

CC [M] /tmp/modconfig-ipqWDR/vmci-only/common/vmciResource.o

CC [M] /tmp/modconfig-ipqWDR/vmci-only/common/vmciRoute.o

CC [M] /tmp/modconfig-ipqWDR/vmci-only/driverLog.o

LD [M] /tmp/modconfig-ipqWDR/vmci-only/vmci.o

Building modules, stage 2.

MODPOST 1 modules

CC /tmp/modconfig-ipqWDR/vmci-only/vmci.mod.o

LD [M] /tmp/modconfig-ipqWDR/vmci-only/vmci.ko.unsigned

NO SIGN [M] /tmp/modconfig-ipqWDR/vmci-only/vmci.ko

make[1]: Leaving directory `/usr/src/kernels/2.6.39-200.24.1.el6uek.x86_64′

/usr/bin/make -C $PWD SRCROOT=$PWD/. \

     MODULEBUILDDIR= postbuild

make[1]: Entering directory `/tmp/modconfig-ipqWDR/vmci-only’

make[1]: `postbuild’ is up to date.

make[1]: Leaving directory `/tmp/modconfig-ipqWDR/vmci-only’

cp -f vmci.ko ./../vmci.o

make: Leaving directory `/tmp/modconfig-ipqWDR/vmci-only’

Using 2.6.x kernel build system.

make: Entering directory `/tmp/modconfig-8Gn05R/vmci-only’

/usr/bin/make -C /lib/modules/2.6.39-200.24.1.el6uek.x86_64/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. \

     MODULEBUILDDIR= modules

make[1]: Entering directory `/usr/src/kernels/2.6.39-200.24.1.el6uek.x86_64′

CC [M] /tmp/modconfig-8Gn05R/vmci-only/linux/driver.o

CC [M] /tmp/modconfig-8Gn05R/vmci-only/linux/vmciKernelIf.o

CC [M] /tmp/modconfig-8Gn05R/vmci-only/common/vmciContext.o

CC [M] /tmp/modconfig-8Gn05R/vmci-only/common/vmciDatagram.o

CC [M] /tmp/modconfig-8Gn05R/vmci-only/common/vmciDoorbell.o

CC [M] /tmp/modconfig-8Gn05R/vmci-only/common/vmciDriver.o

CC [M] /tmp/modconfig-8Gn05R/vmci-only/common/vmciEvent.o

CC [M] /tmp/modconfig-8Gn05R/vmci-only/common/vmciHashtable.o

CC [M] /tmp/modconfig-8Gn05R/vmci-only/common/vmciQPair.o

CC [M] /tmp/modconfig-8Gn05R/vmci-only/common/vmciQueuePair.o

CC [M] /tmp/modconfig-8Gn05R/vmci-only/common/vmciResource.o

CC [M] /tmp/modconfig-8Gn05R/vmci-only/common/vmciRoute.o

CC [M] /tmp/modconfig-8Gn05R/vmci-only/driverLog.o

LD [M] /tmp/modconfig-8Gn05R/vmci-only/vmci.o

Building modules, stage 2.

MODPOST 1 modules

CC /tmp/modconfig-8Gn05R/vmci-only/vmci.mod.o

LD [M] /tmp/modconfig-8Gn05R/vmci-only/vmci.ko.unsigned

NO SIGN [M] /tmp/modconfig-8Gn05R/vmci-only/vmci.ko

make[1]: Leaving directory `/usr/src/kernels/2.6.39-200.24.1.el6uek.x86_64′

/usr/bin/make -C $PWD SRCROOT=$PWD/. \

     MODULEBUILDDIR= postbuild

make[1]: Entering directory `/tmp/modconfig-8Gn05R/vmci-only’

make[1]: `postbuild’ is up to date.

make[1]: Leaving directory `/tmp/modconfig-8Gn05R/vmci-only’

cp -f vmci.ko ./../vmci.o

make: Leaving directory `/tmp/modconfig-8Gn05R/vmci-only’

Using 2.6.x kernel build system.

make: Entering directory `/tmp/modconfig-8Gn05R/vsock-only’

/usr/bin/make -C /lib/modules/2.6.39-200.24.1.el6uek.x86_64/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. \

     MODULEBUILDDIR= modules

make[1]: Entering directory `/usr/src/kernels/2.6.39-200.24.1.el6uek.x86_64′

CC [M] /tmp/modconfig-8Gn05R/vsock-only/linux/af_vsock.o

CC [M] /tmp/modconfig-8Gn05R/vsock-only/linux/notify.o

CC [M] /tmp/modconfig-8Gn05R/vsock-only/linux/notifyQState.o

CC [M] /tmp/modconfig-8Gn05R/vsock-only/linux/stats.o

CC [M] /tmp/modconfig-8Gn05R/vsock-only/linux/util.o

CC [M] /tmp/modconfig-8Gn05R/vsock-only/linux/vsockAddr.o

CC [M] /tmp/modconfig-8Gn05R/vsock-only/driverLog.o

LD [M] /tmp/modconfig-8Gn05R/vsock-only/vsock.o

Building modules, stage 2.

MODPOST 1 modules

CC /tmp/modconfig-8Gn05R/vsock-only/vsock.mod.o

LD [M] /tmp/modconfig-8Gn05R/vsock-only/vsock.ko.unsigned

NO SIGN [M] /tmp/modconfig-8Gn05R/vsock-only/vsock.ko

make[1]: Leaving directory `/usr/src/kernels/2.6.39-200.24.1.el6uek.x86_64′

/usr/bin/make -C $PWD SRCROOT=$PWD/. \

     MODULEBUILDDIR= postbuild

make[1]: Entering directory `/tmp/modconfig-8Gn05R/vsock-only’

make[1]: `postbuild’ is up to date.

make[1]: Leaving directory `/tmp/modconfig-8Gn05R/vsock-only’

cp -f vsock.ko ./../vsock.o

make: Leaving directory `/tmp/modconfig-8Gn05R/vsock-only’

The module vmxnet3 has already been installed on this system by another

installer or package and will not be modified by this installer. Use the flag

–clobber-kernel-modules=vmxnet3 to override.

The module pvscsi has already been installed on this system by another

installer or package and will not be modified by this installer. Use the flag

–clobber-kernel-modules=pvscsi to override.

The module vmmemctl has already been installed on this system by another

installer or package and will not be modified by this installer. Use the flag

–clobber-kernel-modules=vmmemctl to override.

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? [yes]

Using 2.6.x kernel build system.

make: Entering directory `/tmp/modconfig-I75ni0/vmci-only’

/usr/bin/make -C /lib/modules/2.6.39-200.24.1.el6uek.x86_64/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. \

     MODULEBUILDDIR= modules

make[1]: Entering directory `/usr/src/kernels/2.6.39-200.24.1.el6uek.x86_64′

CC [M] /tmp/modconfig-I75ni0/vmci-only/linux/driver.o

CC [M] /tmp/modconfig-I75ni0/vmci-only/linux/vmciKernelIf.o

CC [M] /tmp/modconfig-I75ni0/vmci-only/common/vmciContext.o

CC [M] /tmp/modconfig-I75ni0/vmci-only/common/vmciDatagram.o

CC [M] /tmp/modconfig-I75ni0/vmci-only/common/vmciDoorbell.o

CC [M] /tmp/modconfig-I75ni0/vmci-only/common/vmciDriver.o

CC [M] /tmp/modconfig-I75ni0/vmci-only/common/vmciEvent.o

CC [M] /tmp/modconfig-I75ni0/vmci-only/common/vmciHashtable.o

CC [M] /tmp/modconfig-I75ni0/vmci-only/common/vmciQPair.o

CC [M] /tmp/modconfig-I75ni0/vmci-only/common/vmciQueuePair.o

CC [M] /tmp/modconfig-I75ni0/vmci-only/common/vmciResource.o

CC [M] /tmp/modconfig-I75ni0/vmci-only/common/vmciRoute.o

CC [M] /tmp/modconfig-I75ni0/vmci-only/driverLog.o

LD [M] /tmp/modconfig-I75ni0/vmci-only/vmci.o

Building modules, stage 2.

MODPOST 1 modules

CC /tmp/modconfig-I75ni0/vmci-only/vmci.mod.o

LD [M] /tmp/modconfig-I75ni0/vmci-only/vmci.ko.unsigned

NO SIGN [M] /tmp/modconfig-I75ni0/vmci-only/vmci.ko

make[1]: Leaving directory `/usr/src/kernels/2.6.39-200.24.1.el6uek.x86_64′

/usr/bin/make -C $PWD SRCROOT=$PWD/. \

     MODULEBUILDDIR= postbuild

make[1]: Entering directory `/tmp/modconfig-I75ni0/vmci-only’

make[1]: `postbuild’ is up to date.

make[1]: Leaving directory `/tmp/modconfig-I75ni0/vmci-only’

cp -f vmci.ko ./../vmci.o

make: Leaving directory `/tmp/modconfig-I75ni0/vmci-only’

Using 2.6.x kernel build system.

make: Entering directory `/tmp/modconfig-I75ni0/vmhgfs-only’

/usr/bin/make -C /lib/modules/2.6.39-200.24.1.el6uek.x86_64/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. \

     MODULEBUILDDIR= modules

make[1]: Entering directory `/usr/src/kernels/2.6.39-200.24.1.el6uek.x86_64′

CC [M] /tmp/modconfig-I75ni0/vmhgfs-only/backdoor.o

CC [M] /tmp/modconfig-I75ni0/vmhgfs-only/backdoorGcc64.o

CC [M] /tmp/modconfig-I75ni0/vmhgfs-only/bdhandler.o

CC [M] /tmp/modconfig-I75ni0/vmhgfs-only/cpName.o

CC [M] /tmp/modconfig-I75ni0/vmhgfs-only/cpNameLinux.o

CC [M] /tmp/modconfig-I75ni0/vmhgfs-only/cpNameLite.o

CC [M] /tmp/modconfig-I75ni0/vmhgfs-only/dentry.o

CC [M] /tmp/modconfig-I75ni0/vmhgfs-only/dir.o

CC [M] /tmp/modconfig-I75ni0/vmhgfs-only/file.o

CC [M] /tmp/modconfig-I75ni0/vmhgfs-only/filesystem.o

CC [M] /tmp/modconfig-I75ni0/vmhgfs-only/fsutil.o

CC [M] /tmp/modconfig-I75ni0/vmhgfs-only/hgfsBd.o

CC [M] /tmp/modconfig-I75ni0/vmhgfs-only/hgfsEscape.o

CC [M] /tmp/modconfig-I75ni0/vmhgfs-only/hgfsUtil.o

CC [M] /tmp/modconfig-I75ni0/vmhgfs-only/inode.o

CC [M] /tmp/modconfig-I75ni0/vmhgfs-only/link.o

CC [M] /tmp/modconfig-I75ni0/vmhgfs-only/message.o

CC [M] /tmp/modconfig-I75ni0/vmhgfs-only/module.o

CC [M] /tmp/modconfig-I75ni0/vmhgfs-only/page.o

CC [M] /tmp/modconfig-I75ni0/vmhgfs-only/request.o

CC [M] /tmp/modconfig-I75ni0/vmhgfs-only/rpcout.o

CC [M] /tmp/modconfig-I75ni0/vmhgfs-only/stubs.o

CC [M] /tmp/modconfig-I75ni0/vmhgfs-only/super.o

CC [M] /tmp/modconfig-I75ni0/vmhgfs-only/tcp.o

CC [M] /tmp/modconfig-I75ni0/vmhgfs-only/transport.o

CC [M] /tmp/modconfig-I75ni0/vmhgfs-only/vmci.o

CC [M] /tmp/modconfig-I75ni0/vmhgfs-only/kernelStubsLinux.o

LD [M] /tmp/modconfig-I75ni0/vmhgfs-only/vmhgfs.o

Building modules, stage 2.

MODPOST 1 modules

CC /tmp/modconfig-I75ni0/vmhgfs-only/vmhgfs.mod.o

LD [M] /tmp/modconfig-I75ni0/vmhgfs-only/vmhgfs.ko.unsigned

NO SIGN [M] /tmp/modconfig-I75ni0/vmhgfs-only/vmhgfs.ko

make[1]: Leaving directory `/usr/src/kernels/2.6.39-200.24.1.el6uek.x86_64′

/usr/bin/make -C $PWD SRCROOT=$PWD/. \

     MODULEBUILDDIR= postbuild

make[1]: Entering directory `/tmp/modconfig-I75ni0/vmhgfs-only’

make[1]: `postbuild’ is up to date.

make[1]: Leaving directory `/tmp/modconfig-I75ni0/vmhgfs-only’

cp -f vmhgfs.ko ./../vmhgfs.o

make: Leaving directory `/tmp/modconfig-I75ni0/vmhgfs-only’

Using 2.6.x kernel build system.

make: Entering directory `/tmp/modconfig-apL14r/vmxnet-only’

/usr/bin/make -C /lib/modules/2.6.39-200.24.1.el6uek.x86_64/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. \

     MODULEBUILDDIR= modules

make[1]: Entering directory `/usr/src/kernels/2.6.39-200.24.1.el6uek.x86_64′

CC [M] /tmp/modconfig-apL14r/vmxnet-only/vmxnet.o

Building modules, stage 2.

MODPOST 1 modules

CC /tmp/modconfig-apL14r/vmxnet-only/vmxnet.mod.o

LD [M] /tmp/modconfig-apL14r/vmxnet-only/vmxnet.ko.unsigned

NO SIGN [M] /tmp/modconfig-apL14r/vmxnet-only/vmxnet.ko

make[1]: Leaving directory `/usr/src/kernels/2.6.39-200.24.1.el6uek.x86_64′

/usr/bin/make -C $PWD SRCROOT=$PWD/. \

     MODULEBUILDDIR= postbuild

make[1]: Entering directory `/tmp/modconfig-apL14r/vmxnet-only’

make[1]: `postbuild’ is up to date.

make[1]: Leaving directory `/tmp/modconfig-apL14r/vmxnet-only’

cp -f vmxnet.ko ./../vmxnet.o

make: Leaving directory `/tmp/modconfig-apL14r/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?

[yes]

!!! [EXPERIMENTAL] !!!

VMware automatic kernel modules enables automatic building and installation of

VMware kernel modules at boot that are not already present. By selecting yes,

you will be enabling this experimental feature. You can always disable this

feature by re-running vmware-config-tools.pl.

Would you like to enable VMware automatic kernel modules?

[no]

Thinprint provides driver-free printing. Do you wish to enable this feature?

[yes]

Disabling timer-based audio scheduling in pulseaudio.

Detected X server version 1.10.6

Distribution provided drivers for Xorg X server are used.

Skipping X configuration because X drivers are not included.

Creating a new initrd boot image for the kernel.

Starting Virtual Printing daemon: done

Checking acpi hot plug [ OK ]

Starting VMware Tools services in the virtual machine:

Switching to guest configuration: [ OK ]

VM communication interface: [ OK ]

VM communication interface socket family: [ OK ]

Guest filesystem driver: [ OK ]

Mounting HGFS shares: [FAILED]

Blocking file system: [ OK ]

VMware User Agent: [ OK ]

Guest operating system daemon: [ OK ]

The configuration of VMware Tools 9.2.2 build-893683 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.

Enjoy,

–the VMware team

[root@zeus vmware-tools-distrib]#

Reboot. And wait for the VMware tools to become active. Shutdown the Guest VM when done using it.


Summary

In the article you had a look at the steps for installing VMware workstation. You had a glimpse at the step-by-step installation of 64 bit OEL 6.3 as a guest OS.



December 18, 2012 - Posted by | oracle

1 Comment »

  1. […] online from here or download Installing VMware Workstation 9.0.1 on Windows and creating OEL 6.3 guest […]

    Pingback by Installing VMware Workstation 9.0.1 on Windows and creating OEL 6.3 x86_64 guest VM – Download « Guenadi N Jilevski's Oracle BLOG | December 18, 2012 | Reply


Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

Follow

Get every new post delivered to your Inbox.

Join 783 other followers

%d bloggers like this: