Profile Name
| ESXi-6.5.0-20170702001-standard |
Build
|
For build information, see KB 2149910.
|
Vendor
|
VMware, Inc.
|
Release Date
|
July 27, 2017
|
Acceptance Level
|
PartnerSupported
|
Affected Hardware
|
N/A
|
Affected Software
|
N/A
|
Affected VIBs
|
|
PRs Fixed
| 1226067, 1751189, 1759620, 1760761, 1765298, 1765391, 1768396, 1776389, 1779570, 1780524, 1782442, 1782479, 1783152, 1783750, 1784077, 1784393, 1792472, 1793824, 1796643, 1796948, 1798656, 1799704, 1800745, 1800903, 1805207, 1805383, 1807033, 1808089, 1808532, 1812751, 1818459, 1818649, 1818887, 1820504, 1821649, 1821937, 1822996, 1823028, 1824285, 1825994, 1827738, 1829739, 1831235, 1831499, 1832222, 1832242, 1832318, 1832940, 1835341, 1836212, 1838786, 1839087, 1839380, 1840639, 1842944, 1843621, 1843743, 1846540, 1850988, 1851787, 1852419, 1859128, 1859906, 1863888, 1868876, 1869230, 1876149, 1876880, 1876972, 1881001, 1812407, 1819968, 1824983, 1832972, 1849883, 1791204, 1812539, 1760451, 1770770, 1829440, 1836397, 1846297 |
Related CVE numbers
| N/A |
This patch updates the esx-base, esx-tboot, vsan, vsanhealth, vmkusb, misc-drivers, ne1000, ixgben, usbcore-usb, vmkata, qlnativefc, vmw-ahci, sata-ahci, lsu-ho-hosa-plugin, nvme, vmware-esx-esxcli-nvme-plugin, i40en, lsu-lsi-lsi-mr3-plugin, lsu-lsi-lsi-msgpt3-plugin, lsu-lsi-megaraid-sas-plugin, lsu-lsi-mpt2sas-plugin, igbn, ntg3, pvscsi, esx-ui VIBs to resolve the following issues:
cpu.system
is incorrectly calculated for a virtual machine. The value of the counter is always 0 (zero) and never changes, which makes it impossible to do any kind of data analysis on it.Cannot execute upgrade script on host
error.jumpstart[XXXX]: execution of '--plugin-dir /usr/lib/vmware/esxcli/int/ systemInternal vmswapcleanup cleanup' failed : Host Local Swap Location has not been enabled
You can copy all the VMware Tools data into its own ramdisk. As a result, the data can be read from the flash media only once per boot. All other reads will go to the ramdisk. vCenter Server Agent (vpxa) accesses this data through the /vmimages
directory which has symlinks that point to productLocker.
To activate this feature, follow the steps:
esxcli system settings advanced set -o /UserVars/ToolsRamdisk -i 1
esxcli software profile get
command output after execution of a esxcli software profile update
command. Also software profile name is not marked Updated in esxcli software profile get
command output after an ISO upgrade.guestinfo.toolsInstallErrCode
is set to 1603. The variable is not cleared by rebooting the Guest OS.Operation timed out
error, if the host uses only IPv4 address, and the domain has IPv6 or mixed IPv4 and IPv4 setup.ifOutErrors
and ifOutOctets
counters, when they should be different.@BlueScreen: #PF Exception 14 in world 75561:Default-drai IP 0xxxxxxxxxxxxaddr 0xxxxxxxxxxxx
PTEs:0xXXXXXXXXXXXXX;0xYYYYYYYYYYYYYY;0xZZZZZZZZZZZZZZ;0x0;
[0xxxxxxxxxxxx]SPLockIRQWork@vmkernel#nover+0x26 stack: 0xxxxxxxxxxxx
[0xxxxxxxxxxxx]VMKStatsDrainWorldLoop@vmkernel#nover+0x90 stack: 0x17
MXUserAllocSerialNumber: too many locks
error. If the workaround from KB article 2149941 has been used, please re-enable Guest RPC communication over vSockets by removing the line: guest_rpc.rpci.usevsocket = "FALSE"
numa.nodeAffinity
vmx option might not be honored. The Guest OS might see a performance degradation because of this. Virtual machines configured with latency sensitivity set to high or with a passtrhough device are typically preallocated.Guest introspection not ready
warning in the vCenter Server UI.rhttpproxy
port for /cgi-bin
has a value different from 8303.0x439116e1aeb0:[0x418004878a9c]LACPScheduler@#+0x3c stack: 0x417fcfa00040
0x439116e1aed0:[0x418003df5a26]Net_TeamScheduler@vmkernel#nover+0x7a stack: 0x43070000003c
0x439116e1af30:[0x4180044f5004]TeamES_Output@#+0x410 stack: 0x4302c435d958
0x439116e1afb0:[0x4180044e27a7]EtherswitchPortDispatch@#+0x633 stack: 0x0
Spin count exceeded (refCount) - possible deadlock with PCPU
error, when you reboot the ESXi host under the following conditions:vmware.log
will show similar messages to:
2017-03-02T02:03:24.921Z| vmx| I125: GuestRpc: Too many RPCI vsocket channels opened.
2017-03-02T02:03:24.921Z| vmx| E105: PANIC: ASSERT bora/lib/asyncsocket/asyncsocket.c:5217
2017-03-02T02:03:28.920Z| vmx| W115: A core file is available in "/vmfs/volumes/515c94fa-d9ff4c34-ecd3-001b210c52a3/h8-ubuntu12.04x64/vmx-debug-zdump.001"
2017-03-02T02:03:28.921Z| mks| W115: Panic in progress... ungrabbing
Security.PasswordQualityControl
is observed, when the PAM password setting in the PAM password profile is different to the advanced configuration option Security.PasswordQualityControl
. Because the advanced configuration option Security.PasswordQualityControl
is unavailable for the host profile in this release, use the Requisite
option in the Password PAM Configuration for changing password policy instead.Couldn't enable keep alive
warnings occur during VMware NSX and partner solutions communication through a VMCI socket (vsock). The VMkernel log now omits these repeated warnings because they can be safely ignored.Relocating modules and starting up the kernel...
TBOOT: **************TBOOT ******************
TBOOT: TPM family: 1.2
The source detected that the destination failed to resume
message. The VMkernel log from the ESXi host contains the message D: Migration cleanup initiated, the VMX has exited unexpectedly. Check the VMX log for more details
.ConfigSpec
that specifies the disk backing file using the generic vim.vm.Device.VirtualDevice.FileBackingInfo
class, instead of the disk type specific backing class, such as vim.vm.Device.VirtualDisk.FlatVer2BackingInfo
, vim.vm.Device.VirtualDisk.SeSparseBackingInfo
./Net/NetPktSlabFreePercentThreshold
because of the wrong default value. This problem is resolved by changing the default value./Power/PerfBias
advanced configuration option is not available. Any attempt to set it to a value returns an error.Syslog.global.logDirUnique
option, this option appears grayed out, and cannot be modified.stale NFS file handle
errors, because of the way virtual disk descriptors are written to NFS datastores.PCPU <cpu-num></cpu-num>didn't have a heartbeat for <seconds></seconds>seconds; *may* be locked up.
.upit
) on virtual volume datastores can impact its performance. The .upit
directory is not applicable to virtual volume datastores. The change disables the lookup to the .upit
directory.ConfigSpec
includes an extraConfig
option with an integer valueUnexpected exception during reconfigure: (vim.vm.ConfigSpec) { <snip></snip>} Type Mismatch: expected: N5Vmomi9PrimitiveISsEE, found: N5Vmomi9PrimitiveIiEE
.
pcidrv_alloc_resource
failure. The issue is caused because the system cannot recognize or reserve resources for the USB device.IMM
or iLO
command, the transaction on the USB network device is lost.xHCI Host Controller USB 2.0 Control Transfer may cause IN Data to be dropped
and xHCI controller Parity Error response bit set to avoid parity error on poison packet
, are reported in ESXi VMkernel logs.esxcli
command might give a wrong link status on Intel 82574L based NICs (Intel Gigabit Desktop CT/CT2). You must manually restart the NIC to get the actual link status./var/log/vmkernel
log file you see entries similar to:
YYYY-MM-DDTHH:MM:SS.833Z cpu58:34255)qlnativefc: vmhba2(5:0.0): Recieved a PUREX IOCB woh oo
YYYY-MM-DDTHH:MM:SS.833Z cpu58:34255)qlnativefc: vmhba2(5:0.0): Recieved the PUREX IOCB.
YYYY-MM-DDTHH:MM:SS.833Z cpu58:33674)qlnativefc: vmhba2(5:0.0): sizeof(struct rdp_rsp_payload) = 0x88
YYYY-MM-DDTHH:MM:SS.833Z cpu58:33674qlnativefc: vmhba2(5:0.0): transceiver_codes[0] = 0x3
YYYY-MM-DDTHH:MM:SS.833Z cpu58:33674)qlnativefc: vmhba2(5:0.0): transceiver_codes[0,1] = 0x3, 0x40
YYYY-MM-DDTHH:MM:SS.833Z cpu58:33674)qlnativefc: vmhba2(5:0.0): Stats Mailbox successful.
YYYY-MM-DDTHH:MM:SS.833Z cpu58:33674)qlnativefc: vmhba2(5:0.0): Sending the Response to the RDP packet
YYYY-MM-DDTHH:MM:SS.833Z cpu58:33674 0 1 2 3 4 5 6 7 8 9 Ah Bh Ch Dh Eh Fh
YYYY-MM-DDTHH:MM:SS.833Z cpu58:33674)--------------------------------------------------------------
YYYY-MM-DDTHH:MM:SS.833Z cpu58:33674) 53 01 00 00 00 00 00 00 00 00 04 00 01 00 00 10
YYYY-MM-DDTHH:MM:SS.833Z cpu58:33674) c0 1d 13 00 00 00 18 00 01 fc ff 00 00 00 00 20
YYYY-MM-DDTHH:MM:SS.833Z cpu58:33674) 00 00 00 00 88 00 00 00 b0 d6 97 3c 01 00 00 00
YYYY-MM-DDTHH:MM:SS.833Z cpu58:33674) 0 1 2 3 4 5 6 7 8 9 Ah Bh Ch Dh Eh Fh
YYYY-MM-DDTHH:MM:SS.833Z cpu58:33674)--------------------------------------------------------------
YYYY-MM-DDTHH:MM:SS.833Z cpu58:33674) 02 00 00 00 00 00 00 80 00 00 00 01 00 00 00 04
YYYY-MM-DDTHH:MM:SS.833Z cpu58:33674) 18 00 00 00 00 01 00 00 00 00 00 0c 1e 94 86 08
YYYY-MM-DDTHH:MM:SS.833Z cpu58:33674) 0e 81 13 ec 0e 81 00 51 00 01 00 01 00 00 00 04
YYYY-MM-DDTHH:MM:SS.833Z cpu58:33674) 2c 00 04 00 00 01 00 02 00 00 00 1c 00 00 00 01
YYYY-MM-DDTHH:MM:SS.833Z cpu58:33674) 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
YYYY-MM-DDTHH:MM:SS.833Z cpu58:33674) 00 00 00 00 40 00 00 00 00 01 00 03 00 00 00 10
YYYY-MM-DDTHH:MM:SS.833Z cpu58:33674)50 01 43 80 23 18 a8 89 50 01 43 80 23 18 a8 88
YYYY-MM-DDTHH:MM:SS.833Z cpu58:33674) 00 01 00 03 00 00 00 10 10 00 50 eb 1a da a1 8f
This is a firmware problem and it is caused when Read Diagnostic Parameters (RDP) between the Fibre Channel (FC) Switch and the Hot Bus Adapter (HDA) fails 2048 times. The HBA adapter stops responding and because of this the virtual machine and/or the ESXi host might fail. By default, the RDP routine is initiated by the FC Switch and occurs once every hour, resulting in a reaching the 2048 limit in approximately 85 days.
esxcli storage core device set -l locator -d <device id>
esxcli storage core device set -l error -d <device id>
esxcli storage core device set -l off -d <device id>,
esxcli storage core device set -l locator -d <device id>
esxcli storage core device set -l error -d <device id>
esxcli storage core device set -l off -d <device id>
esxcli storage core device physical get -d <device id>
ntg3
driver might experience unexpected loss of connectivity. The network connection cannot be restored until you reboot the ESXi host. The devices affected are Broadcom NetXtreme I 5717, 5718, 5719, 5720, 5725 and 5727 Ethernet Adapters. The problem is related to certain malformed TSO packets sent by VMs such as (but not limited to) F5 BIG-IP Virtual Appliances. The ntg3
driver, version 4.1.2.0 resolves this problem.