Last week I reported a bug to VMware and yesterday I got their reply stating that this issue is solved in VMware ESX 3.5 Update 4 which they had just released. Damn those VMware guys are fast ;-)

Update 4 has build number 153875, requires a VMware Tools update and includes the following changes:

  • Expanded Support for Enhanced vmxnet Adapter
  • Enablement of Intel Xeon Processor 5500 Series
  • QLogic Fibre Channel Adapter Driver Update
  • Emulex Fibre Channel Adapter Driver Update
  • LSI megaraid_sas and mptscsi Storage Controller Driver Update
  • Newly Supported Guest Operating Systems
  • Newly Supported Management Agents
  • Newly Supported I/O Devices
    • SAS Controllers and SATA Controllers
    • Network Cards
    • Expanded Support for Intel E1000 network interface
    • Onboard Management Processors
    • Storage Arrays

More information can be found in the VMware ESX 3.5 Update 4 release notes

Thanks VMware for this quick fix :-)