Created attachment 343206 [details] generated .xml file Description of problem: virt-convert provided conversion of vmware machine doesn't run. Version-Release number of selected component (if applicable): python-virtinst-0.400.3-8.fc11.noarch libvirt-0.6.2-6.fc11.x86_64 How reproducible: 100% Steps to Reproduce: 1.download http://www.minix3.org/download/minix3_1_2a_vmware.zip 2.unzip somewhere in /tmp 3.virt-convert --i vmx -o virt-image -v MS-DOS.vmx 4.copy minix/MS-DOS.raw to /var/lib/libvirt/images 5.restorecon -v -R /var/lib/libvirt 6.virsh define /tmp/minix/minix/minix.virt-image.xml Actual results: [root@viklef qemu]# LANG=C virsh define /tmp/minix/minix/minix.virt-image.xml error: Failed to define domain from /tmp/minix/minix/minix.virt-image.xml error: internal error incorrect root element Expected results: new domain minix happens Additional info:
Created attachment 343207 [details] minimal machine which virsh define accepted
Created attachment 343208 [details] complete bootable machine (misconfigured network) After some massaging with virt-manager I got this bootable machine, except network manager (is of course screwed up ... I don't what kind of ethernet card vmware pretends to provide).
The xml output by virt-convert is intended to be passed to virt-image, not virsh. Can you try running the output through virt-image and reporting the results? The virt-convert tool truthfully hasn't had a lot of testing, so I'd be interested in hearing what problems you might hit.
Created attachment 343312 [details] what is provided by virt-image
yes, virt-image is sligtly better ... generated .xml runs correctly. But it is still not good enough ... what kind of Ethernet card vmware provides? I suppose it should work with that (because vmware machine is provided by minix folks themselves), but minix in kvm cannot find it.
This bug appears to have been reported against 'rawhide' during the Fedora 11 development cycle. Changing version to '11'. More information and reason for this action is here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
This message is a reminder that Fedora 11 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 11. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '11'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 11's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 11 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora please change the 'version' of this bug to the applicable version. If you are unable to change the version, please add a comment here and someone will do it for you. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
Fedora 11 changed to end-of-life (EOL) status on 2010-06-25. Fedora 11 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. Thank you for reporting this bug and we are sorry it could not be fixed.
This message is a reminder that Fedora 12 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 12. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '12'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 12's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 12 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora please change the 'version' of this bug to the applicable version. If you are unable to change the version, please add a comment here and someone will do it for you. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
It does now in F14, or maybe this was PEBKAC, anyway I was able to import vmWare appliance into virt-manager managed host.