http://bugzilla.suse.com/show_bug.cgi?id=908134 --- Comment #8 from Mike Latimer <mlatimer@suse.com> --- (In reply to Martin Pluskal from comment #4)

Ah, I was using https://access.redhat.com/documentation/en-US/ Red_Hat_Enterprise_Virtualization/3.0/html-single/V2V_Guide/index.html#sub- sect-convert-remote-kvm-virtual-machine as source of information, and my understanding of "Converting a remote KVM virtual machine" was that virt-v2v can also be used to transef vm between hosts.

So that documentation has prompted me to rethink things a bit... It does make sense to convert a KVM guest to RHEV using virt-v2v. As RHEV is KVM-based, KVM to KVM should definitely work.

...

Regarding the log in comment #2, the important message here is "The connected hypervisor does not support a x86_64 kvm guest". I am not sure what was source of this error, but both machines are KVM - I was not trying to convert KVM to XEN.

Hmm... The above message is specifically due to `virsh capabilities` not reporting that an x86_64 guest is supported as a KVM domain. However, looking earlier into the debug log I found the following message:

Could not access KVM kernel module: No such file or directory failed to initialize KVM: No such file or directory

Can you attach a supportconfig from the target machine? It looks like we are not even detecting a hypervisor. Another interesting message in that debug log is as follows:

virt-v2v: No capability in config matches os='linux' name='virtio' distro='opensuse' major='0' minor='0'

It looks like openSUSE_Factory is not reporting a valid major and minor number from the guestfs tools. I'll have to dig deeper here. Can you try testing with SLES12, or openSUSE 13.2? (If you do, please attach debug logs.) I just ran a quick KVM-KVM test (SLES12 KVM -to- SLES12 KVM, with a SLES12 guest) and it did work for me. I'll dig through your logs further next week and track down what the root cause is. -- You are receiving this mail because: You are on the CC list for the bug.