If you encounter the error mentioned above while using VMware vLCM in conjunction with the “HPE OneView for vCenter Plugin,” there is a high likelihood that you can resolve the issue by executing a specific command directly on the ESXi host. To do this, you will need to access the ESXi shell or SSH into the host:

sut -set mode=AutoDeploy

This command sets the mode to “Auto Deploy,” which is essential for ensuring proper functionality with VMware vLCM and the HPE OneView integration.

To verify the current mode of your ESXi host, you can retrieve this information by executing the following command:

sut -exportconfig

This blog post is not about the L1 Terminal Fault (L1TF -> VMware KB56931) but about the HTAware Mitigation tool version 1.0.0.9 (HTAwareMitigation-1.0.0.9.zip) that seems to have issues when used on single hosts (instead of clusters) – here is the problem that I have observed.

You run the command:

Set-HTAwareMitigationConfig -VMhostName <hostname> -Enable

Followed by

Get-HTAwareMitigationConfig -VMhostName <hostname>

Get-HTAwareMitigationConfig not working on single host

 

As you might see the “Set-HTAwareMitigationConfig -VMhostname <hostname>” command doesn’t seem to do anything!

Continue reading

I recently wanted to make sure that my lab environment was on the latest VCSA version (Platform Service Controller and vCenter) so I went to the VAMI interface on my PSC and quickly discovered that there were no updates – that’s was strange because my PSC was at build 8217866 (build 6.7.0.10000) and according to the vSphere version list KB2143838 there has been released some newer versions Continue reading