Comments on: VMware ESX(i) 3.5 U4 released! http://www.yellow-bricks.com/2009/03/31/vmware-esxi-35-u4-released/ Building blocks for virtualization... Fri, 12 Mar 2010 14:11:13 +0000 http://wordpress.org/?v=2.9.2 hourly 1 By: judoman http://www.yellow-bricks.com/2009/03/31/vmware-esxi-35-u4-released/comment-page-1/#comment-2992 judoman Tue, 31 Mar 2009 23:40:55 +0000 http://www.yellow-bricks.com/?p=2676#comment-2992 FYI: The ESX 3.5 U4 update problem is fixed. If the E1G42ET driver is installed prior to U4, U4 will overwrite it with the older v1.0.0-82663 version, a version that does not support the E1G42ET. Furthermore, attempting to reapply the E1G42ET patch with "esxupdate update" or even "esxupdate --force update" does not work. Here's what we did to fix it: 1. rpm -qa|grep "igb" Output: VMware-esx-drivers-net-igb.350.1.0.0-82663 [This is the old driver that U4 installed] 2. rpm -e VMware-esx-drivers-net-igb.350.1.0.0-82663 [Uninstall the old driver] 3. mount the E1G42ET Driver CD: 'ESX 3.5 Driver CD for driver "igb" version 1.3.8.6.3': umount /dev/cdrom /mnt/cdrom 4. rpm -ivh /mnt/cdrom/VMupdate/RPMS/VMware-esx-drivers-net-ibg-350.1.3.8.6.3-i386.rpm [Install the new driver] 5. reboot Back on-line! Andre at VMware Support said that he'll write up a KB on this. Cheers, /j FYI: The ESX 3.5 U4 update problem is fixed. If the E1G42ET driver is installed prior to U4, U4 will overwrite it with the older v1.0.0-82663 version, a version that does not support the E1G42ET. Furthermore, attempting to reapply the E1G42ET patch with “esxupdate update” or even “esxupdate –force update” does not work.

Here’s what we did to fix it:
1. rpm -qa|grep “igb”
Output: VMware-esx-drivers-net-igb.350.1.0.0-82663
[This is the old driver that U4 installed]

2. rpm -e VMware-esx-drivers-net-igb.350.1.0.0-82663
[Uninstall the old driver]

3. mount the E1G42ET Driver CD: ‘ESX 3.5 Driver CD for driver “igb” version 1.3.8.6.3′: umount /dev/cdrom /mnt/cdrom

4. rpm -ivh /mnt/cdrom/VMupdate/RPMS/VMware-esx-drivers-net-ibg-350.1.3.8.6.3-i386.rpm
[Install the new driver]

5. reboot

Back on-line!

Andre at VMware Support said that he’ll write up a KB on this. Cheers,
/j

]]> By: judoman http://www.yellow-bricks.com/2009/03/31/vmware-esxi-35-u4-released/comment-page-1/#comment-2990 judoman Tue, 31 Mar 2009 21:34:42 +0000 http://www.yellow-bricks.com/?p=2676#comment-2990 Applying the U4 update will knock the newly HCL-certified Intel Gigabit ET Dual Port Server Adapter (E1G42ET) off-line. I've already burned several hours on this and am currently waiting on VMware support. If you have any of the new Intel third-gen NICs like the E1G42ET, I recommend you tread carefully so as not to waste time like me! Applying the U4 update will knock the newly HCL-certified Intel Gigabit ET Dual Port Server Adapter (E1G42ET) off-line. I’ve already burned several hours on this and am currently waiting on VMware support.

If you have any of the new Intel third-gen NICs like the E1G42ET, I recommend you tread carefully so as not to waste time like me!

]]> By: NiTRo http://www.yellow-bricks.com/2009/03/31/vmware-esxi-35-u4-released/comment-page-1/#comment-2986 NiTRo Tue, 31 Mar 2009 13:03:40 +0000 http://www.yellow-bricks.com/?p=2676#comment-2986 Hi Duncan, I'm curious about the LUN Queue depth throttling. Tell if i'm wrong : ESX received from the storage array a BUSY or QUEUE FULL status so the VMkernel throttles the LUN queue depth. What's the benefice effect of this algorithm ? Thanks. Hi Duncan, I’m curious about the LUN Queue depth throttling. Tell if i’m wrong : ESX received from the storage array a BUSY or QUEUE FULL status so the VMkernel throttles the LUN queue depth. What’s the benefice effect of this algorithm ?
Thanks.

]]>