Hi!
Run into a small issue today after we decided to create our new VMs in a VC/ESXi 7.0.3 env @ HW version 18 instead of the new default version 19;
new-vm -Version v18..... doesn't work since it complains about only v4,v7,v8,v9,v10,v11,v12,v13 and v14 supported
new-vm -HardwareVersion v18..... complains about virtual machine version is not compatible with the version of the host...(which is a 7.0.3 btw)
Is there a way to automate this for now?
Thanks in advance,
Per
You can create the VM with the default HW version, and then change the HW version with the API method.
See for example Re: Script to change Guest OS and version - VMware Technology Network VMTN
Blog: lucd.info Twitter: @LucD22 Co-author PowerCLI Reference
Ok, I've already tried that too, $vm.Extensiondata.UpgradeVM('vmx-18') gives "Virtual machine compatibility is already up-to-date"
which makes sense I guess since it's a version 19 VM...
Anything else I could try?
Ok, found another way - a bit dirty possibly - if I create the VM @ HW version 14 and the perform the $vm.Extensiondata.UpgradeVM('vmx-18') it works, would that cause any side effects?
Not that I know of.
That was in fact my other option, since I don't think you can downgrade the HW version
Blog: lucd.info Twitter: @LucD22 Co-author PowerCLI Reference
Ok thanks and I hope this gets possible in the future.
Normally they update the possible values with the next PowerCLI release.
Blog: lucd.info Twitter: @LucD22 Co-author PowerCLI Reference