Today I experienced the error shown in the title of this post while opening the VM console of some VMs. This short post will help you solve this issue on short and long term.
Today I stumbled upon an issue where I couldn’t power on a particular VM without triggering a PSOD (Exception 14) on the ESXi host the machine was registered on. This article describes the reason for the PSOD and how I solved it using PowerCLI.
Alot has been going on in my head about how I should transform my homelab from a simple physical box with just plain vSphere 5.5 on it and memory consuming applications like Microsoft Exchange and Lync to a nested ESXi environment where I can test new VMware features and technologies apposed to the Microsoft technologies I have seen for many years now.
Last weekend VMware announced that vSphere 5.5 was available for download and I guess everyone hurried themselves to the download section of the VMware website including me! 🙂
I didn’t have time to actually use the binaries until last tuesday and thought of myself it would be cool to add something extra to my blog; video recordings! So, here it is, my first video recording during my upgrade from vSphere 5.1 to 5.5.
While beginning to write, the session didn’t start yet. This is the first time I’m going to see Cormac Hogan live. I heard good things about him in a technical way. Next to him on stage will be Kyle Gleed, both Cormac and Kyle are from the Cloud Infrastructure Technical Marketing team.
This session will be about the new vSphere 5.5 features, including new features for storage.