查看了網上的文章，自己做了一下實驗。
發覺導出ovf模板時，虛擬CDROM的選項要選【客戶端設備】，導入時才不會出事。
參考連接
Frustrated by the inability to redeploy a template I spent so long preparing, I broke open the OVA template and took a look inside. There were three files with different extensions,
- .ova - OVF descriptor, written in XML, which describes the hardware requirements
- .mf – contains SHA1 checksums of the .OVA and .VMDK
- .vmdk – the virtual hard disk for the virtual machine.
I immediately discarded the .mf. If you modify the .ova and don’t update the .mf, it’ll complain that the checksum is invalid. Removing this file seems to prevent vSphere from checking the checksums, which is useful, seeing as we want to poke around the .ova. After fiddling around inside the .ova, I stumbled across the following line…
<rasd:ResourceSubType>vmware.cdrom.iso</rasd:ResourceSubType>
Changing the above line, to read…
<rasd:ResourceSubType>vmware.cdrom.atapi</rasd:ResourceSubType>
…appears to have fixed my deployment issues. Perhaps changing the ‘CD Drive Device type’ in the virtual machine’s settings would’ve fixed it. But by that point, I had already exported the OVA and deleted the source virtual machine.
Hopefully someone will stumble across this one day, and it’ll save them a few hours!