On 01/03/2013 07:04 PM, Itamar Heim wrote:
On 01/03/2013 07:25 PM, Soeren Grunewald wrote:
On 01/03/2013 05:33 PM, Itamar Heim wrote:
On 01/03/2013 06:28 PM, Soeren Grunewald wrote:
On 01/03/2013 05:08 PM, Itamar Heim wrote:
Hi Everyone,

as we wrap oVirt 3.2, I wanted to check with oVirt users on what they
find good/useful in oVirt, and what they would like to see
improved/added in coming versions?

A nice feature would be to be able to migrate guests between AMD and
Intel host machines.
KVM should be able to support it [1]. I don't know if other hypervisors
are able/can to support this. Because oVirt aims to support different
hypervisors it might be problematic. But I think offline migration
should be possible.

can you please elaborate what do you mean by offline migration?

With offline  migration, I means the guest is not running while moving
it from one host to another.

I have 2 host machines for testing. One is running on a AMD Opteron and
the other Intel Xeon. Since I can not put both machines in the same
cluster, I have specified a cluster called AMD (for the opteron) and
another called Intel (for the xeon).
Now I would like to move a guest from the AMD machine to the Intel
machine. Since the CPU does not match I can't.

I'm not aware that you can't.

Ok, now is see my problem.

you should be able to move the VM from one cluster to the other.
yes, it will see a different cpu model. why is that an issue?

To move the guest I need to "edit" the guest and than I can change the cluster.


I assume the solution for this could be a generic cluster definition.
Something with a limited/specific cpu set equal to the qemu
configuration "-cpu qemu32" or "-cpu qemu64".



Users mailing list

Reply via email to