- Original Message -
From: Itamar Heim ih...@redhat.com
To: Andrew Lau and...@andrewklau.com, George Machitidze
gmachiti...@greennet.ge
Cc: users Users@ovirt.org
Sent: Tuesday, July 22, 2014 12:09:54 AM
Subject: Re: [ovirt-users] Deploying hosted engine on second host
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
Simone, Itamar
thanks for reply
nx flag doesn't exist on second host. should it throw this partucular error
and not detect cpu type?
What is target release for patch?
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 :)
On 07/22/2014 12:58 PM, George Machitidze wrote:
Simone, Itamar
thanks for reply
nx flag doesn't exist on second host. should it throw this partucular
error and not detect cpu type?
not sure.
in any case, please make sure to do a COLD boot after changing it in the
bios.
] 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
On 07/18/2014 02:05 AM, Andrew Lau wrote:
I think you should be able specify this within the ovirt-engine, just
modify the cluster's cpu compatibility. I hit this too, but i think I
just ended up provisioning the older machine first then the newer ones
joined with the older model
1. first the
Hello,
I am deploying hosted engine (HA) on hosts with different CPU
models on one of my oVirt labs.
Host have different CPU's or there is
also the problem: virtualization platform cannot detect CPU at all, The
following CPU types are supported by this host: is empty:
2014-07-17
16:51:42
I think you should be able specify this within the ovirt-engine, just
modify the cluster's cpu compatibility. I hit this too, but i think I
just ended up provisioning the older machine first then the newer ones
joined with the older model
On Thu, Jul 17, 2014 at 11:05 PM, George Machitidze
8 matches
Mail list logo