vSphere 8 Update 3 landed with less fanfare than its major version bump, but the changes under the hood are substantial. After running it in a lab for several weeks and rolling it out to one production cluster, here's what actually matters for day-to-day operations.
DPU Offloading Gets Practical
The SmartNIC / DPU story has been slowly maturing since vSphere 7, and Update 3 is where it starts to feel production-ready. The vSphere Distributed Services Engine now supports NVMe-oF offloading on supported DPUs, which removes a significant chunk of storage I/O processing from the host CPU. In workloads with heavy east-west NFS traffic, we measured up to 18% lower host CPU utilisation with no change in VM density.
If you're running VMware vSAN ESA on Dell PowerEdge or HPE ProLiant servers with SmartNICs, this update is worth prioritising.
vMotion Latency Improvements
VMware quietly improved the pre-copy phase of vMotion by making it aware of memory access patterns. Hot pages are now mirrored earlier, reducing the stun time at the final switchover. In our testing with an Oracle DB VM sitting at 192 GB RAM with ~40% dirty pages, stun time dropped from ~450 ms to ~180 ms — well within the threshold most applications can tolerate.
# Check vMotion stun time after migration in the vmkernel log
grep "vmotion" /var/log/vmkernel.log | grep "total stun time"vCenter UI Refresh
The HTML5 client gets a long-overdue host summary redesign. The new hardware health widget consolidates sensor data that previously required three separate clicks. More importantly, the Hosts and Clusters tree now remembers your expansion state across sessions — a small quality-of-life fix that saves real time if you manage more than a handful of clusters.
What to Watch Out For
- Storage vMotion with vSAN ESA: There's a known issue (KB 96143) where simultaneous Storage vMotion operations on ESA clusters can trigger a resync storm if the destination datastore has less than 15% slack capacity. Stay patched and monitor your slack.
- VMTools 12.4: The bundled VMTools version changed its approach to balloon driver interactions. VMs with aggressive memory reservations may need a restart after tools upgrade.
Bottom Line
Update 3 is a solid, low-drama release. The DPU offloading and vMotion improvements alone justify the maintenance window if your hardware supports them. Plan for a VMTools refresh cycle after the host upgrade.