Today I did something horrible. I yet again noticed that I bought the wrong CPU’s (basically I bought Xeon DP’s with four cores). Those have apparently a feature called SSSE3, which makes vMotion with our old Xeon DP’s (dual cores) fail before even trying. But as we had a cooling outage today (basically ‘cause it broke), I needed to turn off some ESX servers. Thus leaving me with the new ones and one of the old ones. * yuck* ...
Well, I’m back at work after three weeks of vacation (some pictures to follow) and the provider hosting our disaster datacenter had their annual (or is it monthly now?) SAN maintainance, so we shut down everything over there by 9:00 am. After things were back up around 5pm, I booted the ESX hosts, however the VMs we’re all displaying the alert state - as if either the VMs had an HA event or we’re using to much CPU time. It didn’t matter whether or not the VM was running or not, the state persisted. ...
Remember my last post about cpu masking ? Well, turns out that you can do it to a “template”. The only point you don’t need to do, is to mark the VM as a " template". You still can clone it and move it around and all that other stuff, but the good part is, that the cloned VM keeps the cpu mask set to the " template" 🤷 ...