Well, you seem to have extreme problems in setting this up, so I write some basic setup which should just work with all vms and all "hosts" on the same network: have 2 physical servers, both in the same network (maybe via dhcp or static, doesn't matter). Setup on both hosts EL6.4 (6.5 should work too, but I haven't tested that). On one host install ovirt-engine the following way: For ovirt to work, the host must resolve his hostname via his IP. if you do this through /etc/hosts or via DNS is up to you :-) #Install the repo: yum -y install http://resources.ovirt.org/releases/ovirt-release-el.noarch.rpm #Install EPEL (we need some packages from here): yum -y install http://dl.fedoraproject.org/pub/epel/6/x86_64/epel-release-6-8.noarch.rpm #We need these packages from epel: yum install novnc python-ply python-kitchen python-daemon #now deactivate epel, in order to install ovirt-engine! Why deactivate? #EPEL has also some of the ovirt-packages but different versions, so #avoid conflicts by: sed -i 's/enabled=1/enabled=0/' /etc/yum.repos.d/epel.repo #now install engine: yum install ovirt-engine #and configure it (may start automatically, don't remember that one): engine-setup #pay attention to the firewall settings during engine-setup Now the second host: Install EL 6.4(6.5 should work too? didn't do this one for now). #Install EPEL: yum -y install http://ftp.tu-chemnitz.de/pub/linux/fedora-epel/6/i386/epel-release-6-8.noar... #Install ovirt-repo: yum -y install http://resources.ovirt.org/releases/ovirt-release-el.noarch.rpm depending on where you want your data domain, you may have to create a directory for it and assign the rights for ovirt to it: chown -R 36:36 /path/to/local/storage make sure SSH is setup on both hosts. Now go to your adminportal: Create a new datacenter, and a cluster in it. go to "system"(in the left pane)->"Hosts"(right pane) Click "New" select Datacenter and Cluster, fill in a name, address(IP or Resolvable DNS-Name (maybe even via "/etc/hosts")IPv6 doesn't work afaik), fill in the root password of the remote host. Click on "advanced parameters", for most users "automatically configure host firewall" is the right thing. You can test the connection by clicking "fetch", it should fill in automatically the ssh_host_key, if it does not, check your network setup! Optional you can configure powermanagement (you want that, ovirt complains a lot without, and it's useful!). When you click "Ok" the following happens in the background: engine log ins with root/ssh credentials on the other server, installs vdsm via repo and automatically configures the ovirtmgmt bridge for you. (this takes some time) when this is finished you are ready to deploy vms. the datacenter, cluster and host get automatically the "ovirtmgmt" logical network. if you don't create others by hand, your vms in this dc get the same, if DHCP manages it and you install proper images into the vms all vms and hosts should "see" everyone on this network. HTH -- Mit freundlichen Grüßen / Regards Sven Kieske Systemadministrator Mittwald CM Service GmbH & Co. KG Königsberger Straße 6 32339 Espelkamp T: +49-5772-293-100 F: +49-5772-293-333 https://www.mittwald.de Geschäftsführer: Robert Meyer St.Nr.: 331/5721/1033, USt-IdNr.: DE814773217, HRA 6640, AG Bad Oeynhausen Komplementärin: Robert Meyer Verwaltungs GmbH, HRB 13260, AG Bad Oeynhausen