Welcome to the world where thousands of dangerous beasts are lurking in the shadowy nooks of every server room, in every rack. Every single one of them with a single mission - to make your life a living hell.
But wait, now you have a unique chance to recognize them before they attack you and effectively fight back thanks to the knowledge you’ll gain.
Just open the bestiary and begin revealing the secrets of this world...
A bloodcurdling beast with a desire for all your secrets. It sucks sensitive information from every hidden part of your environment just because it can. Empty shell is all that’s left.
VMware response to ‘L1 Terminal Fault - VMM’ (L1TF - VMM) Speculative- Execution vulnerability in Intel processors for vSphere: CVE-2018-3646
Panic sets in as this terrifying monster begins raging. You don’t stand a chance to escape its clutches. No one ever has. Everything you worked so hard to build is gone in a flash.
vCenter Server 6.0 Update 3 or 6.5 fails with the error: Panic: Win32 exception: Access Violation (0xc0000005).
Hiding in the shadows and will attack you when you least expect it. It will find you no matter how hard you try to hide. Definitely not someone you would want to play hide and seek with!
ESXi 6.5 host fails with PSOD when IPV6 is disabled.
It tears, bites, and furiously destroys your network connectivity. Troubleshooting after the attack of this KB nightmare can be one of the hardest things you’ll ever face.
A virtual machine loses network connectivity after vMotion
It’s horrific eyes lurking around the corner. If you see them, it's already too late. The beast enjoys the suffering of desperate mothers when it separates tem from the most important part of their lives.
”LINT1 motherboard interrupt“ error in an ESX/ESXi host.
This KB beast will burn the path to your final destination to ashes. You won’t find it again: it will fall into oblivion.
VMware High Availability cluster reports the error: Could not reach isolation address.
This monster attacks your sense of good and evil to tip the evil scale. It can drag you down to the darkest corners of the underworld.
NSX load balancer crashes due to high memory usage.
A signature burnt into your skin with a branding iron hurts so bad. Until the end of your miserable days, it will remind you that you became one of its slaves.
The virtual machine is assigned an invalid IP address after a reboot.
Eighty-five days of anxiety concluded with an execution awaits anyone who can’t defeat this demon.
ESXi host or virtual machine hangs after approximately 85 days.
Once you receive message from Mess Anger, take a deep breath and enjoy the moment... It can be your last...
ESXi 6.0 Update 2 host fails with a PSOD error mentioning Vmxnet3VMKDevRxWithLock.
This spectre comes without invitation with a burning blade which will melt any precious environment down in seconds.
VMware response to speculative execution security issues, CVE-2017-5753, CVE-2017-5715, CVE-2017-5754, and CVE-2018-3693.
It creeps in silence and enjoys a moment of surprise as it comes thrusting a sharp hook into an unsuspecting admin’s back.
Virtual machines with large disk size on ESXi 6.5 hosts might hang during I/O operations and keep issuing host based VSCSI resets.
Should the motherboard encounter this beast, it will cost you your life, at least…
"LINT1 NVIDIA Out of memory" error in the ESXi 6.x host.
Throws the toxic poison which causes slow and intermittent death to those who are attacked. Purple…. inferno!
ESXi host fails with intermittent NMI PSOD on HP ProLiant Gen8 servers.
When the clouds turn dark, huge magnetic nightmare arise and head to destroy everything that crosses their path.
Using small magnetic disks for vSAN might result in VM failures.
The most powerful beast in all the land. Those who met it talk about a touch of death, bitter cold, and a purple glare which covers everything in sight. Just a shimmering ray of purple light remains...