Virtualisation from the trenches

Recent Posts

For those with NSX-v 6.4, they’d know the end of general support date was 16/01/2021, (just over a year from now). If you check the product lifecycle it now shows the end of general support is 16/01/2022.

Product Lifecycle Matrix

When using the Migration Assistant to Migrate from a Windows 5.5 vCenter to 6.5 VCSA, the migration assistant was failing to run on the Windows vCenter server.

It automatically saves the logs on the desktop. When viewing the logs, this part stood out:

2019-07-22T00:31:58.193Z ERROR upgrade.states.component_states vcIntegrity:CollectRequirements: Remote script failed with an error [InternalError()]
2019-07-22T00:31:58.193Z ERROR upgrade.states.component_states vcIntegrity:CollectRequirements: failed with internal error. For details take a look at CollectRequirements_com.vmware.vcIntegrity_2019_07_22_10_31.log.
2019-07-22T00:31:58.209Z WARNING wf.wf_processor State CollectRequirements com.vmware.vcIntegrity has failed.

During an upgrade from 5.5 to 6.5, update manager started to do the upgrade, but after the host rebooted, it would boot into the ESXi 6.5 installer, but then display About to install for 15 seconds, then flash an error message, and then go back to About to Install. Leaving it for a few hours didn’t make any difference, and I was unable to alt-F1 and log into the console, as when the error message flashed up, it would reset the login process.

Deploying vRNI 4.1 you might get an error: Insufficient capacity on each physical CPU.

Insufficient capacity on each physical CPU

Ovftool can be pretty awesome, but it can also be very difficult to use. I seem to have a love/hate relationship with it.

Here I will go over some common issues I have with the tool. I’ve only tested on the Windows version of ovftool.