Problema con importacion de .ovf

[josecullera]

Hola buenas, hace un par de dias formate el portatil y me metí en un disco duro la misma importacion de maquinas virtuales dos veces por si alguna de las dos fallaba, después de haber formateado y haber cambiado a windows 8.1 pro ya que antes tenia 8.1 instalé los drivers de wifi y demás, luego empecé a instalar virtualbox porque es donde hago trabajos de clase, una vez instalado extraigo los .ovf a mi portatil y al intentar importarlos me da un error:

Fallo al importar el servicio virtualizado C:/Users/Josecullera/Desktop/ee.rar.ova.

Internal inconsistency looking up disk image 'Servicio virtualizado («Appliance»)-disk16.vmdk'. Check compliance OVA package structure and file names references in the section <References> in the OVF file..

Código Resultado: E_FAIL (0x80004005)
Componente: ApplianceWrap
Interfaz: IAppliance {8398f026-4add-4474-5bc3-2f9f2140b23e}

Me han dicho que le ponga extension .rar y que lo extraiga, lo he echo y me aparecen varios archivos .vmdk, he intentado de todo, ayer estuve toda la noche hasta las 6 de la mañana intentando ya que si no consigo arreglarlo perderé el curso, siento no saber inglés, gracias de antemano.

[mpack]

"Internal inconstency?" I'm afraid that error message is too vague for me to decipher what it really means.

I'm having to rely in Google Translate since I don't read Spanish. Are you saying that you exported your VMs prior to upgrading your host OS? It's too late now, but for future reference the best way to back up a VM is simply to copy the VM folder to secondary storage. You can then copy it back on the new host and use Machine|Add... to register it.

There seems to be some confusion as well: an OVF is a text file, renaming it to .rar would not be a good idea. On the other hand an OVA is a tar.gz (a.k.a. .tgz) archive, if you renamed it to .rar that would still be wrong, but your archiving tool is probably smart enough to work out what the file really is.

If you unpack the OVA you get an OVF and one or more VMDKs, and maybe a manifest. The VMDKs are not directly usable in a VM (being compressed), but you can unpack them using "VBoxManage clonehd <vmdk name> <vdi name> --Format VDI". You should then be able to construct a VM around the unpacked VDI.

[josecullera]

"Internal inconstency?" I'm afraid that error message is too vague for me to decipher what it really means.

I'm having to rely in Google Translate since I don't read Spanish. Are you saying that you exported your VMs prior to upgrading your host OS? It's too late now, but for future reference the best way to back up a VM is simply to copy the VM folder to secondary storage. You can then copy it back on the new host and use Machine|Add... to register it.

There seems to be some confusion as well: an OVF is a text file, renaming it to .rar would not be a good idea. On the other hand an OVA is a tar.gz (a.k.a. .tgz) archive, if you renamed it to .rar that would still be wrong, but your archiving tool is probably smart enough to work out what the file really is.

If you unpack the OVA you get an OVF and one or more VMDKs, and maybe a manifest. The VMDKs are not directly usable in a VM (being compressed), but you can unpack them using "VBoxManage clonehd <vmdk name> <vdi name> --Format VDI". You should then be able to construct a VM around the unpacked VDI.

Thank you for answer
Ok I try speack english.
more o less I understand what you said.

as it could create or import virtual machines now ? extensions have VMDK or OVF

[mpack]

as it could create or import virtual machines now ? extensions have VMDK or OVF

Are you asking me to repeat how to create a VM from those two files?

The standard way is to use File|Import... and choose the OVF file when asked.

If that continues to fail then you need to use VBoxManage to convert the VMDK, as I mentioned before.