VMware Tools Part 2 – Versions and Changes

VMware ToolsIn part 1 I covered the overview about VMware Tools (What is VMware Tools, What are the 3 types of VMware Tools, What is the differences between them etc.). In part 2 I will now cover the question which VMware Tools version comes with which vSphere Patch/Update starting with 5.5. Getting Release Notes from older VMware Tools versions was always a challenge that’s why I created a list with every change, you can find in the corresponding KB article. To find the necessary information just click the VMware Tools (Guest OS) version link.

Why I’m not starting with 5.0/5.1? Simple answer is because general supports of this versions will end on August 24th, 2016 and is therefor from my perspective no longer relevant.

ESXi versions and corresponding VMware Tools versions

ProductVersionPatchBuildRelease DatePatch KB ArticleTools-light versionTools Light KB ArticelVMware Tools (Guest OS)VMware Tools (WebClient)
ESXi6.0Update 2362075916.03.2016Link6.0.0-2.34.3620759Link10.0.610246
ESXi6.0Express Patch 5356894023.02.2016Link6.0.0-1.26.338012410.0.010240
ESXi6.0Update 1b338012407.01.2016Link6.0.0-1.26.3380124Link
Link
10.0.010240
ESXi6.0Express Patch 4324772025.11.2015Link6.0.0-1.17.30297589.10.59541
ESXi6.0Update 1a (Express Patch 3)307314606.10.2015Link6.0.0-1.17.30297589.10.59541
ESXi6.0Update 1302975810.09.2015Link6.0.0-1.17.3029758Link
Link
9.10.59541
ESXi6.0ESXi 6.0.0b280920907.07.2015Link6.0.0-0.11.2809209Link
Link
9.10.19537
ESXi6.0Express Patch 2271544014.05.2015Link6.0.0-0.0.24945859.10.09536
ESXi6.0Express Patch 1261570409.04.2015Link6.0.0-0.0.24945859.10.09536
ESXi6.0GA249458512.03.20156.0.0-0.0.24945859.10.09536
ESXi5.5Express Patch 10356872222.02.2016Link5.5.0-3.78.324854710.0.010240
ESXi5.5Express Patch 9334334304.01.2016Link5.5.0-3.78.324854710.0.010240
ESXi5.5Update 3b324854708.12.2015Link5.5.0-3.78.3248547Link
Link
10.0.010240
ESXi5.5Update 3a (Express Patch 8)311689506.10.2015Link5.5.0-3.68.30299449.4.159359
ESXi5.5Update 3302994416.09.2015Link5.5.0-3.68.3029944Link
Link
9.4.159359
ESXi5.5Patch 5 re-release271805508.05.2015Link5.5.0-2.62.2718055Link9.4.129356
ESXi5.5Express Patch 7263830107.04.2015Link5.5.0-2.54.24033619.4.119355
ESXi5.5Express Patch 6245637405.02.2015Link5.5.0-2.54.24033619.4.119355
ESXi5.5Patch 4240336127.01.2015Link5.5.0-2.54.2403361Link9.4.119355
ESXi5.5Express Patch 5230265102.12.2014Link5.5.0-2.39.21438279.4.109354
ESXi5.5Patch 3214382715.10.2014Link5.5.0-2.39.2143827Link9.4.109354
ESXi5.5Update 2206819009.09.2014Link5.5.0-2.33.2068190Link9.4.109354
ESXi5.5Patch 2189279401.07.2014Link5.5.0-1.28.1892794Link
Link
9.4.69350
ESXi5.5Express Patch 4188173711.06.2014Link5.5.0-1.16.17460189.4.59349
ESXi5.5Update 1a174601819.04.2014Link5.5.0-1.16.1746018Link9.4.59349
ESXi5.5Update 1162338711.03.2014Link5.5.0-1.15.1623387Link
Link
9.4.59349
ESXi5.5Patch 1147452822.12.2013Link5.5.0-0.8.1474528Link9.4.09344
ESXi5.5GA133182022.09.20135.5.0-0.0.13318209.4.09344

Release Notes VMware Tools

10.0.6 (ESXi 6.0 Update 2)

What’s New

vmxnet3 driver: The new vmxnet3 driver prevents the Windows Operating System from overriding the Internet Group Management Protocol (IGMP) snooping configuration in DVSwitch.

Resolved Issues

Windows Guest Operating System customization fails to complete
Windows guest Operating System customization fails to complete if the base VM has upgraded tools from build 2981885 (version 9.10.5.49873) to build 3000743 (version 10.0.0.50046) or build 3227872 (version 10.0.5.52125). This issue is resolved by upgrading VMware Tools to this release.

10.0.5

What’s New

Drivers and Certifications: Signed Windows Display Driver Model (WDDM) 8.15.1.33 graphics driver for VMware Tools 10.0.5

Resolved Issues

VMware Tools might stop responding while opening the Network File System mounts
When you take a quiesced snapshot on a Linux virtual machine, VMware Tools might stop responding while opening the Network File System (NFS) mounts and result in all filesystem activity to stop on the guest operating system. An error message similar to the following is displayed and the virtual machine stops responding:

An error occurred while saving the snapshot: msg.snapshot.error-QUIESCINGERROR

This issue is resolved in this release.

Unable to open telnet on Windows 8 or Windows Server 2012 guest operating system after installing VMware Tools
After installing VMware Tools on Windows 8 or Windows Server 2012 guest operating system, attempts to open telnet using the start telnet://xx.xx.xx.xx command fails with the following error message:
Make sure the virtual machine’s configuration allows the guest to open host applications

This issue is resolved in this release.

Rebooting or shutting down might cause kernel panic in Linux systems with kernel versions lower than 3.9
Rebooting or shutting down the guest OS might cause kernel panic in the RHEL operating system with kernel versions lower than 3.9.

This issue is resolved in this release.

vmusr reports log spew with a warning message
vmusr reports log spew  of VMware Tools. In the Windows Application Event log, you might see this warning error message reported multiple times in quick succession:

“[ warning] [vmusr:vmusr] SimpleSock: Socket # closed by peer.”

This issue is resolved in this release.

 Upgrading VMware Tools on Mac OS X guest operating system fails
Upgrading VMware Tools on Mac OS X guest operating system fails with an error similar to the following:

“The installation failed”

This issue is resovled in this release.

10.0.0 (ESXi 5.5 Update 3, ESXi 6.0 Update 1b)

What’s new

  • Common versioning: Infrastructure changes to enable reporting of true versions for VMware Tools Operating System Specific Packages. These changes will depend on host support.
  • Common Agent Framework: Common Agent Framework (CAF) provides the basic services necessary to simplify secure and efficient management of agents inside the guest virtual machines.
  • Quiesced snapshots enhancements on Linux: Robustness related enhancements in quiesced snapshot operation. vmtoolsd service supports caching of log messages when guest I/O has been quiesced. Enhancements in vmbackup plug in to use a separate thread to quiesce the guest operating system to avoid timeout issues due to heavy I/O in the guest.
  • Shared folders: For Linux distributions with kernel version 4.0.0 and higher, there is a new FUSE  based Shared Folders client which is used as a replacement for the kernel mode client.
  • ESXi serviceability: Default vmtoolsd logging is directed to a file instead of Syslog or Event Viewer. Enhanced VMwareToolboxCmd.exe on Windows andvmware-toolbox-cmd on Linux to change vmtoolsd logging levels.
  • GuestInfo enhancements: Plug in enhancements to report more than 64 IP addresses from the guest. These enhancements will depend on host support.

9.10.5 (ESXi 6.0 Update 1)

  • Attempts to install or upgrade to VMware Tools version 9.10.0 available in ESXi 6.0 might fail on Dutch version of Windows Server 2008 R2. An error message similar to the following is displayed:VMware Tools Setup Wizard ended prematurely
  • When you perform a quiesced snapshot of a Linux virtual machine, the VM might fail after the snapshot operation. The following error messages are logged in the vmware.log file:T
    <YYYY-MM-DD>T<TIME>Z| vmx| I120: SnapshotVMXTakeSnapshotComplete: Snapshot 0 failed: Failed to quiesce the virtual machine (40).
    <YYYY-MM-DD>T<TIME>Z| vmx| I120: GuestRpcSendTimedOut: message to toolbox timed out.
    <YYYY-MM-DD>T<TIME>Z| vmx| I120: Vix: [18631 guestCommands.c:1926]: Error VIX_E_TOOLS_NOT_RUNNING in MAutomationTranslateGuestRpcError(): VMware Tools are not running in the guest

9.10.1 (ESXi 6.0.0b)

  • After installing VMware Tools on a Windows 8 or Windows Server 2012 guest operating system, attempts to open telnet using the start telnet://xx.xx.xx.xx command fails with the following error message:
    Make sure the virtual machine’s configuration allows the guest to open host applications
  • The vShield Endpoint drivers are renamed as Guest Introspection drivers and two of these drivers, NSX File Introspection driver (vsepflt.sys) and NSX Network Introspection driver (vnetflt.sys), can be installed separately now. This allows you to install the file driver without installing the network driver.
  • When you use Unidesk in conjunction with VMware View or vSphere with vShield Endpoint enabled, applications such as QuickTime might experience a slowdown in performance. This is due to an interoperability issue that is triggered when the Unidesk volume serialization filter driver and the vShield driver are present on the stack. For each file opened by the application, even if it is just for reading the attributes, the vShield driver calls FltGetFileNameInformation, causing further processing to be performed on the files. As a result, Unidesk driver opens directories and causes an overall application performance degradation.
  • IPv6 Router Advertisements (RA) do not function as expected when tagging 802.1q with VMXNET3 adapters on a Linux virtual machine as the IPv6 RA address intended for the VLAN interface is delivered to the base interface.
  • Quiesced snapshot might fail due to a race condition during snapshot initialization. An error message similar to the following is displayed on the Tasks and Events tab of the vCenter Server:An error occurred while saving the snapshotYou might also see the following information in the guest event log:
    System Event Log
    Source: Microsoft-Windows-DistributedCOM
    Event ID: 10010
    Level: Error
    Description:
    The server {nnnnnnnn-nnnn-nnnn-nnnn-nnnnnnnnnnnn} did not register with DCOM within the required timeout.
  • Attempts to perform a quiesced snapshot on a virtual machine running Microsoft Windows 2008 or later might fail and the VM might panic with a blue screen and error message similar to the following:A problem has been detected and Windows has been shut down to prevent damage to your computer. If this is the first time you’ve seen this Stop error screen restart your computer. If this screen appears again, follow these steps:Disable or uninstall any anti-virus, disk defragmentation or backup utilities. Check your hard drive configuration, and check for any updated drivers. Run CHKDSK /F to check for hard drive corruption, and then restart your computer.This patch resolves the issue. For more information, see KB 2115997.

9.4.15 (ESXi 5.5 Update 3)

  • On a Linux virtual machine, the VMware Tools service, vmtoolsd, might fail when you shut down the guest operating system.
  • Attempts to upgrade VMware Tools on a Windows 2000 virtual machine might fail with an error message similar to the following written to the vmmsi.log file:
    Invoking remote custom action. DLL: C:\WINNT\Installer\MSI12.tmp, Entrypoint: VMRun
    VM_CacheMod. Return value 3.
    PROPERTY CHANGE: Deleting RESUME property. Its current value is ‘1’.
    INSTALL. Return value 3.
  • On an ESXi 5.5 host, some of the drivers installed on Solaris 11 guest operating system might be from Solaris 10. As a result, the drivers might not work as expected.
  • When you attempt to configure VMware Tools with new kernel using the /usr/bin/vmware-config-tools.pl -k  script after the kernel has been updated with Dracut, the driver list in add_drivers entry of/etc/dracut.conf.d/vmware-tools.conf file gets truncated. This issue occurs when the VMware Tools are upstreamed in the kernel.
  • A Linux virtual machine enabled with Large Receive Offload (LRO) functionality on VMXNET3 device might experience packet drops on the receiver side when the Rx Ring #2 runs out of memory, since the size of Rx Ring#2 is unable to be configured originally.
  • When you upgrade the Vmware Tools in 64-bit Windows guest operating system, the tools.conf file gets removed automatically. Thetools.conf file will be retained by default from ESXi 5.5 Update 3 release onwards.
  • After installing VMware Tools on Windows 8 or Windows Server 2012 guest operating system, attempts to open telnet using the start telnet://xx.xx.xx.xx command fails with the following error message
    Make sure the virtual machine’s configuration allows the guest to open host applications 
  • When you power off a virtual machine immediately after an install, upgrade or uninstall of VMware Tools in a Linux environment (RHEL or Cent OS 6), the guest OS might fail during the next reboot due to corrupted RAMDISK image file. The guest OS reports an error similar to the following:RAMDISK: incomplete write (31522 != 32768)
    write error
    Kernel panic – not syncing : VFS: Unable to mount root fs on unknown-block(0,0)This release resolves the complete creation of the initramfs file creation during an install, upgrade or uninstall of VMware Tools.Guest OS with corrupted RAMDISK image file can be rescued to complete boot state. For more information, see Knowledge Base article 2086520.
  • During a High Availability failover or host crash, the .vswp files of powered ON virtual machines on that host might be left behind on the storage. When many such failovers or crashes occur, the storage capacity might become full.
  • IPv6 Router Advertisements (RA) does not function as expected when tagging 802.1q with VMXNET3 adapters in an Linux virtual machine as the IPv6 RA address intended for the VLAN interface is delivered to the base interface.

9.4.12 (ESXi 5.5 Patch 5)

  • Virtual machines with Linux guest operating system might stop responding due to kernel panic in balloon driver. You might see backtrace similar to the following:[ ] :vmmemctl:Balloon_QueryAndExecute+0x67/0x9cc
    [ ] :vmmemctl:OS_UnmapPage+0x102/0x2a0
    [ ] autoremove_wake_function+0x0/0x2e
    [ ] autoremove_wake_function+0x0/0x2e
    [ ] :vmmemctl:OS_UnmapPage+0x8/0x2a0
    [ ] kthread+0xfe/0x132
    [ ] child_rip+0xa/0x11
    [ ] keventd_create_kthread+0x0/0xc4
    [ ] kthread+0x0/0x132
    [ ] child_rip+0x0/0x11For details, see KB 2107363.
  • The vShield Endpoint drivers are renamed as Guest Introspection Drivers and two of these drivers, NSX File Introspection Driver (vsepflt.sys) and NSX Network Introspection Driver (vnetflt.sys), can be installed separately now. This allows you to install the file driver without installing the network driver.
  • When Unidesk is used in conjunction with VMview or vSphere with vShield Endpoint enabled, applications such as QuickTime might experience a slowdown in performance. This is due to an interoperability issue that gets triggered when Unidesk volume serialization filter driver and vShield driver is present on the stack. For each file opened by the application, even if it is just for reading the attributes, the vShield driver calls FltGetFileNameInformation causing further processing to be performed on the files. As a result Unidesk driver opens directories that causes an overall application performance degradation.

9.4.11 (ESXi 5.5 Patch 4)

  • The VMware Tools status for Solaris virtual machine might report an Out of date status error in vSphere Client for new VMware Tools. This is because the ESXi has no AVR manifest for Solaris.
  • When multiple users login to virtual machines running Windows operating systems using the Windows Remote Desktop Protocol (RDP), VMware Tools might fail with an error similar to the following:
    VMware Tools unrecoverable error: (vthread-3)
    Exception 0xc0000005 (access violation) has occured
  • When a quiesced snapshot is created on a Windows Server 2003, Windows Server 2003 R2, Windows Server 2008, Windows Server 2008 R2, or a Windows Server 2012 virtual machine, duplicate disks might be created in the virtual machine.

9.4.10 (ESXi 5.5 Patch 3)

This patch updates the tools-light VIB to resolve an issue where Windows 2008 R2 virtual machines might stop responding and display a blue screen when the vShield Endpoint Thin Agent driver tries to log a filename.

9.4.10 (ESXi 5.5 Update 2)

  • PR 1089690: VMware vShield Endpoint Thin Agent is renamed as VMware Tools Guest Introspection plug-in. The vShield Endpoint driver bundled with VMware Tools is now called Guest Introspection.
  • PR 1147656: Snapshot quiescing and hot cloning of a Linux virtual machine might fail and error messages similar to the following might be written to vmware.log file:
    2013-12-12T00:09:59.446Z| vcpu-1| I120: [msg.snapshot.quiesce.vmerr] The guest OS has reported an error during quiescing.
    2013-12-12T00:09:59.446Z| vcpu-1| I120+ The error code was: 3
    2013-12-12T00:09:59.446Z| vcpu-1| I120+ The error message was: Error when enabling the sync provider.
    2013-12-12T00:09:59.446Z| vcpu-1| I120: —————————————-
    2013-12-12T00:09:59.449Z| vcpu-1| I120: ToolsBackup: changing quiesce state: STARTED -> ERROR_WAIT
    2013-12-12T00:10:00.450Z| vcpu-1| I120: ToolsBackup: changing quiesce state: ERROR_WAIT -> IDLE
    2013-12-12T00:10:00.450Z| vcpu-1| I120: ToolsBackup: changing quiesce state: IDLE -> DONE
    2013-12-12T00:10:00.450Z| vcpu-1| I120: SnapshotVMXTakeSnapshotComplete: Done with snapshot ‘clone-temp-1386910714682919’: 0
    2013-12-12T00:10:00.450Z| vcpu-1| I120: SnapshotVMXTakeSnapshotComplete: Snapshot 0 failed: Failed to quiesce the virtual machine (40).
  • PR 1204553: Virtual machines running MOVE Agentless 3.0 on ESXi host might appear to become unresponsive with a black screen during login for 40 seconds or more.
  • PR 1214493: The memory balloon driver(VMMEMCTL)might fail to compile in FreeBSD versions 10.0 and above. An error message similar to the following is written to xxx.log:
    — vmmemctl —
    os.c:300:22: error: implicit declaration of function ‘kmem_alloc_nofault’ is invalid in C99[-Werror,-Wimplicit-function-declaration] vm_offset_t res = kmem_alloc_nofault(kernel_map, PAGE_SIZE)^
    os.c:357:14: error: incompatible pointer types passing ‘vm_map_t’ (aka ‘struct vm_map ‘) to parameter of type ‘struct vmem ‘ [-Werror,-Wincompatible-pointer- types] kmem_free(kernel_map, (vm_offset_t)mapping, PAGE_SIZE); ^
    @/vm/vm_extern.h:59:29: note: passing argument to parameter here void kmem_free(struct vmem *, vm_offset_t, vm_size_t);^
  • PR 1216736: After installing VMware Tools 5.1 on a Windows virtual machine, the Windows Application Event log of the guest operating system reports warnings similar to the following:
    [ warning] [vmusr:vmusr] vmware::tools::UnityPBRPCServer::Start: Failed to register with the host!
    [ warning] [vmusr:vmtoolsd] Failed registration of app type 2 (Signals) from plugin unity.
    [ warning] [vmusr:vmusr] Error in the RPC receive loop: RpcIn: Unable to send.
    [ warning] [vmusr:vmusr] socket count not create new socket, error 10047: An address incompatible with the requested protocol was used
    [ warning] [vmusr:vmusr] Channel restart failed [1] 
  • PR 1221217: The Managed Object Browser (MOB) for GuestInfo.ipAddress data object might not be populated correctly and the value of GuestInfo.ipAddress data object might be displayed as unset when more than four NICs are connected. This issue occurs when VMware Tools fails to determine a valid GOS IP address.
  • PR 1252476: When you attempt to install RHEL virtual machines using the kick start file, the operating system specific packages (OSPs) might display error message similar to the following:
    Could not load modules.dep
  • PR 1275409: Attempts to perform vMotion might cause the virtual machines to fail with a blue screen and error messages similar to the following might be written to vmware.log file after you upgrade VMware Tools:
    …2014-05-12T00:07:02.052Z| mks| I120: WinBSOD: ( 1) A problem has be
    2014-05-12T00:07:02.066Z| mks| I120: WinBSOD: ( 1)
    A problem has been detected and Windows has been shut down to prevent damage’
    2014-05-12T00:07:02.083Z| mks| I120: WinBSOD: ( 2) to your computer.'
    2014-05-12T00:07:02.084Z| mks| I120: WinBSOD: ( 4)
    The HTTP ke’
    2014-05-12T00:07:02.100Z| mks| I120: WinBSOD: ( 4) The HTTP kernel driver (http.sys) reached a corrupted state and can not recover.'
    2014-05-12T00:07:02.100Z| mks| I120: WinBSOD: ( 5)
    This means’
    2014-05-12T00:07:02.117Z| mks| I120: WinBSOD: ( 6) that the HTTP module detected that its private data is corrupted. This usually'
    2014-05-12T00:07:02.117Z| mks| I120: WinBSOD: ( 7)
    results in’
    2014-05-12T00:07:02.134Z| mks| I120: WinBSOD: ( 8) eventual corruption of the thread pool and an access violation.'
    2014-05-12T00:07:02.150Z| mks| I120: WinBSOD: (10)
    If this is the first time you’ve seen this Stop err’
    2014-05-12T00:07:02.168Z| mks| I120: WinBSOD: (10) If this is the first time you've seen this Stop error screen,'
    2014-05-12T00:07:02.168Z| mks| I120: WinBSOD: (11)
    restart your computer. If this screen appears again, follow’
    2014-05-12T00:07:02.184Z| mks| I120: WinBSOD: (12) `these steps:

    This issue occurs due to incorrect TCP connection handling in the vShield Endpoint TDI Manager driver, vnetflt.sys.
  • PR 1095969: Upgrading to VMware Tools 5.x causes log spew with the message: Error in the RPC receive loop: RpcIn: Unable to sendThis issue occurs when two or more users are logged into Windows Terminal Server or Linux. To fully resolve the issue, you also need to update the esx-base VIB by applying the ESXi550-201409201-UG bulletin and update the tools-light VIB by applying the ESXi550-201409202-UG bulletin.
  • PR 1141296: deployPkg.dll file which is present in C:\Program Files\Vmware\Vmware Tools\ is not found after you upgrade VMware Tools. This is observed when it is upgraded from version 5.1 U2 to 5.5 U2 and version 5.5 to 5.5 U2.
  • PR 1159505: After you install VMware Tools, the Windows Event Viewer displays a warning similar to the following:
    Unable to read a line from ‘C:\Program Files\VMware\VMware Tools\messages\es\hgfsUsability.vmsg’: Invalid byte sequence in conversion input.This issue is particularly noticed when you install VMware Tools on Spanish locale operating system.
  • PR 1174550: You might be unable to automatically upgrade VMware Tools on 64-bit Linux guest operating systems.Error message similar to the following might be written to /var/log/vmware-tools-upgrader.log file:Executing “/tmp/vmware-root/vmware-tools-upgrader-32 ” /tmp/vmware-root/run_upgrader.sh: line 64: /tmp/vmware-root/vmware-tools-upgrader-32: No such file or directoryThis issue occurs when the ESXi Shell is a symbolic link by default.

9.4.6 (ESXi 5.5 Patch 2)

This patch updates the tools-light VIB to resolve the following issue:

  • When you take a quiesced snapshot on a Linux virtual machine, VMware Tools might stop responding while opening the Network File System (NFS) mounts and result in all filesystem activity to stop on the guest operating system. An error message similar to the following is displayed and the virtual machine stops responding:An error occurred while saving the snapshot: msg.snapshot.error-QUIESCINGERROR

9.4.5 (ESXi 5.5 Update 1a)

This patch updates the tools-light VIB to resolve an issue where after you install VMware Tools on a virtual machine running on ESXi 5.5 host, the ISO image entry might not be removed from the VMX file even though the CD has been ejected and the CD-ROM has been disconnected.

This patch resolves this issue for newly created virtual machines. For existing virtual machines with ISO image entry already present in the VMX file or if a stale entry of the iso path is present on the vSphere Web Client or the vSphere Client, you must run the cdrm_iso_line.py script to remove the entry as described in KB 2076512.

Note: To completely resolve this issue, you must install both the esx-base VIB (ESXi550-201404401-SG) and tools-light VIB (ESXi550-201404402-BG) bulletins of this patch.

9.4.5 (ESXi 5.5 Update 1)

  • PR 1053302: When you attempt a VMware Tools update on an earlier ESXi 5.1.x, the vCenter Protect Agent displays aUnregistering VSS driver warning message, which indicates the use of an unsigned executable. Including the executable to the list of files copied to the install folder resolves this issue.
  • PR 1053397: VMware Tools is updated to provide Oracle Linux 5.x with 2.6.39-200/400 prebuilt kernel modules.
  • PR 1061656: When Receive Side Scaling is enabled on a multi vCPU Windows virtual machine, you see NetPort messages for repeating MAC addresses indicating that ports are being disabled and then re-enabled. In the vmkernel.log , you see messages similar to the following:2013-07-08T06:11:58.158Z cpu4:337203)NetPort: 1424: disabled port 0x1000020
    2013-07-08T06:11:58.177Z cpu4:337203)NetPort: 1237: enabled port 0x1000020 with mac xx:xx:xx:xx:xx:xx
    2013-07-08T06:12:46.191Z cpu1:337203)NetPort: 1424: disabled port 0x1000020
    2013-07-08T06:12:46.211Z cpu7:337203)NetPort: 1237: enabled port 0x1000020 with mac xx:xx:xx:xx:xx:xxThe vmware.log file of virtual machines that use these MAC addresses contain corresponding events similar to the following:2013-07-08T06:18:20.175Z| vcpu-1| Ethernet4 MAC Address: xx:xx:xx:xx:xx:xx
    2013-07-08T06:18:20.199Z| vcpu-1| VMXNET3 user: Ethernet4 Driver Info: version = 833450 gosBits = 2 gosType = 2, gosVer = 24848, gosMisc = 212
    2013-07-08T06:18:36.165Z| vcpu-6| Ethernet4 MAC Address: xx:xx:xx:xx:xx:xx
    2013-07-08T06:18:36.187Z| vcpu-6| VMXNET3 user: Ethernet4 Driver Info: version = 833450 gosBits = 2 gosType = 2, gosVer = 24848, gosMisc = 212
    The VMXNET3 network driver is updated in this release.
  • PR 1095083: When Receive Side Scaling is enabled on a multi vCPU Windows virtual machine, you see NetPort messages for repeating MAC addresses indicating that ports are being disabled and then re-enabled. In the vmkernel.log , you see messages similar to the following:2013-07-08T06:11:58.158Z cpu4:337203)NetPort: 1424: disabled port 0x1000020
    2013-07-08T06:11:58.177Z cpu4:337203)NetPort: 1237: enabled port 0x1000020 with mac xx:xx:xx:xx:xx:xx
    2013-07-08T06:12:46.191Z cpu1:337203)NetPort: 1424: disabled port 0x1000020
    2013-07-08T06:12:46.211Z cpu7:337203)NetPort: 1237: enabled port 0x1000020 with mac xx:xx:xx:xx:xx:xxThe vmware.log file of virtual machines that use these MAC addresses contain corresponding events similar to the following:
    2013-07-08T06:18:20.175Z| vcpu-1| Ethernet4 MAC Address: xx:xx:xx:xx:xx:xx
    2013-07-08T06:18:20.199Z| vcpu-1| VMXNET3 user: Ethernet4 Driver Info: version = 833450 gosBits = 2 gosType = 2, gosVer = 24848, gosMisc = 212
    2013-07-08T06:18:36.165Z| vcpu-6| Ethernet4 MAC Address: xx:xx:xx:xx:xx:xx
    2013-07-08T06:18:36.187Z| vcpu-6| VMXNET3 user: Ethernet4 Driver Info: version = 833450 gosBits = 2 gosType = 2, gosVer = 24848, gosMisc = 212
    The VMXNET3 network driver is updated in this release.
  • PR 1114634: You might be unable to run Petrel 3D application for oil and gas explorations correctly on a virtual machine due to issues with OpenGL graphics driver.
  • PR 1123091: When you are saving files from a Microsoft Office 2007 or Microsoft Office 2010 application to a shared directory on a virtual machine protected by VMware vShield Endpoint and an agentless antivirus solution, you see errors similar to the following:
    File is currently in use. Try again later.
    Cannot save the file to this location.Files saved to the share are empty and 0KB in size.
  • PR 1125220: When you run a vmtoolsd query such as vmtoolsd –cmd “info-get guestinfo.ovfEnv”, the VMware Tools service might fail. This issue is known to occur on VMware Tools versions 9.0.1 and 9.0.5.
  • PR 1130590: While upgrading the VMware Tools in Windows 8 and Windows 8.1 virtual machines, the user is automatically logged out of the virtual machines.
  • PR 1162026: An error similar to the following might be displayed while updating an earlier version of VMware Tools to version 9.0.5 in a RHEL 6.2 (Red Hat Linux Enterprise) virtual machine using RPM (Red Hat Package Manager):
    Error: Package: kmod-vmware-tools-vsock-9.3.3.0-2.6.32.71.el6.x86_64.3.x86_64 (RHEL6-isv)
    Requires: vmware-tools-vsock-common = 9.0.1
    Installed: vmware-tools-vsock-common-9.0.5-1.el6.x86_64 (@/vmware-tools-vsock-common-9.0.5-1.el6.x86_64)
    vmware-tools-vsock-common = 9.0.5-1.el6
    Available: vmware-tools-vsock-common-8.6.10-1.el6.x86_64 (RHEL6-isv)
    vmware-tools-vsock-common = 8.6.10-1.el6
    Available: vmware-tools-vsock-common-9.0.1-3.x86_64 (RHEL6-isv)
    vmware-tools-vsock-common = 9.0.1-3

9.4.0 (ESXi 5.5 Patch 1)

This patch updates the tools-light VIB to resolve an issue where attempts to save Microsoft office files to a network share hosted by a virtual machine that is protected by VMware vShield Endpoint and an agentless anti-virus solution might fail with error messages similar to the following:
File is currently in use. Try again later. Cannot save the file to this location.
This issue is caused due to the interference in the scanning process while you attempt to save the file. As a result, you encounter the error messages and cannot save the files.

 

Leave a Reply

Your email address will not be published. Required fields are marked *

*