I indeed followed that procedure, including confirming I could SSH into the KVM host as user ‘vdsm’ without being prompted for a password. I had specified the host name of the KVM host, not the IP (though at one point I also tried the IP, with same results.)
I was curious so on the KVM (source) host I added entries in /etc/hosts for all of the hypervisors in oVirt, along with the oVirt engine host for good measure (probably not necessary). I tried another import, this time withouth the “no_verify=1” and it worked without error. Our internal DNS works – all of the hosts were able to correctly resolve addresses prior to me editing /etc/hosts. But I guess something in that process does not query DNS. Anyway, at least that’s a cleaner solution than removing verification. Thanks, Daniel On 1/5/17, 10:01 AM, "Tomáš Golembiovský" <[email protected]> wrote: Hi, I'm sort of puzzled why you still saw "Host key verification failed" if you followed the procedure (or the steps described in [1]). https://www.ovirt.org/develop/release-management/features/virt/XenToOvirt/ Only thing I can think of is that you used IP of the KVM host during the procedure but then you used hostname in the URL (in import dialog). Another possible problem could be that there were two conflicting host keys in known_hosts file. But I believe adding "no_verify=1" would not help in this case. Tomas On Tue, 3 Jan 2017 22:07:42 +0000 "Beckman, Daniel" <[email protected]> wrote: > To answer my own question: as is often the case, perusing the commercial (RHV 4.0) documentation proved useful. > > The documentation is here: > https://access.redhat.com/documentation/en/red-hat-virtualization/4.0/paged/virtual-machine-management-guide/612-exporting-and-importing-virtual-machines-and-templates > > However, I kept getting the error “Host key verification failed.: Connection reset by peer”. This despite having followed the official documentation on generating and copying keys, under Procedure 6.2.6 Importing a Virtual Machine from KVM. > > Then I found this article from July 2012 about a different (but similar) scenario: > > https://access.redhat.com/solutions/136463 > > What helped was the “alternative test” suggestion. Here is the URI I ended up using with success: > > qemu+ssh://root@MY_KVM_HOST/system?no_verify=1 > > Appending “no_verify=1” did the trick. It’s possible that adding hostnames and IPs to /etc/hosts would have also resolved this, but for something performed infrequently (importing a VM from another environment), modifying the URI is easier. > > Best, > Daniel > > From: <[email protected]> on behalf of "Beckman, Daniel" <[email protected]> > Date: Tuesday, January 3, 2017 at 9:58 AM > To: "[email protected]" <[email protected]> > Subject: [ovirt-users] Import Virtual Machines From Web Admin GUI > > Can anyone point me to a step-by-step guide on getting an import (say, from KVM) to work? I gather it involves some sharing of SSH keys but I haven’t seen it explained in detail. Specifically, what user needs to trust what keys on which machines? The hypervisor hosts? The machine running the engine? Also, some examples of URI paths would be much appreciated. > > Thanks, > Daniel -- Tomáš Golembiovský <[email protected]> _______________________________________________ Users mailing list [email protected] http://lists.ovirt.org/mailman/listinfo/users
