Usual prologue: we're testing on CentOS 5.5, RHEL subscriptions purchased.
Now trying to use virt-v2v to transfer Win2008 Server guest from ESXi host to KVM host.
Have enabled SSH on ESXi host, and can connect using esx+ssh://esxhost, but procedure
fails because nc isn't found on ESXi. Fair enough. BTW, ESXi looks like a radically
cut down RH system (/etc/sysconfig being the give-away)?
So, using esx:// connection method which presumably uses TLS ...
Connection commands I'm trying to use:
virt-v2v -f virt-v2v.conf -ic esx://esxhost/?no_verify=1 -op vm_nfs 'HPTRIM
Sandbox'
virt-v2v -f virt-v2v.conf -ic esx://esxhost/ -op vm_nfs 'HPTRIM Sandbox'
I have eliminated libvirt error messages (all #38) relating to /etc/pki/CA/cacert.pem and
/etc/pki/libvirt/private/clientkey.pem by creating those files on KVM host according to
info on this page:
http://libvirt.org/remote.html#Remote_libvirtd_configuration
Now I am down to a simple connection refused error message:
virt-v2v: Failed to connect to esx://esxhost/: libvirt error code: 38, message: unable to
connect to 'esxhost': Connection refused
I have also tried suggestion on webpage above regarding these libvirtd.conf settings and
restarted libvirtd:
tls_no_verify_certificate = 1
key_file = ""
cert_file = ""
ca_file = ""
crl_file = ""
... But no change.
The problem may well be the TLS certificates, PKI isn't one of my strong points. I
believe the hostnames in the certificates are correct. Which certificates (if any) should
be copied to the ESXi host (client or server)?
Should I copy any certificates from /etc/vmware/ssl to the KVM host, if so which
certificate (rui.crt or rui.key) and where to?
There doesn't appear to be anything resembling an iptables firewall in place on the
ESXi host.
Anyway, any suggestions on what the problem could be greatly appreciated.
Michael Hall
IT Communications Officer
Alice Springs Town Council