Thank you so much for posting this! It was just what I needed to finish this project!
Thanks for the terrific article Bipin.
I have a question regarding the virtual CPU section though.
Is there any best practice recommendation regarding whether to use "virtual sockets" or "cores per socket"?
For example would it be best to not specify any more virtual sockets than the host machine genuinely has?
On increasing disk, add a new virtual disk in multiples of 300GB e.g 300/600/900, to align with Prime Infrastructure's (PI) OVA size:
Do not increase the size of an existing disk, PI will _not_ recognize the increased size of an existing disk. Also, if you have increased the existing disk and have rebooted the PI VM, do not take the increased size away, it will cause disk signature to be corrupted and will require a tedious disk recovery or re-deployment of OVA.
vSphere client will restrict you to the possible max values for virtual sockets<-> vCPUs, it won't let you make impossible configuration.