Yeah, we should all switch to that piece of software that doesn't have any bugs.
Oh, wait.. There is none. Correct me if I'm wrong.
For what it's worth, I have 2 clusters running 5.5 U3 right now and (knock on wood) I have not had the issue or been able to produce the issue. We have CommVault running daily in the environment. I ran a bunch of tests yesterday to produce the issue and see where my environment stands and the results are the following:
On a test VM:
Test 1 – Normal snapshot with out of date VMWare Tools – No crash
Test 2 – Quiesced snapshot with out of date VMWare Tools – No crash
Test 3 – Normal snapshot with updated VMWare Tools – No crash
Test 4 – Quiesced snapshot with updated VMWare Tools – No crash
My VM's live in the root of their respective datastores which seems to be a mitigating factor in some way (not always according to this thread). I also spot checked a few of my guest's vmware.log files greping for some key phrases in the KB that was released and everything came back clean. I heard a lot of buzz about the utilization of Shadow Copy playing a factor which is why I ran tests with older VMWare Tools and the latest VMWare Tools.
I honestly don't know for sure what is preventing me from being susceptible, I just figured I would post my tests and findings.
I have faced same kind of errors in our environment
Please refer the KB published from Vmware.
This issues occurs due to a segmentation fault when changing the snapshot tree data-structure.
ResolutionThis is a known issue affecting VMware ESXi 5.5 Update 3 hosts.
To work around this issue preform one of these options:
- Downgrade the ESXi host(s) to a previous version. For more information, see Reverting to a previous version of ESXi (1033604).
- Consolidate the snapshot(s) with the virtual machine powered off.
- For larger environments where reverting all hosts is not feasible:
- Revert a subset of the ESXi hosts to a previous version. For more information, see Reverting to a previous version of ESXi (1033604).
- Migrate critical virtual machines to the downgraded hosts.
- Create DRS Affinity rules to keep the virtual machines from migrating to the affected ESXi hosts. For more information see the Using DRS Affinity Rules section of the vSphere Resource Management guide.
- Disable non-critical virtual machines from any backup solutions.
A major issue for the environment, where they Snapshot Based Backups.
I dont recommend for the environment with VDP/Veem/TSM4VE.
Regarding the mention of TSM, it works without issue if you are using storage-level snapshots and not VMware snapshots.
Calling this a "bug" is an insult to insects everywhere. This is a catastrophic failure of epic proportions.
We are at the start of upgrading / reinstalling our hosts and 1 has been outfitted with the VMware-ESXi-5.5.0-Update3-3029944-HP-5188.8.131.52-Sep2015.iso passed thursday.
We use Veeam as backup program and i havent seen 1 vm crash on that host as mentioned by several in this post.
We use CBT.
Storage Lefthand and VSA.
For what it's worth,
we're running 6 hosts ESXi 5.5 update 3 (3029944) since the updates became available.
100 VM's, backed nightly using Veeam & CBT. Mostly 2008R2 and 2012R2-servers.
VM's stored in separate folders on datastores.
Storage on HP Lefthand / iSCSI.
If it is of any relevance, our vCenter is rebooted weekly.
No issues what so ever with snapshots or backup so far.
Why on earth is VMware not informing its customers of this issue directly? I stumbled on it in somebody's blog site. Communication is the key!
I manually removed snap from a VM & then did consolidation no issues found.
5.5 u3 & linux 6.7 vm
I have hundreds of VMs backed up nightly by Avamar and only see it on the same 8-10 guests each night. However, there is nothing different about those guests compared to others. Definitely not every single VM affected.
Known Issue :
ESXi550-201510401-BG (ESXi5.5 Update 3a) is released to address Snapshot issue of Update 3.
"This patch updates the esx-base VIB to resolve an issue where snapshot consolidation or deletion results in the virtual machines running on VMware ESXi 5.5 Update 3 hosts to fail with the error: Unexpected signal: 11 "
I would suggest Install said patch and upgrade to UPDATE 3a.