Skip to content

5.0

vSphere 5.0 and 5.1 End of Support 2016-08-24

vsphere-5Today, 5 years after the release vSphere 5.0 and vSphere 5.1, end of support for both products has been reached and enters the technical guidance phase starts.

If not are not aware of the EOS, I encourage you to use my VMware Product End Of Support Countdown to keep an eye on EOS dates (It also supports ics based calendar reminders).

Currently, the only fully supported versions are

  • vSphere 5.5
  • vSphere 6.0

Read More »vSphere 5.0 and 5.1 End of Support 2016-08-24

vSphere 5.0 & 5.1 End of Support soon - Upgrade your ESXi Hosts

hcl-60You might be aware that General Support for VMware vSphere 5.0 and 5.1 ends in about 4 weeks at August 24th. If not, I encourage you to use my VMware Product End Of Support Countdown to keep an eye on EOS dates (It also supports ics based calendar reminders).

If you are not running on ESXi 5.5 or ESXi 6.0, it is time to upgrade now. Prior to upgrade, please check VMware Compatibility Guide (HCL) to verify that your server is supported for the targeted vSphere release.

Read More »vSphere 5.0 & 5.1 End of Support soon - Upgrade your ESXi Hosts

vCenter Server 5.0/5.1 Update - CVE-2014-6593 (SKIP-TLS)

vcenter-server-logoVMware has published an update for vCenter Server 5.0 and 5.1 where CVE-2014-6593 (SKIP-TLS) has been fixed.

It was discovered that the SSL/TLS implementation in the JSSE component in OpenJDK failed to properly check whether the ChangeCipherSpec was received during the SSL/TLS connection handshake. A man-in-the-middle attacker could possibly use this flaw to force a connection to be established without encryption being enabled. The update has been already fixed in newer versions of vCenter Server (6.0a, 5.5 Update 2e). More information are available in VMSA-2015-0003.Read More »vCenter Server 5.0/5.1 Update - CVE-2014-6593 (SKIP-TLS)

VMware ESXi 5.x E1000 PSOD Issue

Even though the bug has been fixed I still see it to come up. ESXi 5.x has two issues that might cause the ESXi host to fail with a purple diagnostic screen. Both PSOD look very similiar:

KB2059053:

#PF Exception 14 in world wwww:WorldName IP 0xnnnnnnnn addr 0x0
PTEs:0xnnnnnnnn;0xnnnnnnnn;0x0;
0xnnnnnnnn:[0xnnnnnnnn]E1000PollRxRing@vmkernel#nover+ 0xdb9
0xnnnnnnnn:[0xnnnnnnnn]E1000DevRx@vmkernel#nover+0x18a

KB2079094:

#PF Exception 14 in world wwww:WorldName IP 0xnnnnnnnn addr 0x0
PTEs:0xnnnnnnnn;0xnnnnnnnn;0x0;
0xnnnnnnnn:[0xnnnnnnnn]E1000PollRxRing@vmkernel#nover+0xeb7
0xnnnnnnnn:[0xnnnnnnnn]E1000DevRx@vmkernel#nover+0x18a
[...]
0xnnnnnnnn:[0xnnnnnnnn]Net_AcceptRxList@vmkernel#nover+0x157

Read More »VMware ESXi 5.x E1000 PSOD Issue

vSphere Health Check Report with ESXi 5.x (Minimum Permissions)

If you are using VMware vSphere Health Check Report v5.0.2 by William Lam in your environment you might get incomplete reports after upgrading to vSphere 5.x. This applies only when you use the script with minimal privileges set. The report is broken (missing VM and Host information) and running the script with --debug 1 throws an error message.Read More »vSphere Health Check Report with ESXi 5.x (Minimum Permissions)

Homelab Upgrade – 16GB Memory with HP N40L Microserver

There have been many rumors about the N40L supporting 8GB modules which enables the server to use up to 16GB of memory. This would be a great enhancement, especially with the new vSphere 5.1 where many appliances require more physical memory.  First of all, the 8GB modules are not supported by HP so upgrade at your own risk.

I picked together all the modules that have been successfully tested with the HP N40L MicroServer:Read More »Homelab Upgrade – 16GB Memory with HP N40L Microserver