----- Original Message -----
From: "George Machitidze" <giomac@gmail.com> To: "Itamar Heim" <iheim@redhat.com> Cc: "Simone Tiraboschi" <stirabos@redhat.com>, "George Machitidze" <gmachitidze@greennet.ge>, "users" <Users@ovirt.org> Sent: Tuesday, July 22, 2014 11:58:35 AM Subject: Re: [ovirt-users] Deploying hosted engine on second host with different CPU model
Simone, Itamar
thanks for reply
nx flag doesn't exist on second host. should it throw this partucular error and not detect cpu type?
Yes, on some CPUs if the NX flag is not active host-deploy cannot detect the CPU type due to hardware constraints getting that error.
What is target release for patch?
3.5.0 beta2, but the patch is of course not able to enable nx flag by itself: it simply inform the user about that asking him to enable NX support in the bios. https://bugzilla.redhat.com/show_bug.cgi?id=1103672
I will build one more test lab for ovirt. I've already faced about 10 bugs in 3.4.2, but all are already solved in 3.4.3 :)
*George Machitidze*
2014-07-22 13:37 GMT+04:00 Itamar Heim <iheim@redhat.com>:
On 07/22/2014 12:31 PM, Simone Tiraboschi wrote:
Than can you also check the presence of vmx and nx flags in /proc/cpuinfo ?
Recently we solved a bug regarding that:https://bugzilla.redhat. com/show_bug.cgi?id=1119145 Hosted engine deploy didn't checked the status of nx flag but some CPU requires also to enable NX to properly support virtualization.
just a note, to avoid live migration issues we always require the nx flag to be turned on in ovirt.
_______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users