Description of problem: Virt-v2v can't convert the guest from VMware ESXi to Openstack Version-Release number of selected component (if applicable): virt-v2v-1.40.2-6.fc31.x86_64 libguestfs-1.40.2-6.fc31.x86_64 libvirt-5.5.0-1.fc31.x86_64 qemu-kvm-4.0.0-5.fc31.x86_64 How reproducible: 100% virt-v2v host: it is a openstack server guest is fedora31 Steps to Reproduce: 1. Prepare a linux guest(in the VMware ESXi, status is shutoff, guest is redhat Enterprise 6.5) and using virt-v2v can convert the linux guest to openstack but the conversion is failed. pls refer to attachment log # virt-v2v -ic vpx://administrator%40vsphere.local.1.213/?no_verify=1 Test02 -o openstack -oo server-id=<openstack-server-id/name> command: mount returned 32 command: mount: stderr: mount: /sysroot: unknown filesystem type. inspect_os: fses: inspect_get_roots: roots: libguestfs: trace: v2v: inspect_os = [] virt-v2v: error: inspection could not detect the source guest (or physical machine). Assuming that you are running virt-v2v/virt-p2v on a source which is supported (and not, for example, a blank disk), then this should not happen. No root device found in this operating system image. The guest information like this: [root@localhost ~]# cat /etc/*release CentOS release 6.10 (Final) CentOS release 6.10 (Final) CentOS release 6.10 (Final) [root@localhost ~]# lsblk NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT sda 8:0 0 3G 0 disk ├─sda1 8:1 0 500M 0 part /boot └─sda2 8:2 0 2.5G 0 part ├─VolGroup-lv_root (dm-0) 253:0 0 2.2G 0 lvm / └─VolGroup-lv_swap (dm-1) 253:1 0 304M 0 lvm [SWAP] sr0 11:0 1 406M 0 rom Actual results: As above description
Created attachment 1591232 [details] virt-v2v vmware guest to openstack log
Unfortunately the conversion log isn't complete. However I can see that the conversion times out: qemu-system-x86_64: curl: Operation timed out after 2000001 milliseconds with 63264 out of 327680 bytes received and everything fails shortly afterwards. You're using the very slow HTTPS method (see virt-v2v-input-vmware section "INPUT FROM VMWARE VCENTER SERVER"). A much faster way to do it is to use -i vmx from local file, over ssh or over VDDK. These alternate methods are also docmented in virt-v2v-input-vmware(1).
This bug appears to have been reported against 'rawhide' during the Fedora 31 development cycle. Changing version to '31'.
This bug appears to have been reported against 'rawhide' during the Fedora 31 development cycle. Changing version to 31.
This message is a reminder that Fedora 31 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora 31 on 2020-11-24. 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 EOL if it remains open with a Fedora 'version' of '31'. 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. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 31 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, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. 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.
Fedora 31 changed to end-of-life (EOL) status on 2020-11-24. Fedora 31 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. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.