VMM create VM to VMware

I saw the article:
http://technet.microsoft.com/en-us/library/gg610683.aspx
When you import a VMware template to the VMM library, the .vmdk file is no longer copied to the library. Instead, VMM only copies the metadata that is associated with the template. The .vmdk file remains in the ESX datastore. Because
of this relationship, you can deploy virtual machines by using the template much more quickly. Also, when you import a VMware template, VMM no longer deletes the source template.
That means we could only import VMware template and create VM by VMM without .vmdk file in library?

This means that when you deploy a VM based on a VMware VM template, it will fetch the physical files from the ESX datastore, so that you don't need duplicate items across your environments.
-kn
Kristian (Virtualization and some coffee: http://kristiannese.blogspot.com )

Similar Messages

Create volumes on VMware datastore

Hi,
I have followed the vova documentation and deployed openstack in a testing environment.
I have created ubuntu images and using that I can launch new instances which seems to be working well. After launching the instance, I can see a folder with their id on the datastore which is defined in vcenter.
But when I create a new volume in openstack, I cannot see anything on the datastore or in the cinder-volumes?! I wonder if the creation of a volume without an instance is being done on the local disk of the vova vm? Also attaching a volume to an existing instance seems not doing anything.
Is there anyway to make sure where a volume has been created? and how can I make it to create the volume on the defined datastore which is being used for vm objects?
Thanks in advance.

Hi,
Thank you for your reply.
About attaching a volume, I created a screencast that I'm attaching to this post.
What I check to see if the volume has been attached or not is the below conditions:
     1. The web interface GUI shows no attachment for the volume.
     2. The "cinder list" command returns the volumes with the "attached to" field being empty.
     3. When I login to the nova instance, the command "fdisk -l" is not showing the device that I used in the "volume-attach" command.
and the problem is that even the command returns a "0" status which I assume it means the operation has been done successfully. (Not sure if it is the right way to check the result of my command?)
Thank you again for your time.

VMware Create mulitple VM at the same time

VMware could create multiple VMs using one template at the same time.
Is it possible for VMM to manage VMware and provide this feature? (i.e. create VMs on VMware using 1 template at the same time) thanks.

Hi,
this should work.
Not by using the VMM management console but check this:
http://social.technet.microsoft.com/Forums/en-US/9b0b6650-f4ee-435c-88a1-01e1921fcb67/could-vmm-2012-provision-multiple-vms-using-the-same-template-at-the-same-time?forum=virtualmachinemanager
http://technet.microsoft.com/en-us/library/dd349315.aspx
Regards
Sebastian

Open-vm-tools/official vmware tools not installing.

I'm trying to install the latest offical vmware tools (16/9/2013) and open-vm-tools but both seem to always fail. I tried some of the patches listed on the wiki, but nothing got me anywhere. The big thing I'm trying to accomplish is to be able to use vmhgfs but, I'd like to have all the tools if possible. Here is what I did.
Open Vm Tools
#[root@localhost] - [14-01-01 18:09:33] - [/home/toxicarrow/Documents/firewall] - [R:0]
pacman -S open-vm-tools open-vm-tools-dkms
resolving dependencies...
looking for inter-conflicts...
Packages (2): open-vm-tools-5:2013.09.16-5 open-vm-tools-dkms-5:2013.09.16-5
Total Installed Size: 8.21 MiB
:: Proceed with installation? [Y/n]
(2/2) checking keys in keyring [#####################################################################################################################] 100%
(2/2) checking package integrity [#####################################################################################################################] 100%
(2/2) loading package files [#####################################################################################################################] 100%
(2/2) checking for file conflicts [#####################################################################################################################] 100%
(2/2) checking available disk space [#####################################################################################################################] 100%
(1/2) installing open-vm-tools [#####################################################################################################################] 100%
>>>
>>> You can mount VMware Shared Folders via:
>>> mount -t vmhgfs .host:/ /mnt/hgfs
>>>
>>> or by adding this line to /etc/fstab:
>>> .host:/ /mnt/hgfs vmhgfs defaults 0 0
>>>
Optional dependencies for open-vm-tools
gtkmm [installed]
libnotify [installed]
libxtst [installed]
fuse [installed]
libsm [installed]
open-vm-tools-modules: for linux kernel
open-vm-tools-dkms: for linux-lts and other kernels [pending]
netctl: suspend-resume network state [installed]
networkmanager: suspend-resume network state
(2/2) installing open-vm-tools-dkms [#####################################################################################################################] 100%
>>> Enable building of open-vm-tools modules:
>>> $ dkms add open-vm-tools/2013.09.16
>>>
>>> Enabling vmxnet driver in /usr/lib/modprobe.d/open-vm-tools-modules.conf
>>> (this will disable pcnet32 driver)
>>>
>>> If vmxnet driver doesn't handle your NIC, you have to manually
>>> disable loading of pcnet32 driver
>>>
#[root@localhost] - [14-01-01 18:09:47] - [/home/toxicarrow/Documents/firewall] - [R:0]
pacman -S open-vm-tools-modules
warning: open-vm-tools-dkms-5:2013.09.16-5 is up to date -- reinstalling
resolving dependencies...
looking for inter-conflicts...
Packages (1): open-vm-tools-dkms-5:2013.09.16-5
Total Installed Size: 5.57 MiB
Net Upgrade Size: 0.00 MiB
:: Proceed with installation? [Y/n]
(1/1) checking keys in keyring [#####################################################################################################################] 100%
(1/1) checking package integrity [#####################################################################################################################] 100%
(1/1) loading package files [#####################################################################################################################] 100%
(1/1) checking for file conflicts [#####################################################################################################################] 100%
(1/1) checking available disk space [#####################################################################################################################] 100%
(1/1) reinstalling open-vm-tools-dkms [#####################################################################################################################] 100%
>>> Enable building of open-vm-tools modules:
>>> $ dkms add open-vm-tools/2013.09.16
>>>
#[root@localhost] - [14-01-01 18:10:14] - [/home/toxicarrow/Documents/firewall] - [R:0]
dkms install -m open-vm-tools -v 2013.04.16 -k $(uname -r)
Error! Could not find module source directory.
Directory: /usr/src/open-vm-tools-2013.04.16 does not exist.
#[root@localhost] - [14-01-01 18:13:14] - [/home/toxicarrow/Documents/firewall] - [R:2]
dkms install -m open-vm-tools -v 2013.09.16 -k $(uname -r)
Kernel preparation unnecessary for this kernel. Skipping...
Building module:
cleaning build area....
make KERNELRELEASE=3.12.6-1-ARCH VM_UNAME=3.12.6-1-ARCH MODULEBUILDDIR=/var/lib/dkms/open-vm-tools/2013.09.16/build -C vmblock; make VM_UNAME=3.12.6-1-ARCH MODULEBUILDDIR=/var/lib/dkms/open-vm-tools/2013.09.16/build -C vmci; make VM_UNAME=3.12.6-1-ARCH MODULEBUILDDIR=/var/lib/dkms/open-vm-tools/2013.09.16/build -C vmhgfs; make VM_UNAME=3.12.6-1-ARCH MODULEBUILDDIR=/var/lib/dkms/open-vm-tools/2013.09.16/build -C vmsync; make VM_UNAME=3.12.6-1-ARCH MODULEBUILDDIR=/var/lib/dkms/open-vm-tools/2013.09.16/build -C vmxnet; make VM_UNAME=3.12.6-1-ARCH MODULEBUILDDIR=/var/lib/dkms/open-vm-tools/2013.09.16/build -C vsock........
Error! Build of vmblock.ko failed for: 3.12.6-1-ARCH (x86_64)
Consult the make.log in the build directory
/var/lib/dkms/open-vm-tools/2013.09.16/build/ for more information.
#[root@localhost] - [14-01-01 18:13:45] - [/home/toxicarrow/Documents/firewall] - [R:7]
Official Tools
Before patches
#[root@localhost] - [14-01-02 2:40:49] - [/home/toxicarrow/vmware/vmware-tools-distrib] - [R:32]
./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: done
Unmounting HGFS shares: done
Guest filesystem driver: done
VM communication interface socket family: done
VM communication interface: done
Stopping Thinprint services in the virtual machine:
Stopping Virtual Printing daemon: done
The removal of VMware Tools 9.6.1 build-1378637 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/init.d]
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-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.6.1 build-1378637 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: done
Unmounting HGFS shares: done
Guest filesystem driver: done
VM communication interface socket family: done
VM communication interface: done
Stopping Thinprint services in the virtual machine:
Stopping Virtual Printing daemon: done
sh: : command not found
sh: : command not found
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 "/bin/gcc".
The path "/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/3.12.6-1-ARCH/build/include".
The path "/lib/modules/3.12.6-1-ARCH/build/include" appears to be a valid path
to the 3.12.6-1-ARCH kernel headers.
Would you like to change it? [no]
make: Entering directory '/tmp/modconfig-lyoMIO/vmci-only'
Using 2.6.x kernel build system.
/bin/make -C /lib/modules/3.12.6-1-ARCH/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. \
MODULEBUILDDIR= modules
make[1]: Entering directory '/usr/src/linux-3.12.6-1-ARCH'
CC [M] /tmp/modconfig-lyoMIO/vmci-only/linux/driver.o
CC [M] /tmp/modconfig-lyoMIO/vmci-only/linux/vmciKernelIf.o
CC [M] /tmp/modconfig-lyoMIO/vmci-only/common/vmciDriver.o
CC [M] /tmp/modconfig-lyoMIO/vmci-only/common/vmciResource.o
CC [M] /tmp/modconfig-lyoMIO/vmci-only/common/vmciRoute.o
CC [M] /tmp/modconfig-lyoMIO/vmci-only/common/vmciContext.o
CC [M] /tmp/modconfig-lyoMIO/vmci-only/common/vmciDatagram.o
CC [M] /tmp/modconfig-lyoMIO/vmci-only/common/vmciHashtable.o
CC [M] /tmp/modconfig-lyoMIO/vmci-only/common/vmciEvent.o
CC [M] /tmp/modconfig-lyoMIO/vmci-only/common/vmciQueuePair.o
CC [M] /tmp/modconfig-lyoMIO/vmci-only/common/vmciQPair.o
CC [M] /tmp/modconfig-lyoMIO/vmci-only/common/vmciDoorbell.o
CC [M] /tmp/modconfig-lyoMIO/vmci-only/driverLog.o
LD [M] /tmp/modconfig-lyoMIO/vmci-only/vmci.o
Building modules, stage 2.
MODPOST 1 modules
CC /tmp/modconfig-lyoMIO/vmci-only/vmci.mod.o
LD [M] /tmp/modconfig-lyoMIO/vmci-only/vmci.ko
make[1]: Leaving directory '/usr/src/linux-3.12.6-1-ARCH'
/bin/make -C $PWD SRCROOT=$PWD/. \
MODULEBUILDDIR= postbuild
make[1]: Entering directory '/tmp/modconfig-lyoMIO/vmci-only'
make[1]: 'postbuild' is up to date.
make[1]: Leaving directory '/tmp/modconfig-lyoMIO/vmci-only'
cp -f vmci.ko ./../vmci.o
make: Leaving directory '/tmp/modconfig-lyoMIO/vmci-only'
make: Entering directory '/tmp/modconfig-VlEWPD/vmci-only'
Using 2.6.x kernel build system.
/bin/make -C /lib/modules/3.12.6-1-ARCH/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. \
MODULEBUILDDIR= modules
make[1]: Entering directory '/usr/src/linux-3.12.6-1-ARCH'
CC [M] /tmp/modconfig-VlEWPD/vmci-only/linux/driver.o
CC [M] /tmp/modconfig-VlEWPD/vmci-only/linux/vmciKernelIf.o
CC [M] /tmp/modconfig-VlEWPD/vmci-only/common/vmciDriver.o
CC [M] /tmp/modconfig-VlEWPD/vmci-only/common/vmciResource.o
CC [M] /tmp/modconfig-VlEWPD/vmci-only/common/vmciRoute.o
CC [M] /tmp/modconfig-VlEWPD/vmci-only/common/vmciContext.o
CC [M] /tmp/modconfig-VlEWPD/vmci-only/common/vmciDatagram.o
CC [M] /tmp/modconfig-VlEWPD/vmci-only/common/vmciHashtable.o
CC [M] /tmp/modconfig-VlEWPD/vmci-only/common/vmciEvent.o
CC [M] /tmp/modconfig-VlEWPD/vmci-only/common/vmciQueuePair.o
CC [M] /tmp/modconfig-VlEWPD/vmci-only/common/vmciQPair.o
CC [M] /tmp/modconfig-VlEWPD/vmci-only/common/vmciDoorbell.o
CC [M] /tmp/modconfig-VlEWPD/vmci-only/driverLog.o
LD [M] /tmp/modconfig-VlEWPD/vmci-only/vmci.o
Building modules, stage 2.
MODPOST 1 modules
CC /tmp/modconfig-VlEWPD/vmci-only/vmci.mod.o
LD [M] /tmp/modconfig-VlEWPD/vmci-only/vmci.ko
make[1]: Leaving directory '/usr/src/linux-3.12.6-1-ARCH'
/bin/make -C $PWD SRCROOT=$PWD/. \
MODULEBUILDDIR= postbuild
make[1]: Entering directory '/tmp/modconfig-VlEWPD/vmci-only'
make[1]: 'postbuild' is up to date.
make[1]: Leaving directory '/tmp/modconfig-VlEWPD/vmci-only'
cp -f vmci.ko ./../vmci.o
make: Leaving directory '/tmp/modconfig-VlEWPD/vmci-only'
make: Entering directory '/tmp/modconfig-VlEWPD/vsock-only'
Using 2.6.x kernel build system.
/bin/make -C /lib/modules/3.12.6-1-ARCH/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. \
MODULEBUILDDIR= modules
make[1]: Entering directory '/usr/src/linux-3.12.6-1-ARCH'
CC [M] /tmp/modconfig-VlEWPD/vsock-only/linux/af_vsock.o
CC [M] /tmp/modconfig-VlEWPD/vsock-only/linux/vsockAddr.o
CC [M] /tmp/modconfig-VlEWPD/vsock-only/linux/notifyQState.o
CC [M] /tmp/modconfig-VlEWPD/vsock-only/linux/util.o
CC [M] /tmp/modconfig-VlEWPD/vsock-only/linux/stats.o
CC [M] /tmp/modconfig-VlEWPD/vsock-only/linux/notify.o
CC [M] /tmp/modconfig-VlEWPD/vsock-only/driverLog.o
LD [M] /tmp/modconfig-VlEWPD/vsock-only/vsock.o
Building modules, stage 2.
MODPOST 1 modules
CC /tmp/modconfig-VlEWPD/vsock-only/vsock.mod.o
LD [M] /tmp/modconfig-VlEWPD/vsock-only/vsock.ko
make[1]: Leaving directory '/usr/src/linux-3.12.6-1-ARCH'
/bin/make -C $PWD SRCROOT=$PWD/. \
MODULEBUILDDIR= postbuild
make[1]: Entering directory '/tmp/modconfig-VlEWPD/vsock-only'
make[1]: 'postbuild' is up to date.
make[1]: Leaving directory '/tmp/modconfig-VlEWPD/vsock-only'
cp -f vsock.ko ./../vsock.o
make: Leaving directory '/tmp/modconfig-VlEWPD/vsock-only'
The module vmxnet3 from this package is not supported for kernels >= 3.10.
Please enable this module in your kernel. You may also have to enable
HYPERVISOR_GUEST.
The module pvscsi from this package is not supported for kernels >= 3.10.
Please enable this module in your kernel. You may also have to enable
HYPERVISOR_GUEST.
The module vmmemctl from this package is not supported for kernels >= 3.10.
Please enable this module in your kernel. You may also have to enable
HYPERVISOR_GUEST.
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]
make: Entering directory '/tmp/modconfig-C1YUSD/vmci-only'
Using 2.6.x kernel build system.
/bin/make -C /lib/modules/3.12.6-1-ARCH/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. \
MODULEBUILDDIR= modules
make[1]: Entering directory '/usr/src/linux-3.12.6-1-ARCH'
CC [M] /tmp/modconfig-C1YUSD/vmci-only/linux/driver.o
CC [M] /tmp/modconfig-C1YUSD/vmci-only/linux/vmciKernelIf.o
CC [M] /tmp/modconfig-C1YUSD/vmci-only/common/vmciDriver.o
CC [M] /tmp/modconfig-C1YUSD/vmci-only/common/vmciResource.o
CC [M] /tmp/modconfig-C1YUSD/vmci-only/common/vmciRoute.o
CC [M] /tmp/modconfig-C1YUSD/vmci-only/common/vmciContext.o
CC [M] /tmp/modconfig-C1YUSD/vmci-only/common/vmciDatagram.o
CC [M] /tmp/modconfig-C1YUSD/vmci-only/common/vmciHashtable.o
CC [M] /tmp/modconfig-C1YUSD/vmci-only/common/vmciEvent.o
CC [M] /tmp/modconfig-C1YUSD/vmci-only/common/vmciQueuePair.o
CC [M] /tmp/modconfig-C1YUSD/vmci-only/common/vmciQPair.o
CC [M] /tmp/modconfig-C1YUSD/vmci-only/common/vmciDoorbell.o
CC [M] /tmp/modconfig-C1YUSD/vmci-only/driverLog.o
LD [M] /tmp/modconfig-C1YUSD/vmci-only/vmci.o
Building modules, stage 2.
MODPOST 1 modules
CC /tmp/modconfig-C1YUSD/vmci-only/vmci.mod.o
LD [M] /tmp/modconfig-C1YUSD/vmci-only/vmci.ko
make[1]: Leaving directory '/usr/src/linux-3.12.6-1-ARCH'
/bin/make -C $PWD SRCROOT=$PWD/. \
MODULEBUILDDIR= postbuild
make[1]: Entering directory '/tmp/modconfig-C1YUSD/vmci-only'
make[1]: 'postbuild' is up to date.
make[1]: Leaving directory '/tmp/modconfig-C1YUSD/vmci-only'
cp -f vmci.ko ./../vmci.o
make: Leaving directory '/tmp/modconfig-C1YUSD/vmci-only'
make: Entering directory '/tmp/modconfig-C1YUSD/vmhgfs-only'
Using 2.6.x kernel build system.
/bin/make -C /lib/modules/3.12.6-1-ARCH/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. \
MODULEBUILDDIR= modules
make[1]: Entering directory '/usr/src/linux-3.12.6-1-ARCH'
CC [M] /tmp/modconfig-C1YUSD/vmhgfs-only/message.o
CC [M] /tmp/modconfig-C1YUSD/vmhgfs-only/rpcout.o
CC [M] /tmp/modconfig-C1YUSD/vmhgfs-only/hgfsUtil.o
CC [M] /tmp/modconfig-C1YUSD/vmhgfs-only/cpName.o
CC [M] /tmp/modconfig-C1YUSD/vmhgfs-only/request.o
CC [M] /tmp/modconfig-C1YUSD/vmhgfs-only/stubs.o
CC [M] /tmp/modconfig-C1YUSD/vmhgfs-only/link.o
CC [M] /tmp/modconfig-C1YUSD/vmhgfs-only/bdhandler.o
CC [M] /tmp/modconfig-C1YUSD/vmhgfs-only/transport.o
CC [M] /tmp/modconfig-C1YUSD/vmhgfs-only/module.o
CC [M] /tmp/modconfig-C1YUSD/vmhgfs-only/file.o
CC [M] /tmp/modconfig-C1YUSD/vmhgfs-only/super.o
CC [M] /tmp/modconfig-C1YUSD/vmhgfs-only/vmci.o
CC [M] /tmp/modconfig-C1YUSD/vmhgfs-only/dir.o
CC [M] /tmp/modconfig-C1YUSD/vmhgfs-only/fsutil.o
CC [M] /tmp/modconfig-C1YUSD/vmhgfs-only/cpNameLinux.o
CC [M] /tmp/modconfig-C1YUSD/vmhgfs-only/hgfsBd.o
CC [M] /tmp/modconfig-C1YUSD/vmhgfs-only/filesystem.o
CC [M] /tmp/modconfig-C1YUSD/vmhgfs-only/page.o
CC [M] /tmp/modconfig-C1YUSD/vmhgfs-only/backdoorGcc64.o
CC [M] /tmp/modconfig-C1YUSD/vmhgfs-only/backdoor.o
CC [M] /tmp/modconfig-C1YUSD/vmhgfs-only/hgfsEscape.o
CC [M] /tmp/modconfig-C1YUSD/vmhgfs-only/inode.o
CC [M] /tmp/modconfig-C1YUSD/vmhgfs-only/dentry.o
CC [M] /tmp/modconfig-C1YUSD/vmhgfs-only/cpNameLite.o
CC [M] /tmp/modconfig-C1YUSD/vmhgfs-only/kernelStubsLinux.o
LD [M] /tmp/modconfig-C1YUSD/vmhgfs-only/vmhgfs.o
Building modules, stage 2.
MODPOST 1 modules
CC /tmp/modconfig-C1YUSD/vmhgfs-only/vmhgfs.mod.o
LD [M] /tmp/modconfig-C1YUSD/vmhgfs-only/vmhgfs.ko
make[1]: Leaving directory '/usr/src/linux-3.12.6-1-ARCH'
/bin/make -C $PWD SRCROOT=$PWD/. \
MODULEBUILDDIR= postbuild
make[1]: Entering directory '/tmp/modconfig-C1YUSD/vmhgfs-only'
make[1]: 'postbuild' is up to date.
make[1]: Leaving directory '/tmp/modconfig-C1YUSD/vmhgfs-only'
cp -f vmhgfs.ko ./../vmhgfs.o
make: Leaving directory '/tmp/modconfig-C1YUSD/vmhgfs-only'
The vmxnet driver is no longer supported on kernels 3.3 and greater. Please
upgrade to a newer virtual NIC. (e.g., vmxnet3 or e1000e)
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]
NOTICE: It appears your system does not have the required fuse packages
installed. The VMware blocking filesystem requires the fuse packages and its
libraries to function properly. Please install the fuse or fuse-utils package
using your systems package management utility and re-run this script in order
to enable the VMware blocking filesystem.
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 server version 1.14.5
Distribution provided drivers for Xorg X server are used.
Skipping X configuration because X drivers are not included.
Warning: This script could not find mkinitrd or update-initramfs and cannot
remake the initrd file!
Checking acpi hot plug done
Starting VMware Tools services in the virtual machine:
Switching to guest configuration: done
VM communication interface: done
VM communication interface socket family: failed
Guest filesystem driver: failed
Mounting HGFS shares: failed
VMware User Agent: done
Guest operating system daemon: done
Unable to start services for VMware Tools
Execution aborted.
After patches
#[root@localhost] - [14-01-02 2:44:39] - [/home/toxicarrow/vmware] - [R:0]
git clone https://github.com/rasa/vmware-tools-patches.git
Cloning into 'vmware-tools-patches'...
remote: Reusing existing pack: 134, done.
remote: Total 134 (delta 0), reused 0 (delta 0)
Receiving objects: 100% (134/134), 22.06 KiB | 0 bytes/s, done.
Resolving deltas: 100% (74/74), done.
Checking connectivity... done.
#[root@localhost] - [14-01-02 2:44:55] - [/home/toxicarrow/vmware] - [R:0]
ls
= VMwareTools-9.6.1-1378637.tar.gz manifest.txt* run_upgrader.sh vmware-tools-distrib/ vmware-tools-patches/ vmware-tools-upgrader-32* vmware-tools-upgrader-64*
#[root@localhost] - [14-01-02 2:44:57] - [/home/toxicarrow/vmware] - [R:0]
cp VMwareTools-9.6.1-1378637.tar.gz vmware-tools-patches
#[root@localhost] - [14-01-02 2:45:13] - [/home/toxicarrow/vmware] - [R:0]
cd vmware-tools-patches
#[root@localhost] - [14-01-02 2:45:17] - [/home/toxicarrow/vmware/vmware-tools-patches] - [R:0]
ls
LICENSE VMwareTools-9.6.1-1378637.tar.gz patch-module.sh* patches/ untar-and-patch-and-compile.sh*
README.md download-patches.sh* patch-modules.sh* untar-all-and-patch.sh* untar-and-patch.sh*
#[root@localhost] - [14-01-02 2:45:18] - [/home/toxicarrow/vmware/vmware-tools-patches] - [R:0]
./untar-and-patch-and-compile.sh
=== Patching ./VMwareTools-9.6.1-1378637.tar.gz ...
--- Applying vmci/vmware9.k3.8rc4.patch ...
patching file linux/driver.c
Hunk #1 FAILED at 124.
Hunk #2 FAILED at 1750.
Hunk #3 FAILED at 1978.
3 out of 3 hunks FAILED -- saving rejects to file linux/driver.c.rej
--- Applying vmhgfs/vmhgfs-uid-gid-kernel-3.12-tools-9.6.1.patch ...
patching file file.c
patching file filesystem.c
patching file fsutil.c
patching file inode.c
Hunk #1 succeeded at 514 (offset -3 lines).
Hunk #2 succeeded at 617 (offset -3 lines).
Hunk #3 succeeded at 1216 (offset -3 lines).
patching file shared/compat_cred.h
--- Applying vmhgfs/vmhgfs-d_count-kernel-3.11-tools-9.6.0.patch ...
patching file inode.c
Hunk #1 succeeded at 31 with fuzz 1.
Hunk #2 FAILED at 1893.
Hunk #3 FAILED at 1946.
2 out of 3 hunks FAILED -- saving rejects to file inode.c.rej
--- Applying vmhgfs/vmware9.compat_mm.patch ...
patching file shared/compat_mm.h
Hunk #1 FAILED at 91.
Hunk #2 FAILED at 100.
2 out of 2 hunks FAILED -- saving rejects to file shared/compat_mm.h.rej
--- Applying vmhgfs/patch_inode.c.patch ...
patching file inode.c
Hunk #1 FAILED at 1798.
Hunk #2 FAILED at 1818.
2 out of 2 hunks FAILED -- saving rejects to file inode.c.rej
--- Applying vmblock/vmblock.3.11.patch ...
patching file linux/file.c
--- Applying vmblock/vmblock.3.10.patch ...
patching file linux/control.c
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/init.d]
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-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.6.1 build-1378637 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: done
Unmounting HGFS shares: done
Guest filesystem driver: done
Stopping Thinprint services in the virtual machine:
Stopping Virtual Printing daemon: done
sh: : command not found
sh: : command not found
make: Entering directory '/tmp/modconfig-HrsGw6/vmci-only'
Using 2.6.x kernel build system.
/bin/make -C /lib/modules/3.12.6-1-ARCH/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. \
MODULEBUILDDIR= modules
make[1]: Entering directory '/usr/src/linux-3.12.6-1-ARCH'
CC [M] /tmp/modconfig-HrsGw6/vmci-only/linux/driver.o
CC [M] /tmp/modconfig-HrsGw6/vmci-only/linux/vmciKernelIf.o
CC [M] /tmp/modconfig-HrsGw6/vmci-only/common/vmciDriver.o
CC [M] /tmp/modconfig-HrsGw6/vmci-only/common/vmciResource.o
CC [M] /tmp/modconfig-HrsGw6/vmci-only/common/vmciContext.o
CC [M] /tmp/modconfig-HrsGw6/vmci-only/common/vmciDatagram.o
CC [M] /tmp/modconfig-HrsGw6/vmci-only/common/vmciHashtable.o
CC [M] /tmp/modconfig-HrsGw6/vmci-only/common/vmciEvent.o
CC [M] /tmp/modconfig-HrsGw6/vmci-only/common/vmciQueuePair.o
CC [M] /tmp/modconfig-HrsGw6/vmci-only/common/vmciDoorbell.o
CC [M] /tmp/modconfig-HrsGw6/vmci-only/common/vmciQPair.o
CC [M] /tmp/modconfig-HrsGw6/vmci-only/common/vmciRoute.o
CC [M] /tmp/modconfig-HrsGw6/vmci-only/driverLog.o
LD [M] /tmp/modconfig-HrsGw6/vmci-only/vmci.o
Building modules, stage 2.
MODPOST 1 modules
CC /tmp/modconfig-HrsGw6/vmci-only/vmci.mod.o
LD [M] /tmp/modconfig-HrsGw6/vmci-only/vmci.ko
make[1]: Leaving directory '/usr/src/linux-3.12.6-1-ARCH'
/bin/make -C $PWD SRCROOT=$PWD/. \
MODULEBUILDDIR= postbuild
make[1]: Entering directory '/tmp/modconfig-HrsGw6/vmci-only'
make[1]: 'postbuild' is up to date.
make[1]: Leaving directory '/tmp/modconfig-HrsGw6/vmci-only'
cp -f vmci.ko ./../vmci.o
make: Leaving directory '/tmp/modconfig-HrsGw6/vmci-only'
make: Entering directory '/tmp/modconfig-pVUBEq/vmci-only'
Using 2.6.x kernel build system.
/bin/make -C /lib/modules/3.12.6-1-ARCH/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. \
MODULEBUILDDIR= modules
make[1]: Entering directory '/usr/src/linux-3.12.6-1-ARCH'
CC [M] /tmp/modconfig-pVUBEq/vmci-only/linux/driver.o
CC [M] /tmp/modconfig-pVUBEq/vmci-only/linux/vmciKernelIf.o
CC [M] /tmp/modconfig-pVUBEq/vmci-only/common/vmciDriver.o
CC [M] /tmp/modconfig-pVUBEq/vmci-only/common/vmciResource.o
CC [M] /tmp/modconfig-pVUBEq/vmci-only/common/vmciContext.o
CC [M] /tmp/modconfig-pVUBEq/vmci-only/common/vmciDatagram.o
CC [M] /tmp/modconfig-pVUBEq/vmci-only/common/vmciHashtable.o
CC [M] /tmp/modconfig-pVUBEq/vmci-only/common/vmciEvent.o
CC [M] /tmp/modconfig-pVUBEq/vmci-only/common/vmciQueuePair.o
CC [M] /tmp/modconfig-pVUBEq/vmci-only/common/vmciDoorbell.o
CC [M] /tmp/modconfig-pVUBEq/vmci-only/common/vmciQPair.o
CC [M] /tmp/modconfig-pVUBEq/vmci-only/common/vmciRoute.o
CC [M] /tmp/modconfig-pVUBEq/vmci-only/driverLog.o
LD [M] /tmp/modconfig-pVUBEq/vmci-only/vmci.o
Building modules, stage 2.
MODPOST 1 modules
CC /tmp/modconfig-pVUBEq/vmci-only/vmci.mod.o
LD [M] /tmp/modconfig-pVUBEq/vmci-only/vmci.ko
make[1]: Leaving directory '/usr/src/linux-3.12.6-1-ARCH'
/bin/make -C $PWD SRCROOT=$PWD/. \
MODULEBUILDDIR= postbuild
make[1]: Entering directory '/tmp/modconfig-pVUBEq/vmci-only'
make[1]: 'postbuild' is up to date.
make[1]: Leaving directory '/tmp/modconfig-pVUBEq/vmci-only'
cp -f vmci.ko ./../vmci.o
make: Leaving directory '/tmp/modconfig-pVUBEq/vmci-only'
make: Entering directory '/tmp/modconfig-pVUBEq/vsock-only'
Using 2.6.x kernel build system.
/bin/make -C /lib/modules/3.12.6-1-ARCH/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. \
MODULEBUILDDIR= modules
make[1]: Entering directory '/usr/src/linux-3.12.6-1-ARCH'
CC [M] /tmp/modconfig-pVUBEq/vsock-only/linux/af_vsock.o
CC [M] /tmp/modconfig-pVUBEq/vsock-only/linux/vsockAddr.o
CC [M] /tmp/modconfig-pVUBEq/vsock-only/linux/notifyQState.o
CC [M] /tmp/modconfig-pVUBEq/vsock-only/linux/util.o
CC [M] /tmp/modconfig-pVUBEq/vsock-only/linux/stats.o
CC [M] /tmp/modconfig-pVUBEq/vsock-only/linux/notify.o
CC [M] /tmp/modconfig-pVUBEq/vsock-only/driverLog.o
LD [M] /tmp/modconfig-pVUBEq/vsock-only/vsock.o
Building modules, stage 2.
MODPOST 1 modules
CC /tmp/modconfig-pVUBEq/vsock-only/vsock.mod.o
LD [M] /tmp/modconfig-pVUBEq/vsock-only/vsock.ko
make[1]: Leaving directory '/usr/src/linux-3.12.6-1-ARCH'
/bin/make -C $PWD SRCROOT=$PWD/. \
MODULEBUILDDIR= postbuild
make[1]: Entering directory '/tmp/modconfig-pVUBEq/vsock-only'
make[1]: 'postbuild' is up to date.
make[1]: Leaving directory '/tmp/modconfig-pVUBEq/vsock-only'
cp -f vsock.ko ./../vsock.o
make: Leaving directory '/tmp/modconfig-pVUBEq/vsock-only'
The module vmxnet3 from this package is not supported for kernels >= 3.10.
Please enable this module in your kernel. You may also have to enable
HYPERVISOR_GUEST.
The module pvscsi from this package is not supported for kernels >= 3.10.
Please enable this module in your kernel. You may also have to enable
HYPERVISOR_GUEST.
The module vmmemctl from this package is not supported for kernels >= 3.10.
Please enable this module in your kernel. You may also have to enable
HYPERVISOR_GUEST.
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]
make: Entering directory '/tmp/modconfig-ukgHfB/vmci-only'
Using 2.6.x kernel build system.
/bin/make -C /lib/modules/3.12.6-1-ARCH/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. \
MODULEBUILDDIR= modules
make[1]: Entering directory '/usr/src/linux-3.12.6-1-ARCH'
CC [M] /tmp/modconfig-ukgHfB/vmci-only/linux/driver.o
CC [M] /tmp/modconfig-ukgHfB/vmci-only/linux/vmciKernelIf.o
CC [M] /tmp/modconfig-ukgHfB/vmci-only/common/vmciDriver.o
CC [M] /tmp/modconfig-ukgHfB/vmci-only/common/vmciResource.o
CC [M] /tmp/modconfig-ukgHfB/vmci-only/common/vmciContext.o
CC [M] /tmp/modconfig-ukgHfB/vmci-only/common/vmciDatagram.o
CC [M] /tmp/modconfig-ukgHfB/vmci-only/common/vmciHashtable.o
CC [M] /tmp/modconfig-ukgHfB/vmci-only/common/vmciEvent.o
CC [M] /tmp/modconfig-ukgHfB/vmci-only/common/vmciQueuePair.o
CC [M] /tmp/modconfig-ukgHfB/vmci-only/common/vmciDoorbell.o
CC [M] /tmp/modconfig-ukgHfB/vmci-only/common/vmciQPair.o
CC [M] /tmp/modconfig-ukgHfB/vmci-only/common/vmciRoute.o
CC [M] /tmp/modconfig-ukgHfB/vmci-only/driverLog.o
LD [M] /tmp/modconfig-ukgHfB/vmci-only/vmci.o
Building modules, stage 2.
MODPOST 1 modules
CC /tmp/modconfig-ukgHfB/vmci-only/vmci.mod.o
LD [M] /tmp/modconfig-ukgHfB/vmci-only/vmci.ko
make[1]: Leaving directory '/usr/src/linux-3.12.6-1-ARCH'
/bin/make -C $PWD SRCROOT=$PWD/. \
MODULEBUILDDIR= postbuild
make[1]: Entering directory '/tmp/modconfig-ukgHfB/vmci-only'
make[1]: 'postbuild' is up to date.
make[1]: Leaving directory '/tmp/modconfig-ukgHfB/vmci-only'
cp -f vmci.ko ./../vmci.o
make: Leaving directory '/tmp/modconfig-ukgHfB/vmci-only'
make: Entering directory '/tmp/modconfig-ukgHfB/vmhgfs-only'
Using 2.6.x kernel build system.
/bin/make -C /lib/modules/3.12.6-1-ARCH/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. \
MODULEBUILDDIR= modules
make[1]: Entering directory '/usr/src/linux-3.12.6-1-ARCH'
CC [M] /tmp/modconfig-ukgHfB/vmhgfs-only/backdoorGcc64.o
CC [M] /tmp/modconfig-ukgHfB/vmhgfs-only/message.o
CC [M] /tmp/modconfig-ukgHfB/vmhgfs-only/request.o
CC [M] /tmp/modconfig-ukgHfB/vmhgfs-only/filesystem.o
CC [M] /tmp/modconfig-ukgHfB/vmhgfs-only/cpName.o
CC [M] /tmp/modconfig-ukgHfB/vmhgfs-only/dentry.o
CC [M] /tmp/modconfig-ukgHfB/vmhgfs-only/rpcout.o
CC [M] /tmp/modconfig-ukgHfB/vmhgfs-only/hgfsUtil.o
CC [M] /tmp/modconfig-ukgHfB/vmhgfs-only/stubs.o
CC [M] /tmp/modconfig-ukgHfB/vmhgfs-only/hgfsEscape.o
CC [M] /tmp/modconfig-ukgHfB/vmhgfs-only/link.o
CC [M] /tmp/modconfig-ukgHfB/vmhgfs-only/transport.o
CC [M] /tmp/modconfig-ukgHfB/vmhgfs-only/module.o
CC [M] /tmp/modconfig-ukgHfB/vmhgfs-only/file.o
CC [M] /tmp/modconfig-ukgHfB/vmhgfs-only/super.o
CC [M] /tmp/modconfig-ukgHfB/vmhgfs-only/vmci.o
CC [M] /tmp/modconfig-ukgHfB/vmhgfs-only/bdhandler.o
CC [M] /tmp/modconfig-ukgHfB/vmhgfs-only/dir.o
CC [M] /tmp/modconfig-ukgHfB/vmhgfs-only/fsutil.o
CC [M] /tmp/modconfig-ukgHfB/vmhgfs-only/cpNameLinux.o
CC [M] /tmp/modconfig-ukgHfB/vmhgfs-only/hgfsBd.o
CC [M] /tmp/modconfig-ukgHfB/vmhgfs-only/page.o
CC [M] /tmp/modconfig-ukgHfB/vmhgfs-only/backdoor.o
CC [M] /tmp/modconfig-ukgHfB/vmhgfs-only/inode.o
CC [M] /tmp/modconfig-ukgHfB/vmhgfs-only/cpNameLite.o
CC [M] /tmp/modconfig-ukgHfB/vmhgfs-only/kernelStubsLinux.o
LD [M] /tmp/modconfig-ukgHfB/vmhgfs-only/vmhgfs.o
Building modules, stage 2.
MODPOST 1 modules
CC /tmp/modconfig-ukgHfB/vmhgfs-only/vmhgfs.mod.o
LD [M] /tmp/modconfig-ukgHfB/vmhgfs-only/vmhgfs.ko
make[1]: Leaving directory '/usr/src/linux-3.12.6-1-ARCH'
/bin/make -C $PWD SRCROOT=$PWD/. \
MODULEBUILDDIR= postbuild
make[1]: Entering directory '/tmp/modconfig-ukgHfB/vmhgfs-only'
make[1]: 'postbuild' is up to date.
make[1]: Leaving directory '/tmp/modconfig-ukgHfB/vmhgfs-only'
cp -f vmhgfs.ko ./../vmhgfs.o
make: Leaving directory '/tmp/modconfig-ukgHfB/vmhgfs-only'
The vmxnet driver is no longer supported on kernels 3.3 and greater. Please
upgrade to a newer virtual NIC. (e.g., vmxnet3 or e1000e)
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]
NOTICE: It appears your system does not have the required fuse packages
installed. The VMware blocking filesystem requires the fuse packages and its
libraries to function properly. Please install the fuse or fuse-utils package
using your systems package management utility and re-run this script in order
to enable the VMware blocking filesystem.
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 server version 1.14.5
Distribution provided drivers for Xorg X server are used.
Skipping X configuration because X drivers are not included.
Warning: This script could not find mkinitrd or update-initramfs and cannot
remake the initrd file!
Checking acpi hot plug done
Starting VMware Tools services in the virtual machine:
Switching to guest configuration: done
VM communication interface: done
VM communication interface socket family: failed
Guest filesystem driver: failed
Mounting HGFS shares: failed
Guest operating system daemon: done
Unable to start services for VMware Tools
Execution aborted.
#[root@localhost] - [14-01-02 2:46:53] - [/home/toxicarrow/vmware/vmware-tools-patches] - [R:0]
Any idea what I should be doing?

I have the same problem on ESXI 5.5 for over a month now, tried the patches, tried the LTS kernel which others say results in an immediate result without patches, nothing seems to work and nobody seems to be able to offer a solution.
Did you make any progress ??
Error! Build of vmblock.ko failed for: 3.10.25-1-lts (x86_64)
Consult the make.log in the build directory
/var/lib/dkms/open-vm-tools/2013.09.16/build/ for more information.
make[2]: *** No rule to make target '/var/lib/dkms/open-vm-tools/2013.09.16/build/vmblock/linux/inode', needed by '/var/lib/dkms/open-vm-tools/2013.09.16/build/vmblock/vmblock.o'. Stop.
Makefile:1224: recipe for target '_module_/var/lib/dkms/open-vm-tools/2013.09.16/build/vmblock' failed
make[1]: *** [_module_/var/lib/dkms/open-vm-tools/2013.09.16/build/vmblock] Error 2
make[1]: Leaving directory '/usr/src/linux-3.10.25-1-lts'
Makefile:120: recipe for target 'vmblock.ko' failed
Last edited by crankshaft (2014-01-10 11:32:32)

VMWare doesn't start after kernel update

Hello,
I've just updated my kernel to 3.10.0-997-generic. After that VMWare Player doesn't start anymore.
I've tried to run patches and different solutions I found in google, but it didn't worked yet.
This is the log of my last attempt.
Thanks in advance
2013-06-14T21:42:29.306-03:00| vthread-3| I120: Log for VMware Workstation pid=14806 version=9.0.2 build=build-1031769 option=Release
2013-06-14T21:42:29.306-03:00| vthread-3| I120: The process is 64-bit.
2013-06-14T21:42:29.306-03:00| vthread-3| I120: Host codepage=UTF-8 encoding=UTF-8
2013-06-14T21:42:29.306-03:00| vthread-3| I120: Host is Linux 3.10.0-997-generic Ubuntu 12.10
2013-06-14T21:42:29.306-03:00| vthread-3| I120: Msg_Reset:
2013-06-14T21:42:29.306-03:00| vthread-3| I120: [msg.dictionary.load.openFailed] Cannot open file "/usr/lib/vmware/settings": No such file or directory.
2013-06-14T21:42:29.306-03:00| vthread-3| I120: ----------------------------------------
2013-06-14T21:42:29.306-03:00| vthread-3| I120: PREF Optional preferences file not found at /usr/lib/vmware/settings. Using default values.
2013-06-14T21:42:29.306-03:00| vthread-3| I120: Msg_Reset:
2013-06-14T21:42:29.306-03:00| vthread-3| I120: [msg.dictionary.load.openFailed] Cannot open file "/root/.vmware/config": No such file or directory.
2013-06-14T21:42:29.306-03:00| vthread-3| I120: ----------------------------------------
2013-06-14T21:42:29.306-03:00| vthread-3| I120: PREF Optional preferences file not found at /root/.vmware/config. Using default values.
2013-06-14T21:42:29.306-03:00| vthread-3| I120: Msg_Reset:
2013-06-14T21:42:29.306-03:00| vthread-3| I120: [msg.dictionary.load.openFailed] Cannot open file "/root/.vmware/preferences": No such file or directory.
2013-06-14T21:42:29.306-03:00| vthread-3| I120: ----------------------------------------
2013-06-14T21:42:29.306-03:00| vthread-3| I120: PREF Failed to load user preferences.
2013-06-14T21:42:29.306-03:00| vthread-3| W110: Logging to /tmp/vmware-root/vmware-modconfig-14806.log
2013-06-14T21:42:29.318-03:00| vthread-3| I120: Reading in info for the vmmon module.
2013-06-14T21:42:29.318-03:00| vthread-3| I120: Reading in info for the vmnet module.
2013-06-14T21:42:29.318-03:00| vthread-3| I120: Reading in info for the vmblock module.
2013-06-14T21:42:29.318-03:00| vthread-3| I120: Reading in info for the vmci module.
2013-06-14T21:42:29.318-03:00| vthread-3| I120: Reading in info for the vsock module.
2013-06-14T21:42:29.318-03:00| vthread-3| I120: Setting vsock to depend on vmci.
2013-06-14T21:42:29.318-03:00| vthread-3| I120: Created new pathsHash.
2013-06-14T21:42:29.318-03:00| vthread-3| I120: Invoking modinfo on "vmmon".
2013-06-14T21:42:29.320-03:00| vthread-3| I120: "/sbin/modinfo" exited with status 0.
2013-06-14T21:42:29.320-03:00| vthread-3| I120: Invoking modinfo on "vmnet".
2013-06-14T21:42:29.322-03:00| vthread-3| I120: "/sbin/modinfo" exited with status 256.
2013-06-14T21:42:29.322-03:00| vthread-3| I120: Invoking modinfo on "vmblock".
2013-06-14T21:42:29.324-03:00| vthread-3| I120: "/sbin/modinfo" exited with status 256.
2013-06-14T21:42:29.324-03:00| vthread-3| I120: Invoking modinfo on "vmci".
2013-06-14T21:42:29.326-03:00| vthread-3| I120: "/sbin/modinfo" exited with status 256.
2013-06-14T21:42:29.326-03:00| vthread-3| I120: Invoking modinfo on "vsock".
2013-06-14T21:42:29.328-03:00| vthread-3| I120: "/sbin/modinfo" exited with status 0.
2013-06-14T21:42:29.345-03:00| vthread-3| I120: Obtaining info using the running kernel.
2013-06-14T21:42:29.345-03:00| vthread-3| I120: Setting header path for 3.10.0-997-generic to "/lib/modules/3.10.0-997-generic/build/include".
2013-06-14T21:42:29.345-03:00| vthread-3| I120: Validating path "/lib/modules/3.10.0-997-generic/build/include" for kernel release "3.10.0-997-generic".
2013-06-14T21:42:29.351-03:00| vthread-3| I120: Preprocessed UTS_RELEASE, got value "3.10.0-997-generic".
2013-06-14T21:42:29.351-03:00| vthread-3| I120: The header path "/lib/modules/3.10.0-997-generic/build/include" for the kernel "3.10.0-997-generic" is valid. Whoohoo!
2013-06-14T21:42:29.517-03:00| vthread-3| I120: Kernel header path retrieved from FileEntry: /lib/modules/3.10.0-997-generic/build/include
2013-06-14T21:42:29.517-03:00| vthread-3| I120: Update kernel header path to /lib/modules/3.10.0-997-generic/build/include
2013-06-14T21:42:29.517-03:00| vthread-3| I120: Validating path "/lib/modules/3.10.0-997-generic/build/include" for kernel release "3.10.0-997-generic".
2013-06-14T21:42:29.523-03:00| vthread-3| I120: Preprocessed UTS_RELEASE, got value "3.10.0-997-generic".
2013-06-14T21:42:29.523-03:00| vthread-3| I120: The header path "/lib/modules/3.10.0-997-generic/build/include" for the kernel "3.10.0-997-generic" is valid. Whoohoo!
2013-06-14T21:42:29.524-03:00| vthread-3| I120: Found compiler at "/usr/bin/gcc"
2013-06-14T21:42:29.526-03:00| vthread-3| I120: Got gcc version "4.7".
2013-06-14T21:42:29.526-03:00| vthread-3| I120: GCC minor version 4 does not match Kernel GCC minor version 4. But that is ok.
2013-06-14T21:42:29.526-03:00| vthread-3| I120: Using user supplied compiler "/usr/bin/gcc".
2013-06-14T21:42:29.528-03:00| vthread-3| I120: Got gcc version "4.7".
2013-06-14T21:42:29.528-03:00| vthread-3| I120: GCC minor version 4 does not match Kernel GCC minor version 4. But that is ok.
2013-06-14T21:42:29.532-03:00| vthread-3| I120: Trying to find a suitable PBM set for kernel "3.10.0-997-generic".
2013-06-14T21:42:29.532-03:00| vthread-3| I120: No matching PBM set was found for kernel "3.10.0-997-generic".
2013-06-14T21:42:29.532-03:00| vthread-3| I120: Validating path "/lib/modules/3.10.0-997-generic/build/include" for kernel release "3.10.0-997-generic".
2013-06-14T21:42:29.538-03:00| vthread-3| I120: Preprocessed UTS_RELEASE, got value "3.10.0-997-generic".
2013-06-14T21:42:29.538-03:00| vthread-3| I120: The header path "/lib/modules/3.10.0-997-generic/build/include" for the kernel "3.10.0-997-generic" is valid. Whoohoo!
2013-06-14T21:42:29.538-03:00| vthread-3| I120: GCC minor version 4 does not match Kernel GCC minor version 4. But that is ok.
2013-06-14T21:42:29.539-03:00| vthread-3| I120: Validating path "/lib/modules/3.10.0-997-generic/build/include" for kernel release "3.10.0-997-generic".
2013-06-14T21:42:29.545-03:00| vthread-3| I120: Preprocessed UTS_RELEASE, got value "3.10.0-997-generic".
2013-06-14T21:42:29.545-03:00| vthread-3| I120: The header path "/lib/modules/3.10.0-997-generic/build/include" for the kernel "3.10.0-997-generic" is valid. Whoohoo!
2013-06-14T21:42:29.545-03:00| vthread-3| I120: GCC minor version 4 does not match Kernel GCC minor version 4. But that is ok.
2013-06-14T21:42:29.545-03:00| vthread-3| I120: Using temp dir "/tmp".
2013-06-14T21:42:29.547-03:00| vthread-3| I120: Invoking modinfo on "vmnet".
2013-06-14T21:42:29.548-03:00| vthread-3| I120: "/sbin/modinfo" exited with status 256.
2013-06-14T21:42:29.548-03:00| vthread-3| I120: Invoking modinfo on "vmblock".
2013-06-14T21:42:29.550-03:00| vthread-3| I120: "/sbin/modinfo" exited with status 256.
2013-06-14T21:42:29.550-03:00| vthread-3| I120: Invoking modinfo on "vmci".
2013-06-14T21:42:29.552-03:00| vthread-3| I120: "/sbin/modinfo" exited with status 256.
2013-06-14T21:42:30.327-03:00| vthread-3| I120: Setting destination path for vmnet to "/lib/modules/3.10.0-997-generic/misc/vmnet.ko".
2013-06-14T21:42:30.327-03:00| vthread-3| I120: Extracting the vmnet source from "/usr/lib/vmware/modules/source/vmnet.tar".
2013-06-14T21:42:30.332-03:00| vthread-3| I120: Successfully extracted the vmnet source.
2013-06-14T21:42:30.332-03:00| vthread-3| I120: Building module with command "/usr/bin/make -j8 -C /tmp/modconfig-YkpUyf/vmnet-only auto-build HEADER_DIR=/lib/modules/3.10.0-997-generic/build/include CC=/usr/bin/gcc IS_GCC_3=no"
2013-06-14T21:42:31.977-03:00| vthread-3| W110: Failed to build vmnet. Failed to execute the build command.
2013-06-14T21:42:31.979-03:00| vthread-3| I120: Setting destination path for vmblock to "/lib/modules/3.10.0-997-generic/misc/vmblock.ko".
2013-06-14T21:42:31.979-03:00| vthread-3| I120: Extracting the vmblock source from "/usr/lib/vmware/modules/source/vmblock.tar".
2013-06-14T21:42:31.990-03:00| vthread-3| I120: Successfully extracted the vmblock source.
2013-06-14T21:42:31.990-03:00| vthread-3| I120: Building module with command "/usr/bin/make -j8 -C /tmp/modconfig-YkpUyf/vmblock-only auto-build HEADER_DIR=/lib/modules/3.10.0-997-generic/build/include CC=/usr/bin/gcc IS_GCC_3=no"
2013-06-14T21:42:33.429-03:00| vthread-3| W110: Failed to build vmblock. Failed to execute the build command.
2013-06-14T21:42:33.431-03:00| vthread-3| I120: Setting destination path for vmci to "/lib/modules/3.10.0-997-generic/misc/vmci.ko".
2013-06-14T21:42:33.431-03:00| vthread-3| I120: Extracting the vmci source from "/usr/lib/vmware/modules/source/vmci.tar".
2013-06-14T21:42:33.445-03:00| vthread-3| I120: Successfully extracted the vmci source.
2013-06-14T21:42:33.446-03:00| vthread-3| I120: Building module with command "/usr/bin/make -j8 -C /tmp/modconfig-YkpUyf/vmci-only auto-build HEADER_DIR=/lib/modules/3.10.0-997-generic/build/include CC=/usr/bin/gcc IS_GCC_3=no"
2013-06-14T21:42:35.773-03:00| vthread-3| I120: Successfully built vmci. Module is currently at "/tmp/modconfig-YkpUyf/vmci.o".
2013-06-14T21:42:35.773-03:00| vthread-3| I120: Found the vmci symvers file at "/tmp/modconfig-YkpUyf/vmci-only/Module.symvers".
2013-06-14T21:42:35.774-03:00| vthread-3| I120: Installing vmci from /tmp/modconfig-YkpUyf/vmci.o to /lib/modules/3.10.0-997-generic/misc/vmci.ko.
2013-06-14T21:42:35.774-03:00| vthread-3| I120: Registering file "/lib/modules/3.10.0-997-generic/misc/vmci.ko".
2013-06-14T21:42:36.234-03:00| vthread-3| I120: "/usr/lib/vmware-installer/2.1.0/vmware-installer" exited with status 0.
2013-06-14T21:42:36.234-03:00| vthread-3| I120: Registering file "/usr/lib/vmware/symvers/vmci-3.10.0-997-generic".
2013-06-14T21:42:36.686-03:00| vthread-3| I120: "/usr/lib/vmware-installer/2.1.0/vmware-installer" exited with status 0.

Before
create file "/usr/lib/vmware/settings"
after
create file "/root/.vmware/config"
after
create file "/root/.vmware/preferences"
And after
Install the build-essential package:
sudo apt-get install build-essential
VMware Workstation 11.1.0 and Player (Pro) 7.1.0 support kernels up to 3.18. You can apply a patch:
curl http://pastie.org/pastes/9934018/download -o /tmp/vmnet-3.19.patch
cd /usr/lib/vmware/modules/source
tar -xf vmnet.tar
patch -p0 -i /tmp/vmnet-3.19.patch
tar -cf vmnet.tar vmnet-only
rm -r *-only
vmware-modconfig --console --install-all
I tried, worked

VMware Fusion 4 guest

Hello,
I've installed Arch in a VM running on VMware Fusion 4. Out of the box it doesn't fit the resolution to the window so if I go fullscreen it gets ugly. When I try to install vmware-tools I get an error:
[Fleet@mba vmware-tools-distrib]$ sudo ./vmware-install.pl
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/vmware.d
What is the directory that contains the init scripts?
[/etc/rc.d/vmware.d] /etc/rc.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 8.8.0 build-465068 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...
Use of uninitialized value $subLevel in split at /usr/bin/vmware-config-tools.pl line 5324.
Use of uninitialized value $subLevel in concatenation (.) or string at /usr/bin/vmware-config-tools.pl line 5325.
Argument "0-ARCH" isn't numeric in multiplication (*) at /usr/bin/vmware-config-tools.pl line 4859.
Use of uninitialized value $subLevel in addition (+) at /usr/bin/vmware-config-tools.pl line 4859.
Making sure services for VMware Tools are stopped.
Stopping VMware Tools services in the virtual machine:
Guest operating system daemon: done
Virtual Printing daemon: done
Unmounting HGFS shares: done
Guest filesystem driver: done
/etc/rc.d/vmware-tools: line 1114: [: BASH=/bin/sh: integer expression expected
/etc/rc.d/vmware-tools: line 1114: [: BASH=/bin/sh: integer expression expected
/etc/rc.d/vmware-tools: line 1199: [: BASH=/bin/sh: integer expression expected
[EXPERIMENTAL] The VMware FileSystem Sync Driver (vmsync) is a new feature that
creates backups of virtual machines. Please refer to the VMware Knowledge Base
for more details on this capability. 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/3.0-ARCH/build/include".
The path "/lib/modules/3.0-ARCH/build/include" appears to be a valid path to
the 3.0-ARCH kernel headers.
Would you like to change it? [no]
Using 2.6.x kernel build system.
make: Entering directory `/tmp/vmware-root/modules/vmci-only'
make -C /lib/modules/3.0-ARCH/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. \
MODULEBUILDDIR= modules
make[1]: Entering directory `/usr/src/linux-3.0-ARCH'
CC [M] /tmp/vmware-root/modules/vmci-only/linux/driver.o
CC [M] /tmp/vmware-root/modules/vmci-only/common/vmciDatagram.o
CC [M] /tmp/vmware-root/modules/vmci-only/linux/vmciKernelIf.o
CC [M] /tmp/vmware-root/modules/vmci-only/common/vmciDriver.o
CC [M] /tmp/vmware-root/modules/vmci-only/common/vmciRoute.o
CC [M] /tmp/vmware-root/modules/vmci-only/common/vmciResource.o
CC [M] /tmp/vmware-root/modules/vmci-only/common/vmciHashtable.o
CC [M] /tmp/vmware-root/modules/vmci-only/common/vmciEvent.o
CC [M] /tmp/vmware-root/modules/vmci-only/common/vmciContext.o
CC [M] /tmp/vmware-root/modules/vmci-only/driverLog.o
CC [M] /tmp/vmware-root/modules/vmci-only/common/vmciQueuePair.o
CC [M] /tmp/vmware-root/modules/vmci-only/common/vmciQPair.o
CC [M] /tmp/vmware-root/modules/vmci-only/common/vmciDoorbell.o
LD [M] /tmp/vmware-root/modules/vmci-only/vmci.o
Building modules, stage 2.
MODPOST 1 modules
CC /tmp/vmware-root/modules/vmci-only/vmci.mod.o
LD [M] /tmp/vmware-root/modules/vmci-only/vmci.ko
make[1]: Leaving directory `/usr/src/linux-3.0-ARCH'
make -C $PWD SRCROOT=$PWD/. \
MODULEBUILDDIR= postbuild
make[1]: Entering directory `/tmp/vmware-root/modules/vmci-only'
make[1]: `postbuild' is up to date.
make[1]: Leaving directory `/tmp/vmware-root/modules/vmci-only'
cp -f vmci.ko ./../vmci.o
make: Leaving directory `/tmp/vmware-root/modules/vmci-only'
Using 2.6.x kernel build system.
make: Entering directory `/tmp/vmware-root/modules/vmci-only'
make -C /lib/modules/3.0-ARCH/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. \
MODULEBUILDDIR= modules
make[1]: Entering directory `/usr/src/linux-3.0-ARCH'
CC [M] /tmp/vmware-root/modules/vmci-only/linux/driver.o
CC [M] /tmp/vmware-root/modules/vmci-only/linux/vmciKernelIf.o
CC [M] /tmp/vmware-root/modules/vmci-only/common/vmciDatagram.o
CC [M] /tmp/vmware-root/modules/vmci-only/common/vmciDriver.o
CC [M] /tmp/vmware-root/modules/vmci-only/common/vmciRoute.o
CC [M] /tmp/vmware-root/modules/vmci-only/common/vmciResource.o
CC [M] /tmp/vmware-root/modules/vmci-only/common/vmciContext.o
CC [M] /tmp/vmware-root/modules/vmci-only/common/vmciHashtable.o
CC [M] /tmp/vmware-root/modules/vmci-only/common/vmciEvent.o
CC [M] /tmp/vmware-root/modules/vmci-only/common/vmciQPair.o
CC [M] /tmp/vmware-root/modules/vmci-only/common/vmciQueuePair.o
CC [M] /tmp/vmware-root/modules/vmci-only/common/vmciDoorbell.o
CC [M] /tmp/vmware-root/modules/vmci-only/driverLog.o
LD [M] /tmp/vmware-root/modules/vmci-only/vmci.o
Building modules, stage 2.
MODPOST 1 modules
CC /tmp/vmware-root/modules/vmci-only/vmci.mod.o
LD [M] /tmp/vmware-root/modules/vmci-only/vmci.ko
make[1]: Leaving directory `/usr/src/linux-3.0-ARCH'
make -C $PWD SRCROOT=$PWD/. \
MODULEBUILDDIR= postbuild
make[1]: Entering directory `/tmp/vmware-root/modules/vmci-only'
make[1]: `postbuild' is up to date.
make[1]: Leaving directory `/tmp/vmware-root/modules/vmci-only'
cp -f vmci.ko ./../vmci.o
make: Leaving directory `/tmp/vmware-root/modules/vmci-only'
Using 2.6.x kernel build system.
make: Entering directory `/tmp/vmware-root/modules/vsock-only'
make -C /lib/modules/3.0-ARCH/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. \
MODULEBUILDDIR= modules
make[1]: Entering directory `/usr/src/linux-3.0-ARCH'
CC [M] /tmp/vmware-root/modules/vsock-only/linux/af_vsock.o
CC [M] /tmp/vmware-root/modules/vsock-only/linux/vsockAddr.o
CC [M] /tmp/vmware-root/modules/vsock-only/linux/util.o
CC [M] /tmp/vmware-root/modules/vsock-only/linux/notifyQState.o
CC [M] /tmp/vmware-root/modules/vsock-only/driverLog.o
CC [M] /tmp/vmware-root/modules/vsock-only/linux/stats.o
CC [M] /tmp/vmware-root/modules/vsock-only/linux/notify.o
LD [M] /tmp/vmware-root/modules/vsock-only/vsock.o
Building modules, stage 2.
MODPOST 1 modules
CC /tmp/vmware-root/modules/vsock-only/vsock.mod.o
LD [M] /tmp/vmware-root/modules/vsock-only/vsock.ko
make[1]: Leaving directory `/usr/src/linux-3.0-ARCH'
make -C $PWD SRCROOT=$PWD/. \
MODULEBUILDDIR= postbuild
make[1]: Entering directory `/tmp/vmware-root/modules/vsock-only'
make[1]: `postbuild' is up to date.
make[1]: Leaving directory `/tmp/vmware-root/modules/vsock-only'
cp -f vsock.ko ./../vsock.o
make: Leaving directory `/tmp/vmware-root/modules/vsock-only'
Using 2.6.x kernel build system.
make: Entering directory `/tmp/vmware-root/modules/vmxnet3-only'
make -C /lib/modules/3.0-ARCH/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. \
MODULEBUILDDIR= modules
make[1]: Entering directory `/usr/src/linux-3.0-ARCH'
CC [M] /tmp/vmware-root/modules/vmxnet3-only/vmxnet3_shm.o
CC [M] /tmp/vmware-root/modules/vmxnet3-only/vmxnet3_ethtool.o
CC [M] /tmp/vmware-root/modules/vmxnet3-only/vmxnet3_drv.o
LD [M] /tmp/vmware-root/modules/vmxnet3-only/vmxnet3.o
Building modules, stage 2.
MODPOST 1 modules
CC /tmp/vmware-root/modules/vmxnet3-only/vmxnet3.mod.o
LD [M] /tmp/vmware-root/modules/vmxnet3-only/vmxnet3.ko
make[1]: Leaving directory `/usr/src/linux-3.0-ARCH'
make -C $PWD SRCROOT=$PWD/. \
MODULEBUILDDIR= postbuild
make[1]: Entering directory `/tmp/vmware-root/modules/vmxnet3-only'
make[1]: `postbuild' is up to date.
make[1]: Leaving directory `/tmp/vmware-root/modules/vmxnet3-only'
cp -f vmxnet3.ko ./../vmxnet3.o
make: Leaving directory `/tmp/vmware-root/modules/vmxnet3-only'
Using 2.6.x kernel build system.
make: Entering directory `/tmp/vmware-root/modules/pvscsi-only'
make -C /lib/modules/3.0-ARCH/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. \
MODULEBUILDDIR= modules
make[1]: Entering directory `/usr/src/linux-3.0-ARCH'
CC [M] /tmp/vmware-root/modules/pvscsi-only/pvscsi.o
Building modules, stage 2.
MODPOST 1 modules
CC /tmp/vmware-root/modules/pvscsi-only/pvscsi.mod.o
LD [M] /tmp/vmware-root/modules/pvscsi-only/pvscsi.ko
make[1]: Leaving directory `/usr/src/linux-3.0-ARCH'
make -C $PWD SRCROOT=$PWD/. \
MODULEBUILDDIR= postbuild
make[1]: Entering directory `/tmp/vmware-root/modules/pvscsi-only'
make[1]: `postbuild' is up to date.
make[1]: Leaving directory `/tmp/vmware-root/modules/pvscsi-only'
cp -f pvscsi.ko ./../pvscsi.o
make: Leaving directory `/tmp/vmware-root/modules/pvscsi-only'
Using 2.6.x kernel build system.
make: Entering directory `/tmp/vmware-root/modules/vmmemctl-only'
make -C /lib/modules/3.0-ARCH/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. \
MODULEBUILDDIR= modules
make[1]: Entering directory `/usr/src/linux-3.0-ARCH'
CC [M] /tmp/vmware-root/modules/vmmemctl-only/backdoorGcc64.o
CC [M] /tmp/vmware-root/modules/vmmemctl-only/os.o
CC [M] /tmp/vmware-root/modules/vmmemctl-only/vmballoon.o
LD [M] /tmp/vmware-root/modules/vmmemctl-only/vmmemctl.o
Building modules, stage 2.
MODPOST 1 modules
CC /tmp/vmware-root/modules/vmmemctl-only/vmmemctl.mod.o
LD [M] /tmp/vmware-root/modules/vmmemctl-only/vmmemctl.ko
make[1]: Leaving directory `/usr/src/linux-3.0-ARCH'
make -C $PWD SRCROOT=$PWD/. \
MODULEBUILDDIR= postbuild
make[1]: Entering directory `/tmp/vmware-root/modules/vmmemctl-only'
make[1]: `postbuild' is up to date.
make[1]: Leaving directory `/tmp/vmware-root/modules/vmmemctl-only'
cp -f vmmemctl.ko ./../vmmemctl.o
make: Leaving directory `/tmp/vmware-root/modules/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? [yes]
Using 2.6.x kernel build system.
make: Entering directory `/tmp/vmware-root/modules/vmci-only'
make -C /lib/modules/3.0-ARCH/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. \
MODULEBUILDDIR= modules
make[1]: Entering directory `/usr/src/linux-3.0-ARCH'
CC [M] /tmp/vmware-root/modules/vmci-only/linux/driver.o
CC [M] /tmp/vmware-root/modules/vmci-only/common/vmciDatagram.o
CC [M] /tmp/vmware-root/modules/vmci-only/linux/vmciKernelIf.o
CC [M] /tmp/vmware-root/modules/vmci-only/common/vmciContext.o
CC [M] /tmp/vmware-root/modules/vmci-only/common/vmciDriver.o
CC [M] /tmp/vmware-root/modules/vmci-only/common/vmciDoorbell.o
CC [M] /tmp/vmware-root/modules/vmci-only/common/vmciHashtable.o
CC [M] /tmp/vmware-root/modules/vmci-only/common/vmciResource.o
CC [M] /tmp/vmware-root/modules/vmci-only/common/vmciRoute.o
CC [M] /tmp/vmware-root/modules/vmci-only/common/vmciQueuePair.o
CC [M] /tmp/vmware-root/modules/vmci-only/common/vmciEvent.o
CC [M] /tmp/vmware-root/modules/vmci-only/driverLog.o
CC [M] /tmp/vmware-root/modules/vmci-only/common/vmciQPair.o
LD [M] /tmp/vmware-root/modules/vmci-only/vmci.o
Building modules, stage 2.
MODPOST 1 modules
CC /tmp/vmware-root/modules/vmci-only/vmci.mod.o
LD [M] /tmp/vmware-root/modules/vmci-only/vmci.ko
make[1]: Leaving directory `/usr/src/linux-3.0-ARCH'
make -C $PWD SRCROOT=$PWD/. \
MODULEBUILDDIR= postbuild
make[1]: Entering directory `/tmp/vmware-root/modules/vmci-only'
make[1]: `postbuild' is up to date.
make[1]: Leaving directory `/tmp/vmware-root/modules/vmci-only'
cp -f vmci.ko ./../vmci.o
make: Leaving directory `/tmp/vmware-root/modules/vmci-only'
Using 2.6.x kernel build system.
make: Entering directory `/tmp/vmware-root/modules/vmhgfs-only'
make -C /lib/modules/3.0-ARCH/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. \
MODULEBUILDDIR= modules
make[1]: Entering directory `/usr/src/linux-3.0-ARCH'
CC [M] /tmp/vmware-root/modules/vmhgfs-only/message.o
CC [M] /tmp/vmware-root/modules/vmhgfs-only/cpName.o
CC [M] /tmp/vmware-root/modules/vmhgfs-only/rpcout.o
CC [M] /tmp/vmware-root/modules/vmhgfs-only/link.o
CC [M] /tmp/vmware-root/modules/vmhgfs-only/filesystem.o
CC [M] /tmp/vmware-root/modules/vmhgfs-only/dentry.o
CC [M] /tmp/vmware-root/modules/vmhgfs-only/module.o
CC [M] /tmp/vmware-root/modules/vmhgfs-only/file.o
CC [M] /tmp/vmware-root/modules/vmhgfs-only/stubs.o
CC [M] /tmp/vmware-root/modules/vmhgfs-only/request.o
CC [M] /tmp/vmware-root/modules/vmhgfs-only/hgfsUtil.o
CC [M] /tmp/vmware-root/modules/vmhgfs-only/tcp.o
CC [M] /tmp/vmware-root/modules/vmhgfs-only/backdoor.o
CC [M] /tmp/vmware-root/modules/vmhgfs-only/vmci.o
CC [M] /tmp/vmware-root/modules/vmhgfs-only/transport.o
CC [M] /tmp/vmware-root/modules/vmhgfs-only/bdhandler.o
CC [M] /tmp/vmware-root/modules/vmhgfs-only/page.o
CC [M] /tmp/vmware-root/modules/vmhgfs-only/cpNameLinux.o
CC [M] /tmp/vmware-root/modules/vmhgfs-only/dir.o
CC [M] /tmp/vmware-root/modules/vmhgfs-only/super.o
CC [M] /tmp/vmware-root/modules/vmhgfs-only/fsutil.o
CC [M] /tmp/vmware-root/modules/vmhgfs-only/hgfsBd.o
CC [M] /tmp/vmware-root/modules/vmhgfs-only/backdoorGcc64.o
CC [M] /tmp/vmware-root/modules/vmhgfs-only/hgfsEscape.o
CC [M] /tmp/vmware-root/modules/vmhgfs-only/inode.o
CC [M] /tmp/vmware-root/modules/vmhgfs-only/cpNameLite.o
CC [M] /tmp/vmware-root/modules/vmhgfs-only/kernelStubsLinux.o
LD [M] /tmp/vmware-root/modules/vmhgfs-only/vmhgfs.o
Building modules, stage 2.
MODPOST 1 modules
CC /tmp/vmware-root/modules/vmhgfs-only/vmhgfs.mod.o
LD [M] /tmp/vmware-root/modules/vmhgfs-only/vmhgfs.ko
make[1]: Leaving directory `/usr/src/linux-3.0-ARCH'
make -C $PWD SRCROOT=$PWD/. \
MODULEBUILDDIR= postbuild
make[1]: Entering directory `/tmp/vmware-root/modules/vmhgfs-only'
make[1]: `postbuild' is up to date.
make[1]: Leaving directory `/tmp/vmware-root/modules/vmhgfs-only'
cp -f vmhgfs.ko ./../vmhgfs.o
make: Leaving directory `/tmp/vmware-root/modules/vmhgfs-only'
Using 2.6.x kernel build system.
make: Entering directory `/tmp/vmware-root/modules/vmxnet-only'
make -C /lib/modules/3.0-ARCH/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. \
MODULEBUILDDIR= modules
make[1]: Entering directory `/usr/src/linux-3.0-ARCH'
CC [M] /tmp/vmware-root/modules/vmxnet-only/vmxnet.o
Building modules, stage 2.
MODPOST 1 modules
CC /tmp/vmware-root/modules/vmxnet-only/vmxnet.mod.o
LD [M] /tmp/vmware-root/modules/vmxnet-only/vmxnet.ko
make[1]: Leaving directory `/usr/src/linux-3.0-ARCH'
make -C $PWD SRCROOT=$PWD/. \
MODULEBUILDDIR= postbuild
make[1]: Entering directory `/tmp/vmware-root/modules/vmxnet-only'
make[1]: `postbuild' is up to date.
make[1]: Leaving directory `/tmp/vmware-root/modules/vmxnet-only'
cp -f vmxnet.ko ./../vmxnet.o
make: Leaving directory `/tmp/vmware-root/modules/vmxnet-only'
Using 2.6.x kernel build system.
make: Entering directory `/tmp/vmware-root/modules/vmblock-only'
make -C /lib/modules/3.0-ARCH/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. \
MODULEBUILDDIR= modules
make[1]: Entering directory `/usr/src/linux-3.0-ARCH'
CC [M] /tmp/vmware-root/modules/vmblock-only/linux/stubs.o
CC [M] /tmp/vmware-root/modules/vmblock-only/linux/dbllnklst.o
CC [M] /tmp/vmware-root/modules/vmblock-only/linux/file.o
CC [M] /tmp/vmware-root/modules/vmblock-only/linux/block.o
CC [M] /tmp/vmware-root/modules/vmblock-only/linux/module.o
CC [M] /tmp/vmware-root/modules/vmblock-only/linux/super.o
CC [M] /tmp/vmware-root/modules/vmblock-only/linux/inode.o
CC [M] /tmp/vmware-root/modules/vmblock-only/linux/control.o
CC [M] /tmp/vmware-root/modules/vmblock-only/linux/filesystem.o
CC [M] /tmp/vmware-root/modules/vmblock-only/linux/dentry.o
LD [M] /tmp/vmware-root/modules/vmblock-only/vmblock.o
Building modules, stage 2.
MODPOST 1 modules
CC /tmp/vmware-root/modules/vmblock-only/vmblock.mod.o
LD [M] /tmp/vmware-root/modules/vmblock-only/vmblock.ko
make[1]: Leaving directory `/usr/src/linux-3.0-ARCH'
make -C $PWD SRCROOT=$PWD/. \
MODULEBUILDDIR= postbuild
make[1]: Entering directory `/tmp/vmware-root/modules/vmblock-only'
make[1]: `postbuild' is up to date.
make[1]: Leaving directory `/tmp/vmware-root/modules/vmblock-only'
cp -f vmblock.ko ./../vmblock.o
make: Leaving directory `/tmp/vmware-root/modules/vmblock-only'
!!! [EXPERIMENTAL] !!!
VMware automatic kernel modules enables automatic building and installation of
VMware kernel modules at boot they 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]
Detected X server version 1.10.4
Distribution provided drivers for Xorg X server are used.
Skipping X configuration because X drivers are not included.
Warning: This script could not find mkinitrd or update-initramfs and cannot
remake the initrd file!
Starting VMware Tools services in the virtual machine:
Switching to guest configuration: done
Paravirtual SCSI module: done
Guest memory manager: done
/etc/rc.d/vmware-tools: line 1114: [: BASH=/bin/sh: integer expression expected
VM communication interface: failed
VM communication interface socket family: failed
/etc/rc.d/vmware-tools: line 1114: [: BASH=/bin/sh: integer expression expected
Blocking file system: done
VMware User Agent: done
/etc/rc.d/vmware-tools: line 1199: [: BASH=/bin/sh: integer expression expected
Guest operating system daemon: done
Virtual Printing daemon: done
Unable to start services for VMware Tools
Execution aborted.
I can't figure out what to do different. Do you have any suggestions? I have also tried open-vm-tools but resolution auto switch and the other functionality didn't seem to work for me.
Last edited by Fleet (2011-09-25 15:48:14)

I am evaluating Virtualbox as an alternative but Arch performes sluggish in VB though it allows me to run fullscreen with native resolution (1440x900).
Last edited by Fleet (2011-10-14 19:56:06)

Oracle Linux 6 installation FAILURE on VMWare virtual machine

I just downloaded OEL 6.0 x64, created a new VMWare virtual machine (I have many VMWare VMs running various flavors of OEL 5) and did an installation. It all seemed to work fine. I was just testing, so I didn't do any customization. It finished, and looked good, just like all the other ones I've done. I clicked "reboot", and it did. Or it tried to.
It did boot from the disk, but after about 15 seconds, it said:
No root device found
Boot has failed, sleeping forever.
I retried the installation using a fresh VM, and even let the installer check the whole DVD first. Same result.
Anyone installed OEL 6 to a virtual machine on VMWare ESX?
Any idea what the heck could be wrong?

The problem is:
The Red Hat compatible kernel includes the vmw_pvscsi driver whereas Unbreakable Enterprise Kernel doesn’t. The kernel that the installer boots first does have the drivers, which is why everything is set up fine until UEK tries to find the root volume. It's an issue we plan to address in an updated kernel.
For now the workaround is:
When creating a new VM in VSphere, do not pick Red Hat Enterprise Linux 6 x86-64 as the OS type but use Oracle Linux 5 x86-64 (or Red Hat Enterprise Linux 5). ESX will then expose the LSI logic scsi controller to the OS and the 2.6.32-100.28.* kernel will work.
Sergio

Role in VMWARE Integrated Open Stack

How can I create a role and modify access level of created role in VMWARE Integrated Open Stack ??
for example I want a role to assign tenant member that member just be able to create instance or can't create network

Hi Nagaraj,
See that the mandatory SICF setting are enabled or Active in the SICF Services. Follow the steps as below:-
Enter the TCode SICF
Execute the same for Hierarchy Type SICF.
Check the following SAP Note 1295006.
If every thing is Active then, the IC Agent role will open.
Still if it is not opening Let me know.
regards,
Sarangamath

[Blog] Monitoring WebLogic J2EE on VMware with VMware vCenter Operations (vCOps)

Monitoring WebLogic J2EE on VMware with VMware vCenter Operations
The Blue Medora vC Ops Management Pack for Oracle OEM was updated in early May (2014) to include enhanced support for Oracle WebLogic J2EE integration. All of the Oracle EM target types for WebLogic related components including WebLogic Server, J2EE Application Deployments, Oracle HTTP Server, as well as WebLogic Cluster are now available to be ingested into VMware vC Ops Enterprise Edition.
With the data available within these new vC Ops 'Resource Kinds', you have the ability to create WebLogic on VMware relationship views, WebLogic on VMware mashup dashboards, as well as leverage vC Ops anomaly detection and predictive analytics on your WebLogic J2EE landscape. Below are a number of example dashboards that were easily created using the WebLogic data available within the Management Pack.
The first dashboard, the WebLogic on VMware Relationship View -- helps you visualize your WebLogic environment running on VMware all the way down to the VMware VM, ESX, and even Datastore level. This can useful for diagnosing critical J2EE applications running within the vSphere environment -- allowing you to quickly discern whether a problem exists in the Oracle WebLogic layer or one of the VMware virtualization layers.
vC Ops Management Pack for Oracle EM - WebLogic on VMware Relationship View
Continued here: Monitoring WebLogic J2EE on VMware with VMware vCenter Operations | Blue Medora

Can you point me to recommendations on installing Hyperic on VMware virtual appliances?
Is it as simple as treating the appliance as a Linux VM during installation? Can vSphere be used to deploy Hyperic to a VMware appliance like vRA (non-IAAS)?
Thanks,
-MattG

My SCVMM upgrade to UR6 after, I can't create VM and hardware profile.

My SCVMM's hardware profile is missing, once I create hardware profile in Library , system will be crash. how to fix it?

Had a similar problem a couple of days ago.
where able to create Hardware Profiles, but not delete them. and since the Create Virtual machine process in vmm creates and remove a Hardware Template, the creation failed.
when it failed to delete, i got a error log located in C:\ProgramData\VMMLogs\. take a look at it.
in my case it was a database error.
i ran "DBCC CHECKDB (VirtualManagerDB)" and it indicated that my indexes was corrupted.
I then did run "DBCC CHECKDB (VirtualManagerDB, repair_rebuild)" and it fixed the problem.
Read the log, check the database. and if its the same problem as me. run the repair_rebuild.
but remember to take a backup, just in case.

VMWare Not detecting Harddisk

Dear All,
I am new to VMWare environment.
I installed the VMWare on my local Vista OS.
Now when I am trying to create a new VMWare Virtual Machine by clicking the "Create Virtual Machines" under Virtual Machines tab, the VMWare is not detecting the Harddisk size on my PC.
Please find the attachment "VMware.jpg" & "VMware2.jpg" to view the issue I am facing.
Much Appreciate your help on this one.
Thanks,
Madhu K.

Hi Madhu,
The issue could be that ur ESX server cannot yet see the disks.
Try scannning the storage from the Configuration menu -> Storage Adapters -> Rescan

UCSM / VMware vCenter Server dependencies for vDS

I am still trying to wrap my head around the differences between the vDS created via UCSM / VMware vCenter integration and the traditional N1K.
If understand correctly, the UCSM (1.4) vDS does not require the VSM appliance that is needed with the N1K. And if that is correct, is there any dependency on vCenter? If vCenter goes down will the vDS continue to operate normally as the FIs are acting as the VSM?

Hi Peter,
Just to add to the nice post from Eric, 5+ Eric
as you might aware that with the Cisco M81KR VIC adapter
- VN-Link in hardware, all traffic to and from a virtual machine passes through the DVS and the hypervisor.
and then returns to the virtual machine on the server. Switching occurs in the fabric interconnect (hardware).
As a result, network policies can be applied to traffic between virtual machines. This capability provides
consistency between physical and virtual servers
For Cisco UCS instances that use Cisco M81KR VIC adapters to implement VN-Link in hardware, you must
create and install an extension file to establish the relationship and communications between Cisco UCS
Manager and the VMware vCenter. This extension file is an XML file that contains vital information
The distributed virtual switch (DVS) framework delivers VN-Link in hardware features and capabilities for virtual machines on Cisco UCS servers with VIC adapters
With VN-link in hardware, Layer 2 traffic between two VMs on the same host is not locally switched on the DVS but it sent upstream to the UCs-6100 for the policy application and switching. Switching occurs in the fabric interconnect (hardware). As a result, network policies can be applied to traffic between virtual machines. This capability provides consistency between physical and virtual servers.
In VMware vCenter, a port profile is represented as a port group. Cisco UCS Manager pushes the port profile names to vCenter, which displays the names as port groups. None of the specific networking properties or settings in the port profile are visible in VMware vCenter.
for more technical details see the bellow link
http://www.cisco.com/en/US/products/ps10281/products_configuration_example09186a0080b52d0d.shtml
HTH
if helpful Rate

Vista and VDA/Vmware VDI - gets stuck in the factory

Hi
I've created a VDA/VMware /vdi demo and have everything working fine with XP.
However with Vista the vm's get stuck in the factory.
I've created a custom specification in VMWare for Vista.
I have disable RDP and written the SetupComplete script to enable it again once sysprep
is finished, however it still gets stuck.
I suspect it is windows firewall stopping as this gets turned on by default - even though my template system has it turned off.
Any ideas please?
Thanks

Try disabling your firewall service.

VMWare - Hyper-V Conversion Failed: Does Not Have Write Permissions

Hey Guys -
Today I've been trying to convert a VM from VMWare Workstation to Hyper-V. I have it in VMWare Workstation and not ESX because I'm working from home currently. My Hyper-V server is also local and hosted on a new Windows Server 2012 R2 build.
When I try to convert it at the end of the process, I get the below error:
Blocking Issue(s):
1: UNC Path "\\192.168.0.10\VDisks\Nagios Log Server" is not valid or does not have write permissions
Warnings(s):
1: The number of USB devices configured on the VMWare guest machine is 1. The USB device (window cuts off here)
2: The video memory configured on the VMware guest machine is greater than 4 MB. The vid (window cuts off here)
Below is a screenshot:
Environment
- Hyper-V server is on a separate system running Windows Server 2012 R2
- VMWare Workstation is on the PC I'm running the converter on. The source VM is shared and I have Workstation configured to share on port 444 (443 is taken)
- Hyper-V Server is on domain - VMWare Workstation Computer is NOT joined to that domain - however - when choosing VM I connected with the domain credentials and browsed to select target folder - not just typed it in.
- I'm using Domain Admin credentials and the VDisks share is set to have full access to the account
- I can connect to target share via Explorer and write files / create folders successfully
- VMWare Workstation version 11 running on Windows 8.1 Update 1 x64
Any ideas or suggestions? Thanks!
Ben K.

Hi,
in my case it worked when the Server(-VM) on which we installed the MVMC AND the target-file server were joined to the domain.
We also created a domain account, which has write-permissions to the target fileshare. We used this domain account for logon on the MVMC-machine and for running the MVMC Wizard.
Hope that helps
Regards
Robert

Get VMM powershell from jobs

Hi All,
I like when VMM creates a service, a VM, or a complex operation.
We can see all these operations on the Jobs view, and we can almost see the first command like New-SCVirtualMachine
or something else.
Now, is there any way to get all the VMM powershell commands from a specific job. I'm sure the commands are stored somewhere since we can make a 'Restart Job' for example.
This will be nice since we can reuse these powershell commands to create great scripts.
Thanks
Regards, Samir Farhat Infrastructure Consultant

FWIW and not sure if this is related to your issue...
Unfortunately, the Get-SCJob SCVMM command was aliased to
Get-Job , which is a command that comes with Windows / Powershell natively..
In order to get around this awesome (sarcasm) problem, if you are trying to get to the Windows jobs, you have to reference the fully qualified command, which is:
Microsoft.PowerShell.Core\Get-Job
Otherwise, you'll always get the results from Get-SCJob whether you intended to or not.
Have an open case on this, no hotfix / fix date supplied yet.
Seth Cohen

VMM create VM to VMware

Similar Messages

Maybe you are looking for