Earlier this week, I was on a demonstration discussing the concept of a desired state with a particularly interesting customer. Ordinarily, most customers and prospects I talk with consider the concept of a desired state to be a pretty simple concept. Due to the tools we have in the marketplace today, most people consider the desired state somewhere between no active alerts and no phone calls from end users. But the concept is much more complicated than that. This prospect in particular was challenging me on the concept that not only is there no single desired state, but that there was also a desired state for every level of virtualization, and the only true way to assure performance was to find a desired state for both at the same time in real time. We had only been talking at that point on how to assure service performance while maximizing the efficiency of the hypervisor layer, when the prospect brought up Cisco UCS. He mentioned that, occasionally, he finds that performance degradation occurs on his fabric layer, but does not manifest itself as an alert in his vSphere environment. He then challenged me and asked, can VMTurbo not only control a hypervisor in a desired state, but also control in a desired state for Cisco UCS?