Hi Yuval i think migrate was only the RAM not die virtual hard disk. For so an scenario you need one separate Ovirt Engine (Management) one separate Storage and two Ovirt Nodes. An then you can build a HA Solution to reduce a Node failure. the single point of failure there will still give Eg. Storage, Ovirt Engine and Network. But i think you can cluster the application and storage from the nodes. Using drbd, ucarp, etc. greeting Andreas ----- Ursprüngliche Mail ----- Von: "Yuval M" <yuvalme(a)gmail.com&gt; An: users(a)ovirt.org CC: "Limor Gavish" <lgavish(a)gmail.com&gt; Gesendet: Sonntag, 6. Januar 2013 21:08:48 Betreff: [Users] Choosing which network to run VM migration on ovirt 3.1 Hi, I'm running the following setup: 2 hosts, each has 2 physical NICs, the first NIC (which is bridged to ovirtmgmt) is a 100Mbps ethernet card connected to a switch (and to the internet) the 2nd NIC is a fast Infiniband card which is connected back-to-back to the other host. both links are running fine, and I managed to have the 2nd host mount the storage via the fast link. The problem is that VM migration takes place over the slow link. How do I configure the cluster so that the migration uses the fast link? I've already created a network using the web interface. the migration still uses the slow link. Thanks, Yuval _______________________________________________ Users mailing list Users(a)ovirt.org http://lists.ovirt.org/mailman/listinfo/users

On Sun, Jan 06, 2013 at 10:08:48PM +0200, Yuval M wrote: > Hi, > I'm running the following setup: > 2 hosts, > each has 2 physical NICs, > the first NIC (which is bridged to ovirtmgmt) is a 100Mbps ethernet card > connected to a switch (and to the internet) > the 2nd NIC is a fast Infiniband card which is connected back-to-back to > the other host. > > both links are running fine, and I managed to have the 2nd host mount the > storage via the fast link. > The problem is that VM migration takes place over the slow link. > > How do I configure the cluster so that the migration uses the fast link? > I've already created a network using the web interface. the migration still > uses the slow link. Currently, oVirt always uses the ovirtmgmt network for migration data, even though libvirt already supports choosing a non-mananagement IP address for that. So I do not see how you could use the Infiniband card for migration without defining ovirtmgmt there, or with serious vdsm hacking. When I'm saying "serious", I mean something in the lines of (the untested!) http://gerrit.ovirt.org/10696 . To use this patch, you would first need to define a non-VM network over the Infiniband connection on both hosts, and provide them with IP address. Then, the name of this network should be passed as the value of a VM custom propery call 'mignet'. It would be great if you can try it out and debug it and/or comment on it. Dan

I would like to suggest a brand new "migration network" role in http://www.ovirt.org/Features/Migration_Network to provide managenet/migration network separation. _______________________________________________