5.1 - VMware Tools of Patch ESXi510-201212402-BG has not detected if necessary

Similar Questions

• Could not use the Clone Stamp tool as the area to clone has not been set

  Freshly installed 10 items.  Can not use the option-click to define an area for the clone stamp.  The error I get is:

  Could not use the clone stamp tool because the area to clone has not been defined (option - click to set a sampling point).

  New Mac Mini.  Had the same problems in Elements 9 so I installed the trial of 10.  Is it an error of keyboard shortcut?  Do not have this problem with Elements 9 on my Mac Air or my Windows 7 system.

  I'm not a newbie and know how to use the tool clone.  I won't say that I'm an expert, so if it's something related to diapers please throw some ideas.

  Yes, that sounds like a problem of layers.  If the area that you use to define the source of duplication is a transparent area on one of your layers, it will not work.  Released from the Palette layers, then make sure that you use the area of the image (and not the mask area) - if the area of the image on the layer is active, it will have a border.

  Ken

• Install vmware tools in Debian 7.1 comments will not work

  Hello

  can anyone help with this, I tried to installthe vmware tools in a 7.1 Debian guest and got the following error:

  "VMware Tools 8.8.2 build-590212 for FreeBSD will not install on the operating system you are using. Please make sure that you install the version of VMware Tools that is appropriate for your operating system. »

  The client has been installed with the operating system other type > FreeBSD 64-bit.

  Any suggestions?

  Concerning

  Jens

  Hi Darius,.

  It's the amd64, but Linux > Debian 7 x 64 isn't available, I chose the 5 x 64 Version, it works.

  I wonder if I should buy the 9 workstation to have the correct choice available..., I would do that.

  I forgot to mention that I use version 8 of workstation.

  Thank you!

  See you soon

  Jens

• security analysis of Microsoft has not detected spyware "ms removal tool. Why not?

  has suckered in by this spy

  Hello

  You can't count on a program to remove all malware

  It's also a malware so being written every day

  This reading below the link to the specific way to remove MS removal Tool

  http://www.bleepingcomputer.com/virus-removal/remove-Ms-removal-tool

• How to launch and use the VMware tools

  After installing 2008r2 as a virtual machine and install VMware Tools, I am unable to open the tools and use them.  I did two days of searching, and I can't find an answer to my problem.    Downstairs is an action I took, but I would appreciate any help from the community.

  Purpose:

  Laboratory at home training and certification.

  Hardware environment: (based on "Chris Wahl" home Build Lab)

  SuperMicro Motherboard MBD-X10SLH-F-O

  Intel Xeon E3-1230 v3 3.30 GHz processor with 32 GB of ram

  Software environment:

  64-bit version of Windows 7 Professional, host operating system

  VMware Workstation 10 with all updates installed with administrator privileges

  VM #2: vSphere 5.1 install

  VM #1: The Windows 2008R2 VM I have a problem with VMware tools.

  I've deleted and rebuilt the two VM three times now, thinking it was my environment somehow.  ESXi 5.1 works although I have not built anything there yet.  I am able to access this part of the laboratory fine of vSphere Client.

  VMware Tools:

  Within the Services of VM 2008 I can see VMware Tools started service, the icon in the system tray notification area and see the files on the C: drive of the virtual computer, but there is no way to open it.

  I followed several links to create a virtual laboratory, but should not be this hard to run a program.  It's my first time that you try to use VMware tools, but I'm following the steps in the lab below install procedures.

  In the middle of the page of "Blog Editor" part 4 "build the ultimate vSphere Lab is where it installs the VMware tool and lowest after restarting Windows Update service I'm stuck to the next step."

  "Open VMware Tools, go to the Shrink ."  Click on the button of the prepare to shrink . »

  ?  How to "open the VMware Tools?

  Now on the path I have searched for and deleted and reinstalled the tools, but always without success.

  Here is a link where I found the following measures to be taken, but it doesn't work either.  The "NOTE" at the bottom, it's something I noticed and made sure was right when I installed the last time tools.

  I even found a link to where you can download the tools separately from the ISO files, and yet, it does not work.  A LITTLE HELP PLEASE!

  http://www.vdsyn.com/Windows-2008-R2-virtual-machine-VMware-tools-shows-not-running-current-after-vmotionsnapshot-operations-randomly/

  So next step that we did was
  1 uninstalled VMware Tools in the virtual machine
  2 restarted the VM
  3. manually deleted/renamed the C:\Program VMware Tools
  4. manually deleted/renamed C:\Programdata\VMware\VMware tools
  5 Rebooted
  6. install the VMware tools
  7 Rebooted

  The issue is not reproducible after the same

  
  NOTE: Make sure that the virtual computer CD player points to the correct image.  I found it always go back to the windows 7 iso image on my C: drive from physical machines to where the image 2008r2 was on drive E:

  No need to reinstall again. You're not missing something. VMware has changed the VMware Tools tray and removed options that were available in previous versions. Take a look at for example experience front of VMware: The VMware Tools GUI is gone - now what? with some information about this change and the replacement of the command line.

  André

• VMware tools for windows 98

  I'm fighting for two hours just to find the @$ & #^! VMware tools for Windows 98.

  For admins:

  Is it so difficult to include a link and a line on the site somewhere?

  With so many questions posted here, you already know that you don't have to make it all work automated, so in many cases a manual alternative is the only option.

  After the installation of Windows 98, there was a message that Vmware tools OS installed but I still only 16 colors, 640 x 480 res and an answer that is worse than a slideshow, so I guess that no Vmware tools have been installed.

  I tried some of the ISO images here https://packages.vmware.com/tools/esx/index.html but they are not accepted for the player or the operating system.

  So, Vmware tools option exists for Windows 98 or not?

  Hello

  you do not have the option:

  Player - manage?  (because theire you might normally before the installation process) to mount the iso,... and so on

  have you tried to mount the Iso local player manually? (not the source vmware Web)

  you have enough disk space?

  Best regards

  Max

• Cannot install VMWare Tools on virtual Mac

  I created a virtual instance of a Mac (Mountain Lion) on my Windows 7 system.

  I click the button on the drive, select manage and then install VMware Tools. I get an error: component not found on the update server. Contact VMware Support or your system administrator.

  I have confirmed that I can browse the Internet from the virtual system. What other steps should I take, so that I can install the tools?

  Thank you

  Virginia

  Post edited by: BigSam1 Thanks to each of you for the information. I was curious to know if this could be done, so I searched and found a blog with instructions. Now that I know it's not cool to do, I have deleted the virtual Mac.

  Because MAC OS on an Apple brand hardware not violates Apple EULA, this is not supported by VMware Player, which is the reason why there are not VMware Tools available for it.

  André

• VMware Tools release notes

  Is anyone able to provide me with the release notes for each version of vmware tools?

  was a search on the web, but was unable to find anything.

  I remember that there is not a note of support for VMware Tools - it's buried in the Release Notes for ESX/ESXi because it is a piece of ESX/ESXi

• VMware tools report

  Hi all

  I am trying to extract a progress report from VMware Tools Using PowerShell, the script below does not solve my goal, but I'm the output is empty for details ESX. Am I missing something?

  SE connect-VIServer xxxxx
  $esx = get-VMHost
  Get - VM | Get-View | `
  Select @{N = "VMName"; E={$_. Name}},
  @{N = "HardwareVersion"; E={$_. Config.Version}},
  @{N = "ToolsVersion"; E={$_. Config.Tools.ToolsVersion}},
  @{N = "ToolsStatus"; E={$_. Summary.Guest.ToolsStatus}},
  @{N = "ToolsVersionStatus"; E={$_. Summary.Guest.ToolsVersionStatus}},
  @{N = "ToolsRunningStatus"; E={$_. Summary.Guest.ToolsRunningStatus}},
  @{N = 'Cluster'; E={$_ | Get-Cluster}},
  @{N = "ESX host"; E = {$esx. Name}},
  @{N = 'ESX Version'; E = {$esx. Version}},
  @{N = "ESX Build"; E = {$esx. Build}} | `
  Export-Csv "P:\Desktop\Tools.csv" - NoTypeInformation
  Disconnect-VIServer xxxxx - confirm: $false
  Failed to retrieve the stats for the Cluster and ESX host corresponding to the Virtual Machine.

  Can someone please?

  Thank you

  Mohammed

  Try it like this

  Connect-VIServer xxxxxGet-VM | `Select @{N="VMName"; E={$_.Name}},@{N="HardwareVersion"; E={$_.Extensiondata.Config.Version}},@{N="ToolsVersion"; E={$_.Extensiondata.Config.Tools.ToolsVersion}},@{N="ToolsStatus"; E={$_.Extensiondata.Summary.Guest.ToolsStatus}},@{N="ToolsVersionStatus"; E={$_.Extensiondata.Summary.Guest.ToolsVersionStatus}},@{N="ToolsRunningStatus"; E={$_.Extensiondata.Summary.Guest.ToolsRunningStatus}},@{N="Cluster"; E={(Get-Cluster -VM $_.Name).Name}},@{N="ESX Host"; E={$_.Host.Name}},@{N="ESX Version"; E={$_.Host.Version}},@{N="ESX Build"; E={$_.Host.Build}} | ` Export-Csv "P:\Desktop\Tools.csv" -NoTypeInformationDisconnect-VIServer xxxxx -Confirm:$false
  

• Rule gold for the resettlement of the VMWare Tools?

  "The VMware Tools package includes a display driver that has been optimized for the guest operating system running in a virtual machine."

  KB http://bit.ly/bdXGhX

  Is this compatible with the other components of tools? This makes me think that the only factors that affect installation tools are the guest operating system and the host operating system, but that doesn't seem fair to me.

  I wonder what situations dictate that the tools be reinstalled on an existing virtual machine?  For example:

  VM moves a version of workstation player, ESXi, to another (5 WS WS 6, ESX ESX 3.5 3.0). Some requiring the use of the converter except with worms backward compatibility.

  VM moves product i.e. ESXi on workstation, the desktop player. I think that this is supported only through the help of converter, but sometimes operates independently.

  VM moves from machine A to machine B / Server A, Server B both using the same product. (Share/copy a virtual machine)

  Move VM includes change of machine and version.

  Put VM at level in a newer version of the workstation.

  etc...

  In my experience sometimes changes invites for a relocation/development tools while other times there are no complaints of the virtual machine. If the performance takes a hit seems to be hit or miss, and it reduces the field to tools is difficult because of the variety of hardware and software factors. The only advice that I seem to be able to find is "install VMWare Tools".

  Hello

  Sorry did not read the article linked, but...

  Is this compatible with the other components of tools? This makes me think that the only factors that affect installation tools are the guest operating system and the host operating system, but that doesn't seem fair to me.

  No, it's not, the VMware product and version used also play an important role.

  Rule of thumb here is that you want to keep the version of VMware Tools in sync. While their is certainly backwards compatibility, there is no guarantee that it will work well if not a match.

  VM moves a version of workstation player, ESXi, to another (5 WS WS 6, ESX ESX 3.5 3.0). Some requiring the use of the converter except with worms backward compatibility.

  If you move between the major releases of the product you want to reinstall VMware Toools

  VM moves product i.e. ESXi on workstation, the desktop player. I think that this is supported only through the help of converter, but sometimes operates independently.

  If you keep the main synchronized versions then it usually works very well. So you can move a machine virtual merger 3.0.x to workstation 7.0.x for Server 2.0.x (even to vSphere ESX) without reinstalling VMware Tools. With vSphere, this depends somewhat on the guest like e.g. vSphere can't stand aero, so you would have no problem to a VM Win7 native of vSphere Workstation, but a native Win7 VM from Workstation to vSphere his video card driver needs changed.

  VM moves from machine A to machine B / Server A, Server B both using the same product. (Share/copy a virtual machine)

  Normally, no relocation is necessary if the VMware product is at the same level of review.

  Move VM includes change of machine and version.

  See previous answer

  Put VM at level in a newer version of the workstation.

  It depends on... most of the time a newer version of the product VMware also upgraded to a newer version of VMware Tools, but it is not completely 1 on 1.

  > The only advice that I seem to be able to find is "install VMWare Tools".

  That's good advice, but it is not always necessary.

  Hope this helps,

  --
  Wil
  _____________________________________________________
  VI Toolkit & scripts wiki at http://www.vi-toolkit.com

  Writer to the blog www.planetvm.net

  Twitter: @wilva

• VMware-tools of are needed?

  VMware-tools in a linux guest, who does not use a graphical environment but the shell only?

  See page 155

  http://www.VMware.com/PDF/vi3_35/esx_3/r35u2/vi3_35_25_u2_admin_guide.PDF

• Update the vmWare tools in VoP via vCenter

  I'm still new to this community and I hope I'll catch up here soon, but I'm not sure of the update process the vmtools on the device of VoP. I know once I spunt'sand he upwards and configured the IP etc, the vCenter as the tools were obsolete. Tonight is our night of patch management and we'd get VoP abreast, as far as tools go. What is the process to get this done? Do I just shoot vCenter or are there steps to perform on the server of VoP so.

  Thank you in advance for your help!

  Hi David,

  You can update VMWare Tools on the device in the same way as you would for any virtual machine of OpenSUSE Linux.  This can be done manually from the console if vCenter may not withdraw that, alone.

  I hope this helps!

• 8.0.2 - > 8.1.0 vmware tools (win64) usb FTDI driver problem

  I'm Win10x64 running on latest El Capitan.  When I upgraded from fusion 8.0.2 to 8.1.0, I could no longer communicate with all FTDI device that I plugged in USB.  There are some devices that I have with FTDI chips create COM serial ports (debugger microcontroller pods, etc.).

  To go back, I uninstalled vmware tools and downgraded fusion to 8.0.2 and reinstalled the previous vmware tools and everything works well.  Something seems to have changed in 8.1.0 that breaks it.

  Yes, it is a known issue in the merger 8.1 and should be fixed in the next version of the patch. In the meantime, version 8.0.2.

• VMware tools

  When I decide to use the style pension RHEL based tools vmwrae, I take a step back, he me reason not to do so, update-tools-NoReboot - RunAsync, pls correct me if wrong

  I think that only works when we have the tools are installed using the mount traditinal CD

  Also it is a big limitation, Vmware release new patches every 2 to 3 months, now, if we have repo in a central nas mount, we need to upgrade this repo often so if you said Chief revenue you must update etc, update-Tools is so much easier with update-tools is easier and does not need updated repo & updated recipes from the head (for that matter puppet thing), all entries or suggestion or am I missing something here?

  Thank you

  As far as I know, Yes.

  RHEL based repository is intended for virtual computers that run a Linux guest operating system.

  And Yes, you will maintain this directory.

  The advantage is that you can install/upgrade VMware Tools in your Linux virtual machines in the same way as other SW packages.

  The cmdlet Update-Tools works only in ESXI ISO files.

• Upgrade VMware Tools to 11.1 in Xubuntu invited 14.04 fails

  Hello

  Upgrade VMware Tools from 11.0 to 11.1 in Xubuntu 14.04 fails - see the error message below.

  My Xubuntu 14.04 is up-to-date. I've recently performed 'apt - get dist-upgrade'.

  I can continue with the installation, but then shared folders does not work.

  I don't know what the problem... Everything has worked fine up to 11.0 and I never had problems with VMware Tools upgrade. Help, please.

  Annex: Error Message

  Using the kernel build system.

  "do: Verzeichnis" / tmp/modconfig-snuOuv/vmhgfs-only 'enter wird. "

  / usr/bin/make /lib/modules/3.13.0-46-generic/build/include/ - c... SUBDIRS = $PWD SRCROOT = $PWD. \

  MODULEBUILDDIR = modules

  make [1]: Verzeichnis»/usr/src/linux-headers-3.13.0-46-generic«wird enter

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

  In file included from usr/src/linux-headers-3.13.0-46-generic/arch/x86/include/asm/percpu.h:44:0,

  of usr/src/linux-headers-3.13.0-46-generic/arch/x86/include/asm/preempt.h:5.

  of include/linux/preempt.h:18.

  of include/linux/spinlock.h:50.

  of include/linux/mmzone.h:7.

  of include/linux/gfp.h:4.

  of include/linux/mm.h:8.

  of include/linux/pagemap.h:7.

  from /tmp/modconfig-snuOuv/vmhgfs-only/inode.c:29:

  /tmp/modconfig-snuOuv/vmhgfs-only/inode.c: in function 'HgfsPermission ':

  include/Linux/kernel.h:793:27: error: 'struct dentry' has no member named 'd_alias '.

  const typeof (((type *) 0)-> member) * __mptr = (ptr); \

  ^

  include/linux/List.h:687:40: Note: the expansion of the macro «container_of»

  #define hlist_entry (ptr, type, member) container_of (ptr, type, member)

  ^

  include/linux/List.h:698:15: Note: the expansion of the macro 'hlist_entry '.

  ___ptr? hlist_entry (___ptr, type, member): NULL; \

  ^

  include/linux/List.h:708:13: Note: the expansion of the macro 'hlist_entry_safe '.

  for (pos = hlist_entry_safe ((head)-> first, typeof (* (pos)), member); \)

  ^

  /tmp/modconfig-snuOuv/vmhgfs-only/inode.c:1920:7: Note: the expansion of the macro 'hlist_for_each_entry '.

  hlist_for_each_entry (dentry,

  ^

  include/Linux/kernel.h:793:48: warning: initialization of the [default] incompatible pointer type

  const typeof (((type *) 0)-> member) * __mptr = (ptr); \

  ^

  include/linux/List.h:687:40: Note: the expansion of the macro «container_of»

  #define hlist_entry (ptr, type, member) container_of (ptr, type, member)

  ^

  include/linux/List.h:698:15: Note: the expansion of the macro 'hlist_entry '.

  ___ptr? hlist_entry (___ptr, type, member): NULL; \

  ^

  include/linux/List.h:708:13: Note: the expansion of the macro 'hlist_entry_safe '.

  for (pos = hlist_entry_safe ((head)-> first, typeof (* (pos)), member); \)

  ^

  /tmp/modconfig-snuOuv/vmhgfs-only/inode.c:1920:7: Note: the expansion of the macro 'hlist_for_each_entry '.

  hlist_for_each_entry (dentry,

  ^

  In file included from include/linux/compiler-gcc.h:106:0,

  of include/linux/compiler.h:54.

  of include/uapi/linux/stddef.h:1.

  of include/linux/stddef.h:4.

  of usr/src/linux-headers-3.13.0-46-generic/include/uapi/linux/posix_types.h:4.

  of include/uapi/linux/types.h:13.

  of include/linux/types.h:5.

  of tmp/modconfig-snuOuv/vmhgfs-only/./shared/driver-config.h:71.

  from /tmp/modconfig-snuOuv/vmhgfs-only/inode.c:26:

  include/Linux/compiler-gcc4.h:14:34: error: 'struct dentry' has no member named 'd_alias '.

  #define __compiler_offsetof(a,b) __builtin_offsetof (a, b)

  ^

  include/linux/STDDEF.h:17:31: Note: the expansion of the macro '__compiler_offsetof '.

  #define offsetof (TYPE, MEMBER) __compiler_offsetof (TYPE, MEMBER)

  ^

  include/Linux/kernel.h:794:29: Note: the expansion of the macro "offsetof".

  (type *) ((char *) __mptr - offsetof (type, member)) ;})

  ^

  include/linux/List.h:687:40: Note: the expansion of the macro «container_of»

  #define hlist_entry (ptr, type, member) container_of (ptr, type, member)

  ^

  include/linux/List.h:698:15: Note: the expansion of the macro 'hlist_entry '.

  ___ptr? hlist_entry (___ptr, type, member): NULL; \

  ^

  include/linux/List.h:708:13: Note: the expansion of the macro 'hlist_entry_safe '.

  for (pos = hlist_entry_safe ((head)-> first, typeof (* (pos)), member); \)

  ^

  /tmp/modconfig-snuOuv/vmhgfs-only/inode.c:1920:7: Note: the expansion of the macro 'hlist_for_each_entry '.

  hlist_for_each_entry (dentry,

  ^

  In file included from include/linux/preempt.h:10:0,

  of include/linux/spinlock.h:50.

  of include/linux/mmzone.h:7.

  of include/linux/gfp.h:4.

  of include/linux/mm.h:8.

  of include/linux/pagemap.h:7.

  from /tmp/modconfig-snuOuv/vmhgfs-only/inode.c:29:

  include/linux/List.h:710:35: error: 'struct dentry' has no member named 'd_alias '.

  POS = hlist_entry_safe ((pos)-> member.next, typeof (* (pos)), member))

  ^

  include/linux/List.h:697:12: Note: in the definition of the macro 'hlist_entry_safe '.

  ({typeof (ptr) ___ptr = (ptr); \})

  ^

  /tmp/modconfig-snuOuv/vmhgfs-only/inode.c:1920:7: Note: the expansion of the macro 'hlist_for_each_entry '.

  hlist_for_each_entry (dentry,

  ^

  include/linux/List.h:710:35: error: 'struct dentry' has no member named 'd_alias '.

  POS = hlist_entry_safe ((pos)-> member.next, typeof (* (pos)), member))

  ^

  include/linux/List.h:697:28: Note: in the definition of the macro 'hlist_entry_safe '.

  ({typeof (ptr) ___ptr = (ptr); \})

  ^

  /tmp/modconfig-snuOuv/vmhgfs-only/inode.c:1920:7: Note: the expansion of the macro 'hlist_for_each_entry '.

  hlist_for_each_entry (dentry,

  ^

  In file included from usr/src/linux-headers-3.13.0-46-generic/arch/x86/include/asm/percpu.h:44:0,

  of usr/src/linux-headers-3.13.0-46-generic/arch/x86/include/asm/preempt.h:5.

  of include/linux/preempt.h:18.

  of include/linux/spinlock.h:50.

  of include/linux/mmzone.h:7.

  of include/linux/gfp.h:4.

  of include/linux/mm.h:8.

  of include/linux/pagemap.h:7.

  from /tmp/modconfig-snuOuv/vmhgfs-only/inode.c:29:

  include/Linux/kernel.h:793:27: error: 'struct dentry' has no member named 'd_alias '.

  const typeof (((type *) 0)-> member) * __mptr = (ptr); \

  ^

  include/linux/List.h:687:40: Note: the expansion of the macro «container_of»

  #define hlist_entry (ptr, type, member) container_of (ptr, type, member)

  ^

  include/linux/List.h:698:15: Note: the expansion of the macro 'hlist_entry '.

  ___ptr? hlist_entry (___ptr, type, member): NULL; \

  ^

  include/linux/List.h:710:13: Note: the expansion of the macro 'hlist_entry_safe '.

  POS = hlist_entry_safe ((pos)-> member.next, typeof (* (pos)), member))

  ^

  /tmp/modconfig-snuOuv/vmhgfs-only/inode.c:1920:7: Note: the expansion of the macro 'hlist_for_each_entry '.

  hlist_for_each_entry (dentry,

  ^

  include/Linux/kernel.h:793:48: warning: initialization makes pointer from integer without a cast [default]

  const typeof (((type *) 0)-> member) * __mptr = (ptr); \

  ^

  include/linux/List.h:687:40: Note: the expansion of the macro «container_of»

  #define hlist_entry (ptr, type, member) container_of (ptr, type, member)

  ^

  include/linux/List.h:698:15: Note: the expansion of the macro 'hlist_entry '.

  ___ptr? hlist_entry (___ptr, type, member): NULL; \

  ^

  include/linux/List.h:710:13: Note: the expansion of the macro 'hlist_entry_safe '.

  POS = hlist_entry_safe ((pos)-> member.next, typeof (* (pos)), member))

  ^

  /tmp/modconfig-snuOuv/vmhgfs-only/inode.c:1920:7: Note: the expansion of the macro 'hlist_for_each_entry '.

  hlist_for_each_entry (dentry,

  ^

  In file included from include/linux/compiler-gcc.h:106:0,

  of include/linux/compiler.h:54.

  of include/uapi/linux/stddef.h:1.

  of include/linux/stddef.h:4.

  of usr/src/linux-headers-3.13.0-46-generic/include/uapi/linux/posix_types.h:4.

  of include/uapi/linux/types.h:13.

  of include/linux/types.h:5.

  of tmp/modconfig-snuOuv/vmhgfs-only/./shared/driver-config.h:71.

  from /tmp/modconfig-snuOuv/vmhgfs-only/inode.c:26:

  include/Linux/compiler-gcc4.h:14:34: error: 'struct dentry' has no member named 'd_alias '.

  #define __compiler_offsetof(a,b) __builtin_offsetof (a, b)

  ^

  include/linux/STDDEF.h:17:31: Note: the expansion of the macro '__compiler_offsetof '.

  #define offsetof (TYPE, MEMBER) __compiler_offsetof (TYPE, MEMBER)

  ^

  include/Linux/kernel.h:794:29: Note: the expansion of the macro "offsetof".

  (type *) ((char *) __mptr - offsetof (type, member)) ;})

  ^

  include/linux/List.h:687:40: Note: the expansion of the macro «container_of»

  #define hlist_entry (ptr, type, member) container_of (ptr, type, member)

  ^

  include/linux/List.h:698:15: Note: the expansion of the macro 'hlist_entry '.

  ___ptr? hlist_entry (___ptr, type, member): NULL; \

  ^

  include/linux/List.h:710:13: Note: the expansion of the macro 'hlist_entry_safe '.

  POS = hlist_entry_safe ((pos)-> member.next, typeof (* (pos)), member))

  ^

  /tmp/modconfig-snuOuv/vmhgfs-only/inode.c:1920:7: Note: the expansion of the macro 'hlist_for_each_entry '.

  hlist_for_each_entry (dentry,

  ^

  make [2]: * [/ tmp/modconfig-snuOuv/vmhgfs-only/inode.o] Fehler 1

  make [2]: * Auf noch nicht processes wird going going...

  make [1]: * [_module_/tmp/modconfig snuOuv/vmhgfs-only] error 2

  make [1]: Verzeichnis»/usr/src/linux-headers-3.13.0-46-generic«verlassen wird

  make: * [vmhgfs.ko] Fehler 2

  "do: Verzeichnis" / tmp/modconfig-snuOuv/vmhgfs-only "verlassen wird."

  The filesystem (vmhgfs module) driver is used only for the shared folder

  feature. The rest of the software provided by VMware Tools is designed to work

  regardless of this function.

  If you want the shared folders feature, you can install the driver of

  running vmware-config - tools.pl again after making sure that gcc, binutils, make

  and your kernel sources are installed on your computer.

  These packages are available on the installation of your distribution CD.

  [Press the Enter key to continue]

  As Barney42 pointed out, this question comes with the new kernel 3.13.0 - 46. And indeed helped me to find a workaround:

  Tools can be patched manually. In vmhgfs.tar, inode.c d_alias should be replaced by d_u.d_alias put it back to the tar and then recompile tools.

  Here is a script that does this (tested on ubuntu 32 bit 14.04, vmware workstation on a windows host 11.1):

  #!/bin/sh -x
cd /usr/lib/vmware-tools/modules/source
tar xf vmhgfs.tar
grep -q d_u.d_alias vmhgfs-only/inode.c && echo "already patched" && exit 0
sed -i -e s/d_alias/d_u.d_alias/ vmhgfs-only/inode.c
cp -p vmhgfs.tar vmhgfs.tar.orig
tar cf vmhgfs.tar vmhgfs-only
vmware-config-tools.pl -d -m

  NOTE: This makes incompatible tools with older versions of the kernel, i.e. 3.13.0 - 45.

  (Original post at askubuntu)

  However, @VMware-team, please do run again out of the box, or submit a patch for the Linux kernel. You are a large business, should be no problem.