For more information on earlier updates, see my articles:

• Storage Fixes in VMware ESX Server 3.5 Update 2
• Storage Changes in VMware ESX 3.5 Update 3

Expanded Support for Enhanced vmxnet Adapter

Not specifically a storage change, but the enhanced vmxnet adapter introduced back in the original release of ESX 3.5 now works with most versions of Windows Server 2003 and XP Pro. Look for improved performance when using guest-side SMB and NFS as well as the guest iSCSI initiator. Note that you cannot select this driver when configuring non-Enterprise Edition machines; you have to select Windows Server 2003 Enterprise Edition (64-bit) regardless of which version of Server 2003 you are using.

Expanded SAS and SATA Controller Support

If you’d like to install ESX on a server equipped with a PMC 8011, Intel ICH9 or ICH10, CERC 6/I SATA/SAS Integrated RAID Controller, or HP Smart Array P700m Controller, you’ll find happiness in Update 4.

The Intel controllers are especially important, as we’re seeing them used more and more and this driver is more full-featured than the earlier Broadcom HT 1000 and Intel ICH7 drivers. The Intel ICH9/ICH10 is a dual-mode (IDE/ATA and AHCI/SATA) driver, supports SATA hard drives, SSDs, and optical drives, and now enables VMFS support when in AHCI/SATA mode. It’s not clear whether VMware actually supports VMFS datastores on ICH9/10 SATA, but it says it works. Anyone want to try it out? One thing is certain: You can’t use SATA drives in a shared/clustered environment because SATA does not include reservations. See this tech note and especially this question:

Earlier, it was mentioned that we can create VMFS if we use AHCI/SATA mode. If so, why did VMware not claim VMFS support when using SATA controller running in AHCI/SATA mode?

VMware might decide to add support in the near future. There is no strong need to have VMFS support on a SATA drive, because native SATA protocol does not support reserve/release. Reserve/release is needed if VMFS is used as clustered file system in a shared disk environment.

PXE Boot Support

Rich at VM/ETC points out that Update 4 includes experimental PXE boot support for ESX and ESXi. As he notes, this has major implications for cloud computing platforms, since it means that ESX servers can boot guests without local storage at all. Very interesting! Let’s bet that Update 5 (expected in June or July) will include this as a supported option.

Updated QLogic, Emulex, and LSI Drivers

Like most ESX updates, this one included updated Fibre Channel drivers.

• The QLogic Fibre Channel Adapter driver and firmware (versions 7.08-vm66 and 4.04.06, respectively) include bug fixes and enhanced NPIV support.
• On the Emulex side, driver version 7.4.0.40 supports the company’s HBAnyware 4.0 management software.
• Users of SAS and SCSI LSI MegaRAIDs will find driver version 3.19vmw (megaraid_sas) and 2.6.48.18 vmw (mptscsi) which improves performance and enhances event handling capabilities.

Expanded Sun Storage Array Support

All you StorageTek loyalists out there will be happy to see support for Sun’s low-end StorageTek 2530 SAS array as well as the modular 6580 and 6780 Fibre Channel arrays. It looks like just about every model in Sun’s current storage lineup is now supported in ESX.

Expanded Network Card Support

Support for Gigabit cards is greatly expanded, including HP’s quad-port NC375i and dual-port NC362i and NC360m, Intel’s Gigabit CT and 82574L, and NetXtreme’s BCM5722, BCM5755, BCM5755M, and BCM5756. Intel’s widely-used 10-gig 82598EB cards are now supported as well.

Tweaks and Fixes

Looking through the release notes, a few storage-related tweaks and fixes stand out:

1. WMware can optionally automatically throttle back the queue depth when congestion is encountered. See Controlling LUN queue depth throttling in VMware ESX for 3PAR Storage Arrays for more information.
2. VMklinux module heap size can now be adjusted as LUN queue-depth values are increased. Since tuning LUN queue depths is one common trick of the storage trade to improve performance, especially in queue-stingy systems like ESX, this is welcome news. But call VMware support before you monkey with it!
3. An RDM-related issue where SCSI inquiry data over 36 bytes was truncated or corrupted (for example when using Microsoft VSS and NetApp SnapDrive) has been resolved.

Well, that’s all folks. I suggest you all read the release notes for yourself, and please leave a comment if you see an error in what I wrote here or have something to add!

© sfoskett for Stephen Foskett, Pack Rat, 2009. | Storage Changes in VMware ESX 3.5 Update 4
This post was categorized as Enterprise storage, Gestalt IT, Virtual Storage. Each of my categories has its own feed if you'd like to filter out or focus on posts like this.

For more information on Update 2, see my article, Storage Fixes in VMware ESX Server 3.5 Update 2.

Update 3 is not as important from a storage perspective, but there are some goodies in there:

• New VMDK recovery tool (nifty!)
• Storage tweaks like fixed multipathing on IBM SVC, interrupt coalescing on QLogic 4 Gb FC HBAs, and some bug fixes
• Expanded support for SATA (but not for VMFS), SAS, and some Broadcom NICs (but still no TOE)

Read on for more details!

VMDK Recovery Tool

ESX users with Update 3 get a nifty new script for deeper inspection of disk image files on VMFS. Although I haven’t had a chance to try it out yet, it appears to be related to VCB, in that it identifies which disk blocks make up a VMDK. But the VMDK Recovery script (which runs in Service Console on ESX – sorry, ESXi!) allows you to copy these blocks to a new file.

What good is this? Well, it could certainly be used to recover VMDK files from corrupted VMFS datastores, and could serve as an undelete feature as well. And as Rich Brambley points out on VM/ETC, it could be the basis for some nifty scripted backup and restore operations as well. I’m looking forward to seeing what happens with this, but it’s definitely a minor addition.

Storage Tweaks

Update 3 includes some minor tweaks and bug fixes in storage:

• ESX used to only support most-recently used (MRU) multipathing with IBM’s SAN Volume Controller storage virtualization platform, but Update 3 allows fixed policies to be used as well.
• The VMkernel iSCSI driver gets two new advanced configuration options (Disk.UseLunReset and Disk.UseDeviceReset) to control whether multipath failover will issue a LUN reset or target reset.
• SCSI sense codes are now included in /var/log/vmkernel by default.  This should assist in deep troubleshooting of storage problems.
• The lengthy iSCSI target discovery process that used to happen whenever a discovery address was added has been removed, speeding up iSCSI storage configuration.
• Users of QLogic 4 Gb Fibre Channel HBAs will now get updated firmware and a new performance feature called interrupt coalescing. As it sounds, IC will combine interrupts from multiple I/Os, improving overall performance by reducing the number of interrupts the CPU has to handle.

Note that VMware ESX 3.5 Update 3 still doesn’t really make maximal use of 10 Gb Ethernet. Besides the lack of TCP offload engine (TOE) support, the company still doesn’t make any speed claims when people step up to faster NICs. The Known Issues list specifically says it’s for connectivity, not performance. At least the QLogic iSCSI HBA support is pretty good.

[ad#banner]

© sfoskett for Stephen Foskett, Pack Rat, 2008. | Storage Changes in VMware ESX 3.5 Update 3
This post was categorized as Enterprise storage, Virtual Storage. Each of my categories has its own feed if you'd like to filter out or focus on posts like this.