VMware 的文件导入 VirtualBox

VirtualBox and VMware's ovftool have a different idea of how a storage controller should be described. This prevents exporting a VM from, e.g. VMware Fusion, and then importing it into VirtualBox. However, this can be worked around.

Ovftool produces output like

  0
  SATA Controller
  sataController0
  3
  vmware.sata.ahci
  20

but VirtualBox wants a tag named Caption, not ElementName. It also wants ResourceSubType to be just 'AHCI'. See the code below

case ResourceType_OtherStorageDevice:        // 20       SATA controller
{
    /* 
        SATA Controller
        sataController0
        4
        20
        AHCI
        0
        0
     */
    if (    i.strCaption.startsWith("sataController", RTCString::CaseInsensitive)
         && !i.strResourceSubType.compare("AHCI", RTCString::CaseInsensitive)
       )
    {
        HardDiskController hdc;
        hdc.system = HardDiskController::SATA;
        hdc.idController = i.ulInstanceID;
        hdc.strControllerType = i.strResourceSubType;

        vsys.mapControllers[i.ulInstanceID] = hdc;
    }
    else
        throw OVFLogicError(N_("Error reading \"%s\": Host resource of type \"Other Storage Device (%d)\" is supported with SATA AHCI controllers only, line %d"),
                            m_strPath.c_str(),
                            ResourceType_OtherStorageDevice,
                            i.ulLineNumber);
    break;
}

If you modify the ovf file to make these changes, the import should succeed. After modfying it, be sure to update the sha1sum of the ovf file in the mf file.

 

就是修改.vof文件,对应配置,

增加sataController0

 修改值AHCI

另外,.mf文件里面的sha1值要修改下,下个软件来算下新的vof文件sha1值就可以了!不改的话,导入时校验sha1会失败.