I have finally completed my Packer Build for Windows Server using the vmware-iso plugin which creates templates in VMware Workstation. However, I found an issue when trying to use the generated ova or ovf file. This post will detail the importance of keeping software up to date!
This post was written using the following versions:
- Packer v1.8.6
- vmware-iso plugin v1.0.7
- VMware Open Virtualization Format Tool v4.4.3
- VMware Workstation v17.01
I was finishing my Packer builds for VMware Workstation and successfully created and tested Windows Server 2016 and 2019. However, I noticed a problem after the OVA or OVF was successfully created. The template imports successfully:
Nonetheless on booting the VM the following is shown:
and then the VM goes into the EFI Boot Manager:
The VM will simply not boot correctly.
After investigation, I stumbled upon the issue with the imported VM. Looking at the VM Settings and then the General Settings I saw the Guest operating system was set to Other/Other:
This should be set to Microsoft Windows/Windows Server 2022:
Now the VM boots correctly - but why?
This is ultimately a tale of keeping your software up to date. It turns out I was running v4.4.3 of the OVF Tool. Upon further research I found out v4.6.0 was available. As soon as I installed the new version and re-ran the Packer build importing the OVA worked correctly:
Note: OVF Tool 4.5 for vSphere 8.0 is here at this location, not in the drop-down menu.
Not sure why the drop-down can’t have the latest version in it.
I read the release notes for OVF Tool and could not see the details of what Operating Systems it supports for the metadata of the OS Config. Maybe VMware could incorporate that.
Anyway, a lesson in keeping your software up to date!