Hi Shahar,
I'm trying to import some .ova images from VMWare that have been
copied to
> a node. In both cases they fail with the error:
>
> "Conversion of VM from exteral enironment failed: copy-disk stream closed
> unexpectedly"
First you need to look at vdsm log to see more details why it failed.
Here is more detail:
2016-07-14 16:59:01,058 INFO
[org.ovirt.engine.core.vdsbroker.vdsbroker.ConvertOvaVDSCommand]
(pool-7-thread-10) [49ba3bae] START, ConvertOvaVDSCommand(HostName =
kvm-ldn-01, ConvertOvaVDSParameters:{runAsync='true'
, hostId='385dc50a-0617-4e84-9aea-1d9e0de294a5',
ovaPath='/home/export/vm/wvm2.ova', vmName='wvm2',
storageDomainId='9d1fe12c-5c5f-49ad-a875-a735acba2530',
storagePoolId='f351dc97-b524-434c-b14d-c12e04ac4c7d', virtio
2016-07-14 16:59:02,230 INFO
[org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector]
(pool-7-thread-10) [49ba3bae] Correlation ID: 49ba3bae, Call Stack: null,
Custom Event ID: -1, Message: Starting to convert Vm wvm2
2016-07-14 17:04:44,765 INFO
[org.ovirt.engine.core.bll.exportimport.ConvertVmCallback]
(DefaultQuartzScheduler4) [49ba3bae] Conversion of VM from exteral
enironment failed: copy-disk stream closed unexpectedly
2016-07-14 17:04:45,793 ERROR
[org.ovirt.engine.core.bll.exportimport.ConvertOvaCommand]
(DefaultQuartzScheduler2) [43b33ecc] Ending command
'org.ovirt.engine.core.bll.exportimport.ConvertOvaCommand' with failure.
2016-07-14 17:04:45,882 INFO
[org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector]
(DefaultQuartzScheduler2) [43b33ecc] Correlation ID: 49ba3bae, Call Stack:
null, Custom Event ID: -1, Message: Failed to convert Vm wvm2
>
> I'm considering using virt-v2v to do the conversion of the .ova, but I'm
> not sure how to get that into ovirt then.
>
> Any suggestions?
What I ended up doing was using Joey Boggs's guest-image-ovf-creator.py to
convert the image to the 'correct'
structure and then upload it via engine-image-uploader to my export domain.
It did this, and I can see the files
in the export domain, but I can't import them via the GUI as they don't
appear. Should they? Or should there be
an 'import domain' somewhere?
Try to run virt-v2v -i ova -o local to import the ova to local disk
(see
the
virt-v2v man page for more options) and see if that pass - the errors can
be
more detailed there (it suppose to reflect the same error that you get in
vdsm
log)., another options you can do is run virt-v2v in verbose mode (virt-v2v
-v).
I can try this but I'm not quite sure how to go about it. The ovf I created
via guest-image-ovf-creator is on an NFS mount
on the engine: do I need to run virt-v2v on one of the nodes? If so, I
assume I need to set the output to an export domain.
Does '-o local' stick it on the node's VM storage?
Thanks,
Cam
>
> Regards,
>
> Cam
> _______________________________________________
> Users mailing list
> Users(a)ovirt.org
>
http://lists.ovirt.org/mailman/listinfo/users