Sangfor can import virtual machines in only 2 formats: OVA and VMA. The VMA is not Proxmox's VMA. It is Sangfor's VMA.
 |
| Importing a VMA file produced by Proxmox. FAIL. |
Not surprising. Sangfor's documentation ("SANGFOR_HCI_v5.2_User Manual-0308.pdf", page 50) did say, "The following types of VM files can be imported onto Sangfor HCI platform: OVA files exported from VMware virtualization platform, VMA files exported from other Sangfor HCI platforms."
Got to use VMware then... here's the plan...
 |
| An overview of the steps. |
 |
| Download and install "VMware vCenter Converter Standalone" in the Hyper-V server. |
(Note: The list of screenshots here is a representation of the process. I forgot to take screenshots in some parts, and I have to repeat the process. That's why the timestamps in the pictures may look funny.)
 |
| Launch "VMware vCenter Converter Standalone". |
 |
| Hyper-V VM successfully converted to VMware VM. |
 |
| Making sure that the converted Hyper-V VM can boot in VMware ESXi. |
 |
| Shut down the VM so that it can be exported. |
 |
| Exporting the VM from ESXi. |
 |
| Download and instal "OVF Tool" from VMware. |
 |
Convert OVF to OVA. Actual command:
"C:\Program Files\VMware\VMware OVF Tool\ovftool.exe" "C:\Share\HV-VM1\HV-VM1.ovf" "C:\Share\HV-VM1\HV-VM1.ova" |
 |
| Import the OVA file into Sangfor. |
 |
| Importing OVA file into Sangfor completed. |
 |
| Some details about the imported VM. |
 |
| The imported VM can boot. |
 |
| Still have to manually set the IP address as emulated network hardware/driver changed from "Hyper-V Network Adapter" to "Realtek". |
