Description of problem: I'm testing OVA file import and it fails without clear info. IIUC it fails because vdsm does not like return code of v2v ??? ... 2018-01-30 12:42:30,228+0100 INFO (v2v/338b5bd8) [vdsm.api] FINISH teardownImage return=None from=internal, task_id=3d3838df-67d7-462a-8629-b97dcac91f65 (api:52) 2018-01-30 12:42:30,229+0100 ERROR (v2v/338b5bd8) [root] Job u'338b5bd8-324c-43a1-980b-0dfe47d6198b' failed (v2v:866) Traceback (most recent call last): File "/usr/lib/python2.7/site-packages/vdsm/v2v.py", line 861, in _run self._import() File "/usr/lib/python2.7/site-packages/vdsm/v2v.py", line 886, in _import self._proc.returncode)) V2VProcessError: Job u'338b5bd8-324c-43a1-980b-0dfe47d6198b' process failed exit-code: 1 ... some interesting lines before libguestfs stuff closes "convertion"...: ... # egrep -i '^(guestfs.*|virt-v2v).*(error|warn|fail|no such)' /var/log/vdsm/import/import-338b5bd8-324c-43a1-980b-0dfe47d6198b-20180130T124140.log guestfsd: error: /var/lib/dpkg/status: No such file or directory ... Debian, really? I used an OVA file found online as example https://virtuallymikebrown.com/2012/02/05/a-small-virtual-machine-for-a-test-lab/#more-678: curl -o dsl-4-4-10.ova https://virtuallymikebrown.files.wordpress.com/2012/02/dsl-4-4-10.doc I would expect useful info about failure. I am not also sure why import did run supermin5/qemu if this is just convertion and no "provision" of the image itself is expected to be done. Version-Release number of selected component (if applicable): vdsm-4.20.17-1.el7ev.x86_64 virt-v2v-1.36.10-6.el7.x86_64 How reproducible: 100% Steps to Reproduce: 1. import this ova file (see above) 2. fails without clear info 3. Actual results: it's not clear what's the problem. i can run without any issue vmdk inside ova file via qemu-system-x86_64 -m 512 -hda $image Expected results: clear info. Additional info: $ tar tvf dsl-4-4-10.ova -rw-r--r-- VMware/VMware 5142 2012-02-02 10:15 DSL-4.4.10.ovf -rw-r--r-- VMware/VMware 58358272 2012-02-02 10:15 DSL-4.4.10-disk1.vmdk -rw-r--r-- VMware/VMware 135 2012-02-02 10:15 DSL-4.4.10.mf $ qemu-img info DSL-4.4.10-disk1.vmdk image: DSL-4.4.10-disk1.vmdk file format: vmdk virtual size: 128M (134217728 bytes) disk size: 56M cluster_size: 65536 Format specific information: cid: 1680580603 parent cid: 4294967295 create type: streamOptimized extents: [0]: compressed: true virtual size: 134217728 filename: DSL-4.4.10-disk1.vmdk cluster size: 65536 format:
yep, conversion failed, I guess what you're converting is not really a "normal" debian OS, is it?
(In reply to Michal Skrivanek from comment #2) > yep, conversion failed, I guess what you're converting is not really a > "normal" debian OS, is it? Yes, DSL = Damn Small Linux, IIUC not really Debian based.
I would suggest to open issue on upstream libguestfs to support this OS. oVirt only supports conversion of OSes which libguestfs does, and DSL is not on the list AFAIK.
(In reply to Michal Skrivanek from comment #4) > I would suggest to open issue on upstream libguestfs to support this OS. > oVirt only supports conversion of OSes which libguestfs does, and DSL is not > on the list AFAIK. What? Where is it stated (url to docs please!) that one cannot upload whatever OVA file he wants? We do support 'Other OS' as VM guest type, so I don't understand your logic here.
upstream virt-v2v guest support (from manpage) Red Hat Enterprise Linux 3, 4, 5, 6, 7 CentOS 3, 4, 5, 6, 7 Scientific Linux 3, 4, 5, 6, 7 Oracle Linux Fedora SLES 10 and up OpenSUSE 10 and up Debian 6 and up Ubuntu 10.04, 12.04, 14.04, 16.04, and up Windows XP to Windows 10 / Windows Server 2016