<div dir="ltr">So cpu in fact does pass validation? Could my issue be the network interface name - p1p1? Usually it's em1 but on this machine for some reason was named differently..<br></div><div class="gmail_extra">
<br><br><div class="gmail_quote">On Mon, May 20, 2013 at 3:05 AM, Sandro Bonazzola <span dir="ltr"><<a href="mailto:sbonazzo@redhat.com" target="_blank">sbonazzo@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Il 20/05/2013 10:02, Dan Kenigsberg ha scritto:<br>
<div><div class="h5">> On Mon, May 20, 2013 at 10:34:35AM +0300, Itamar Heim wrote:<br>
>> On 05/20/2013 10:01 AM, Sandro Bonazzola wrote:<br>
>>> Il 17/05/2013 17:48, Itamar Heim ha scritto:<br>
>>>> On 05/17/2013 06:01 PM, Sandro Bonazzola wrote:<br>
>>>>> Hi,<br>
>>>>> looking at the logs seems you're trying to install all-in-one on a<br>
>>>>> host that doesn't support virtualization:<br>
>>>>><br>
>>>>> 2013-05-17 07:57:56,749 ERROR<br>
>>>>> [org.ovirt.engine.core.bll.InstallerMessages] (VdsDeploy) Installation<br>
>>>>> ovirt.wilk.local: Failed to execute stage 'Setup validation': Hardware<br>
>>>>> does not support virtualization<br>
>>>>><br>
>>>>> This seems to be the reason for<br>
>>>>><br>
>>>>> Error: Host was found in a 'Failed' state.<br>
>>>> wasn't this the first step in AIO - to validate this?<br>
>>>><br>
>>> AIO ask libvirtd about supported cpus, this is the log about the cpu<br>
>>> validation:<br>
>>><br>
>>> 2013-05-17 07:54:31::INFO::all_in_one_100::203::root:: libvirt service<br>
>>> is started<br>
>>> 2013-05-17 07:54:31::DEBUG::setup_sequences::59::root:: running<br>
>>> getSupportedCpus<br>
>>> 2013-05-17 07:54:31::DEBUG::all_in_one_100::393::root:: Attempting to<br>
>>> load the caps vdsm module<br>
>>> 2013-05-17 07:54:32::DEBUG::all_in_one_100::403::root:: Supported CPU<br>
>>> models are:<br>
>>> 2013-05-17 07:54:32::DEBUG::all_in_one_100::405::root:: model_athlon<br>
>>> 2013-05-17 07:54:32::DEBUG::all_in_one_100::405::root:: model_Opteron_G1<br>
>>> 2013-05-17 07:54:32::DEBUG::setup_sequences::59::root:: running getCPUFamily<br>
>>> 2013-05-17 07:54:32::DEBUG::all_in_one_100::414::root:: Determening the<br>
>>> CPU family supported by the host<br>
>>> 2013-05-17 07:54:32::DEBUG::all_in_one_100::434::root:: comparing<br>
>>> model_Westmere with supported models<br>
>>> 2013-05-17 07:54:32::DEBUG::all_in_one_100::434::root:: comparing<br>
>>> model_Nehalem with supported models<br>
>>> 2013-05-17 07:54:32::DEBUG::all_in_one_100::434::root:: comparing<br>
>>> model_Penryn with supported models<br>
>>> 2013-05-17 07:54:32::DEBUG::all_in_one_100::434::root:: comparing<br>
>>> model_Conroe with supported models<br>
>>> 2013-05-17 07:54:32::DEBUG::all_in_one_100::434::root:: comparing<br>
>>> model_Opteron_G3 with supported models<br>
>>> 2013-05-17 07:54:32::DEBUG::all_in_one_100::434::root:: comparing<br>
>>> model_Opteron_G2 with supported models<br>
>>> 2013-05-17 07:54:32::DEBUG::all_in_one_100::434::root:: comparing<br>
>>> model_Opteron_G1 with supported models<br>
>>> 2013-05-17 07:54:32::DEBUG::all_in_one_100::436::root:: Supported model<br>
>>> family is: AMD Opteron G1<br>
>>><br>
>>> so it passed cpu validation.<br>
>> ok, that's one part of cpu validation for the cpu model. VDSM (or<br>
>> the old bootstrap code) was also supposed to have one for VT enabled<br>
>> in bios.<br>
> The old bootstrap code indeed has virtEnabledInCpuAndBios().<br>
> ovirt-host-deploy has a parallel VdsmEnv.CHECK_VIRT_HARDWARE optional<br>
> check.<br>
><br>
> HTH,<br>
> Dan.<br>
<br>
</div></div>Ok, I'll add this check in AIO plugin.<br>
Has anybody already opened a bug about this issue?<br>
<div class="HOEnZb"><div class="h5"><br>
--<br>
Sandro Bonazzola<br>
Better technology. Faster innovation. Powered by community collaboration.<br>
See how it works at <a href="http://redhat.com" target="_blank">redhat.com</a><br>
<br>
</div></div></blockquote></div><br></div>