To All:

I have a 64bit cpu with Centos 6.6 as the O/S. I am trying to get Virualization up and working and am having a problem. I had to go to the System/Administration/ADD/Remove software to load the Virtualization files and then i ran the load for Qemu-kvm, python-virstinst, virt-manager, virt-top, virt-viewer, libvirt, and libvirt-client.

Some of them didn't load up I beleive because they were there. Some did load. then I start the Virtual Machine Manager, enter the password, and when the window opens I select the localmachine and then do an ADD connection option and I select the "connect to remote host option" and it has ssh in there and username 'root' and then hostname i put rybo-vm.

I check the "autoconnect" box and hit connect. I then get this ERROR:


Unable to open a connection to the libvirt management daemon.

Libvirt URI is: qemu+ssh://root@rybo-vm/system

Verify that:
- The 'libvirtd' daemon has been started


Cannot recv data: ssh: Could not resolve hostname rybo-vm: Name or service not known: Connection reset by peer

Traceback (most recent call last):
File "/usr/share/virt-manager/virtManager/connection.py", line 1168, in _open_thread
self.vmm = self._try_open()
File "/usr/share/virt-manager/virtManager/connection.py", line 1152, in _try_open
flags)
File "/usr/lib64/python2.6/site-packages/libvirt.py", line 102, in openAuth
if ret is None:raise libvirtError('virConnectOpenAuth() failed')
libvirtError: Cannot recv data: ssh: Could not resolve hostname rybo-vm: Name or service not known: Connection reset by peer


What should I do to fix this problem? HELP!

cajunchief

It seems like it would be a whole hell of a lot easier to install ProxMox, instead of trying to create VMs on CentOS..

It would appear that you are trying to connect virt-manager to manage virtual machines on a different host.

When it starts the virst time. Double click on the new connection listed in the big white box. Set it to local host. Like in the image below.

It will be so much fun debugging a weird hybrid of debian, rhel and ovz, right? One that doesn't even use libvirt

The error is quite self-explanatory - the client software (virt-manager) cannot connect to the backend server (libvirtd).

If you are trying to connecto to a local machine, you need to use localhost
If you are actually trying to reach another host, then you should check connectivity (network/ports/firewall/etc) and the actual backend daemon, i.e. verify libvirtd is up and running