[Users] all-in-one install fail
I've successfully installed several all-in-one setups but am having issues currently. Install details: Engine: **Set SELinux to permissive Fedora 18 basic install yum remove firewalld Edit /etc/hosts 192.168.0.120 engine.ovirt.local Update packages: yum -y update Reboot Configure Repo: yum localinstall http://ovirt.org/releases/ovirt-release-fedora.noarch.rpm Install Engine: yum install ovirt-engine-setup-plugin-allinone engine-setup Setup works fine until it reaches adding local host and fails with error: Error: Host was found in a 'Failed' state. I've attached engine-setup logs. I've also tried manually adding host from admin console with no luck. Showing ssh error 1. Thanks in advance. Ryan
This is a multi-part message in MIME format. --------------090708070201090303060403 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Hi, looking at the logs seems you're trying to install all-in-one on a host that doesn't support virtualization: 2013-05-17 07:57:56,749 ERROR [org.ovirt.engine.core.bll.InstallerMessages] (VdsDeploy) Installation ovirt.wilk.local: Failed to execute stage 'Setup validation': Hardware does not support virtualization This seems to be the reason for Error: Host was found in a 'Failed' state. Il 17/05/2013 16:11, Ryan Wilkinson ha scritto:
I've successfully installed several all-in-one setups but am having issues currently. Install details:
Engine:
**Set SELinux to permissive
Fedora 18 basic install
yum remove firewalld
Edit /etc/hosts
192.168.0.120 engine.ovirt.local
Update packages:
yum -y update
Reboot
Configure Repo:
yum localinstall http://ovirt.org/releases/ovirt-release-fedora.noarch.rpm
Install Engine:
yum install ovirt-engine-setup-plugin-allinone
engine-setup
Setup works fine until it reaches adding local host and fails with error:
Error: Host was found in a 'Failed' state.
I've attached engine-setup logs. I've also tried manually adding host from admin console with no luck. Showing ssh error 1.
Thanks in advance.
Ryan
_______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
-- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com --------------090708070201090303060403 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit <html> <head> <meta content="text/html; charset=ISO-8859-1" http-equiv="Content-Type"> </head> <body bgcolor="#FFFFFF" text="#000000"> <div class="moz-cite-prefix"><br> Hi,<br> looking at the logs seems you're trying to install all-in-one on a host that doesn't support virtualization:<br> <br> 2013-05-17 07:57:56,749 ERROR [org.ovirt.engine.core.bll.InstallerMessages] (VdsDeploy) Installation ovirt.wilk.local: Failed to execute stage 'Setup validation': Hardware does not support virtualization<br> <br> This seems to be the reason for <br> <pre wrap="">Error: Host was found in a 'Failed' state.</pre> <br> <br> <br> <br> Il 17/05/2013 16:11, Ryan Wilkinson ha scritto:<br> </div> <blockquote cite="mid:CAOC1=1VOqWt8K0tw6SNHMtnPMQMVdeKTcdvp2nADGBCaEdS6ng@mail.gmail.com" type="cite"> <pre wrap="">I've successfully installed several all-in-one setups but am having issues currently. Install details: Engine: **Set SELinux to permissive Fedora 18 basic install yum remove firewalld Edit /etc/hosts 192.168.0.120 engine.ovirt.local Update packages: yum -y update Reboot Configure Repo: yum localinstall <a class="moz-txt-link-freetext" href="http://ovirt.org/releases/ovirt-release-fedora.noarch.rpm">http://ovirt.org/releases/ovirt-release-fedora.noarch.rpm</a> Install Engine: yum install ovirt-engine-setup-plugin-allinone engine-setup Setup works fine until it reaches adding local host and fails with error: Error: Host was found in a 'Failed' state. I've attached engine-setup logs. I've also tried manually adding host from admin console with no luck. Showing ssh error 1. Thanks in advance. Ryan </pre> <br> <fieldset class="mimeAttachmentHeader"></fieldset> <br> <pre wrap="">_______________________________________________ Users mailing list <a class="moz-txt-link-abbreviated" href="mailto:Users@ovirt.org">Users@ovirt.org</a> <a class="moz-txt-link-freetext" href="http://lists.ovirt.org/mailman/listinfo/users">http://lists.ovirt.org/mailman/listinfo/users</a> </pre> </blockquote> <br> <br> <pre class="moz-signature" cols="72">-- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com</pre> </body> </html> --------------090708070201090303060403--
On 05/17/2013 06:01 PM, Sandro Bonazzola wrote:
Hi, looking at the logs seems you're trying to install all-in-one on a host that doesn't support virtualization:
2013-05-17 07:57:56,749 ERROR [org.ovirt.engine.core.bll.InstallerMessages] (VdsDeploy) Installation ovirt.wilk.local: Failed to execute stage 'Setup validation': Hardware does not support virtualization
This seems to be the reason for
Error: Host was found in a 'Failed' state.
wasn't this the first step in AIO - to validate this?
Il 17/05/2013 16:11, Ryan Wilkinson ha scritto:
I've successfully installed several all-in-one setups but am having issues currently. Install details:
Engine:
**Set SELinux to permissive
Fedora 18 basic install
yum remove firewalld
Edit /etc/hosts
192.168.0.120 engine.ovirt.local
Update packages:
yum -y update
Reboot
Configure Repo:
yum localinstallhttp://ovirt.org/releases/ovirt-release-fedora.noarch.rpm
Install Engine:
yum install ovirt-engine-setup-plugin-allinone
engine-setup
Setup works fine until it reaches adding local host and fails with error:
Error: Host was found in a 'Failed' state.
I've attached engine-setup logs. I've also tried manually adding host from admin console with no luck. Showing ssh error 1.
Thanks in advance.
Ryan
_______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
-- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com
_______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Il 17/05/2013 17:48, Itamar Heim ha scritto:
On 05/17/2013 06:01 PM, Sandro Bonazzola wrote:
Hi, looking at the logs seems you're trying to install all-in-one on a host that doesn't support virtualization:
2013-05-17 07:57:56,749 ERROR [org.ovirt.engine.core.bll.InstallerMessages] (VdsDeploy) Installation ovirt.wilk.local: Failed to execute stage 'Setup validation': Hardware does not support virtualization
This seems to be the reason for
Error: Host was found in a 'Failed' state.
wasn't this the first step in AIO - to validate this?
AIO ask libvirtd about supported cpus, this is the log about the cpu validation: 2013-05-17 07:54:31::INFO::all_in_one_100::203::root:: libvirt service is started 2013-05-17 07:54:31::DEBUG::setup_sequences::59::root:: running getSupportedCpus 2013-05-17 07:54:31::DEBUG::all_in_one_100::393::root:: Attempting to load the caps vdsm module 2013-05-17 07:54:32::DEBUG::all_in_one_100::403::root:: Supported CPU models are: 2013-05-17 07:54:32::DEBUG::all_in_one_100::405::root:: model_athlon 2013-05-17 07:54:32::DEBUG::all_in_one_100::405::root:: model_Opteron_G1 2013-05-17 07:54:32::DEBUG::setup_sequences::59::root:: running getCPUFamily 2013-05-17 07:54:32::DEBUG::all_in_one_100::414::root:: Determening the CPU family supported by the host 2013-05-17 07:54:32::DEBUG::all_in_one_100::434::root:: comparing model_Westmere with supported models 2013-05-17 07:54:32::DEBUG::all_in_one_100::434::root:: comparing model_Nehalem with supported models 2013-05-17 07:54:32::DEBUG::all_in_one_100::434::root:: comparing model_Penryn with supported models 2013-05-17 07:54:32::DEBUG::all_in_one_100::434::root:: comparing model_Conroe with supported models 2013-05-17 07:54:32::DEBUG::all_in_one_100::434::root:: comparing model_Opteron_G3 with supported models 2013-05-17 07:54:32::DEBUG::all_in_one_100::434::root:: comparing model_Opteron_G2 with supported models 2013-05-17 07:54:32::DEBUG::all_in_one_100::434::root:: comparing model_Opteron_G1 with supported models 2013-05-17 07:54:32::DEBUG::all_in_one_100::436::root:: Supported model family is: AMD Opteron G1 so it passed cpu validation.
Il 17/05/2013 16:11, Ryan Wilkinson ha scritto:
I've successfully installed several all-in-one setups but am having issues currently. Install details:
Engine:
**Set SELinux to permissive
Fedora 18 basic install
yum remove firewalld
Edit /etc/hosts
192.168.0.120 engine.ovirt.local
Update packages:
yum -y update
Reboot
Configure Repo:
yum localinstallhttp://ovirt.org/releases/ovirt-release-fedora.noarch.rpm
Install Engine:
yum install ovirt-engine-setup-plugin-allinone
engine-setup
Setup works fine until it reaches adding local host and fails with error:
Error: Host was found in a 'Failed' state.
I've attached engine-setup logs. I've also tried manually adding host from admin console with no luck. Showing ssh error 1.
Thanks in advance.
Ryan
_______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
-- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com
_______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
-- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com
On 05/20/2013 10:01 AM, Sandro Bonazzola wrote:
Il 17/05/2013 17:48, Itamar Heim ha scritto:
On 05/17/2013 06:01 PM, Sandro Bonazzola wrote:
Hi, looking at the logs seems you're trying to install all-in-one on a host that doesn't support virtualization:
2013-05-17 07:57:56,749 ERROR [org.ovirt.engine.core.bll.InstallerMessages] (VdsDeploy) Installation ovirt.wilk.local: Failed to execute stage 'Setup validation': Hardware does not support virtualization
This seems to be the reason for
Error: Host was found in a 'Failed' state.
wasn't this the first step in AIO - to validate this?
AIO ask libvirtd about supported cpus, this is the log about the cpu validation:
2013-05-17 07:54:31::INFO::all_in_one_100::203::root:: libvirt service is started 2013-05-17 07:54:31::DEBUG::setup_sequences::59::root:: running getSupportedCpus 2013-05-17 07:54:31::DEBUG::all_in_one_100::393::root:: Attempting to load the caps vdsm module 2013-05-17 07:54:32::DEBUG::all_in_one_100::403::root:: Supported CPU models are: 2013-05-17 07:54:32::DEBUG::all_in_one_100::405::root:: model_athlon 2013-05-17 07:54:32::DEBUG::all_in_one_100::405::root:: model_Opteron_G1 2013-05-17 07:54:32::DEBUG::setup_sequences::59::root:: running getCPUFamily 2013-05-17 07:54:32::DEBUG::all_in_one_100::414::root:: Determening the CPU family supported by the host 2013-05-17 07:54:32::DEBUG::all_in_one_100::434::root:: comparing model_Westmere with supported models 2013-05-17 07:54:32::DEBUG::all_in_one_100::434::root:: comparing model_Nehalem with supported models 2013-05-17 07:54:32::DEBUG::all_in_one_100::434::root:: comparing model_Penryn with supported models 2013-05-17 07:54:32::DEBUG::all_in_one_100::434::root:: comparing model_Conroe with supported models 2013-05-17 07:54:32::DEBUG::all_in_one_100::434::root:: comparing model_Opteron_G3 with supported models 2013-05-17 07:54:32::DEBUG::all_in_one_100::434::root:: comparing model_Opteron_G2 with supported models 2013-05-17 07:54:32::DEBUG::all_in_one_100::434::root:: comparing model_Opteron_G1 with supported models 2013-05-17 07:54:32::DEBUG::all_in_one_100::436::root:: Supported model family is: AMD Opteron G1
so it passed cpu validation.
ok, that's one part of cpu validation for the cpu model. VDSM (or the old bootstrap code) was also supposed to have one for VT enabled in bios.
On Mon, May 20, 2013 at 10:34:35AM +0300, Itamar Heim wrote:
On 05/20/2013 10:01 AM, Sandro Bonazzola wrote:
Il 17/05/2013 17:48, Itamar Heim ha scritto:
On 05/17/2013 06:01 PM, Sandro Bonazzola wrote:
Hi, looking at the logs seems you're trying to install all-in-one on a host that doesn't support virtualization:
2013-05-17 07:57:56,749 ERROR [org.ovirt.engine.core.bll.InstallerMessages] (VdsDeploy) Installation ovirt.wilk.local: Failed to execute stage 'Setup validation': Hardware does not support virtualization
This seems to be the reason for
Error: Host was found in a 'Failed' state.
wasn't this the first step in AIO - to validate this?
AIO ask libvirtd about supported cpus, this is the log about the cpu validation:
2013-05-17 07:54:31::INFO::all_in_one_100::203::root:: libvirt service is started 2013-05-17 07:54:31::DEBUG::setup_sequences::59::root:: running getSupportedCpus 2013-05-17 07:54:31::DEBUG::all_in_one_100::393::root:: Attempting to load the caps vdsm module 2013-05-17 07:54:32::DEBUG::all_in_one_100::403::root:: Supported CPU models are: 2013-05-17 07:54:32::DEBUG::all_in_one_100::405::root:: model_athlon 2013-05-17 07:54:32::DEBUG::all_in_one_100::405::root:: model_Opteron_G1 2013-05-17 07:54:32::DEBUG::setup_sequences::59::root:: running getCPUFamily 2013-05-17 07:54:32::DEBUG::all_in_one_100::414::root:: Determening the CPU family supported by the host 2013-05-17 07:54:32::DEBUG::all_in_one_100::434::root:: comparing model_Westmere with supported models 2013-05-17 07:54:32::DEBUG::all_in_one_100::434::root:: comparing model_Nehalem with supported models 2013-05-17 07:54:32::DEBUG::all_in_one_100::434::root:: comparing model_Penryn with supported models 2013-05-17 07:54:32::DEBUG::all_in_one_100::434::root:: comparing model_Conroe with supported models 2013-05-17 07:54:32::DEBUG::all_in_one_100::434::root:: comparing model_Opteron_G3 with supported models 2013-05-17 07:54:32::DEBUG::all_in_one_100::434::root:: comparing model_Opteron_G2 with supported models 2013-05-17 07:54:32::DEBUG::all_in_one_100::434::root:: comparing model_Opteron_G1 with supported models 2013-05-17 07:54:32::DEBUG::all_in_one_100::436::root:: Supported model family is: AMD Opteron G1
so it passed cpu validation.
ok, that's one part of cpu validation for the cpu model. VDSM (or the old bootstrap code) was also supposed to have one for VT enabled in bios.
The old bootstrap code indeed has virtEnabledInCpuAndBios(). ovirt-host-deploy has a parallel VdsmEnv.CHECK_VIRT_HARDWARE optional check. HTH, Dan.
Il 20/05/2013 10:02, Dan Kenigsberg ha scritto:
On Mon, May 20, 2013 at 10:34:35AM +0300, Itamar Heim wrote:
Il 17/05/2013 17:48, Itamar Heim ha scritto:
On 05/17/2013 06:01 PM, Sandro Bonazzola wrote:
Hi, looking at the logs seems you're trying to install all-in-one on a host that doesn't support virtualization:
2013-05-17 07:57:56,749 ERROR [org.ovirt.engine.core.bll.InstallerMessages] (VdsDeploy) Installation ovirt.wilk.local: Failed to execute stage 'Setup validation': Hardware does not support virtualization
This seems to be the reason for
Error: Host was found in a 'Failed' state. wasn't this the first step in AIO - to validate this?
AIO ask libvirtd about supported cpus, this is the log about the cpu validation:
2013-05-17 07:54:31::INFO::all_in_one_100::203::root:: libvirt service is started 2013-05-17 07:54:31::DEBUG::setup_sequences::59::root:: running getSupportedCpus 2013-05-17 07:54:31::DEBUG::all_in_one_100::393::root:: Attempting to load the caps vdsm module 2013-05-17 07:54:32::DEBUG::all_in_one_100::403::root:: Supported CPU models are: 2013-05-17 07:54:32::DEBUG::all_in_one_100::405::root:: model_athlon 2013-05-17 07:54:32::DEBUG::all_in_one_100::405::root:: model_Opteron_G1 2013-05-17 07:54:32::DEBUG::setup_sequences::59::root:: running getCPUFamily 2013-05-17 07:54:32::DEBUG::all_in_one_100::414::root:: Determening the CPU family supported by the host 2013-05-17 07:54:32::DEBUG::all_in_one_100::434::root:: comparing model_Westmere with supported models 2013-05-17 07:54:32::DEBUG::all_in_one_100::434::root:: comparing model_Nehalem with supported models 2013-05-17 07:54:32::DEBUG::all_in_one_100::434::root:: comparing model_Penryn with supported models 2013-05-17 07:54:32::DEBUG::all_in_one_100::434::root:: comparing model_Conroe with supported models 2013-05-17 07:54:32::DEBUG::all_in_one_100::434::root:: comparing model_Opteron_G3 with supported models 2013-05-17 07:54:32::DEBUG::all_in_one_100::434::root:: comparing model_Opteron_G2 with supported models 2013-05-17 07:54:32::DEBUG::all_in_one_100::434::root:: comparing model_Opteron_G1 with supported models 2013-05-17 07:54:32::DEBUG::all_in_one_100::436::root:: Supported model family is: AMD Opteron G1
so it passed cpu validation. ok, that's one part of cpu validation for the cpu model. VDSM (or
On 05/20/2013 10:01 AM, Sandro Bonazzola wrote: the old bootstrap code) was also supposed to have one for VT enabled in bios. The old bootstrap code indeed has virtEnabledInCpuAndBios(). ovirt-host-deploy has a parallel VdsmEnv.CHECK_VIRT_HARDWARE optional check.
HTH, Dan.
Ok, I'll add this check in AIO plugin. Has anybody already opened a bug about this issue? -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com
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.. On Mon, May 20, 2013 at 3:05 AM, Sandro Bonazzola <sbonazzo@redhat.com>wrote:
Il 20/05/2013 10:02, Dan Kenigsberg ha scritto:
On Mon, May 20, 2013 at 10:34:35AM +0300, Itamar Heim wrote:
Il 17/05/2013 17:48, Itamar Heim ha scritto:
On 05/17/2013 06:01 PM, Sandro Bonazzola wrote:
Hi, looking at the logs seems you're trying to install all-in-one on a host that doesn't support virtualization:
2013-05-17 07:57:56,749 ERROR [org.ovirt.engine.core.bll.InstallerMessages] (VdsDeploy) Installation ovirt.wilk.local: Failed to execute stage 'Setup validation': Hardware does not support virtualization
This seems to be the reason for
Error: Host was found in a 'Failed' state. wasn't this the first step in AIO - to validate this?
AIO ask libvirtd about supported cpus, this is the log about the cpu validation:
2013-05-17 07:54:31::INFO::all_in_one_100::203::root:: libvirt service is started 2013-05-17 07:54:31::DEBUG::setup_sequences::59::root:: running getSupportedCpus 2013-05-17 07:54:31::DEBUG::all_in_one_100::393::root:: Attempting to load the caps vdsm module 2013-05-17 07:54:32::DEBUG::all_in_one_100::403::root:: Supported CPU models are: 2013-05-17 07:54:32::DEBUG::all_in_one_100::405::root:: model_athlon 2013-05-17 07:54:32::DEBUG::all_in_one_100::405::root:: model_Opteron_G1 2013-05-17 07:54:32::DEBUG::setup_sequences::59::root:: running getCPUFamily 2013-05-17 07:54:32::DEBUG::all_in_one_100::414::root:: Determening the CPU family supported by the host 2013-05-17 07:54:32::DEBUG::all_in_one_100::434::root:: comparing model_Westmere with supported models 2013-05-17 07:54:32::DEBUG::all_in_one_100::434::root:: comparing model_Nehalem with supported models 2013-05-17 07:54:32::DEBUG::all_in_one_100::434::root:: comparing model_Penryn with supported models 2013-05-17 07:54:32::DEBUG::all_in_one_100::434::root:: comparing model_Conroe with supported models 2013-05-17 07:54:32::DEBUG::all_in_one_100::434::root:: comparing model_Opteron_G3 with supported models 2013-05-17 07:54:32::DEBUG::all_in_one_100::434::root:: comparing model_Opteron_G2 with supported models 2013-05-17 07:54:32::DEBUG::all_in_one_100::434::root:: comparing model_Opteron_G1 with supported models 2013-05-17 07:54:32::DEBUG::all_in_one_100::436::root:: Supported model family is: AMD Opteron G1
so it passed cpu validation. ok, that's one part of cpu validation for the cpu model. VDSM (or
On 05/20/2013 10:01 AM, Sandro Bonazzola wrote: the old bootstrap code) was also supposed to have one for VT enabled in bios. The old bootstrap code indeed has virtEnabledInCpuAndBios(). ovirt-host-deploy has a parallel VdsmEnv.CHECK_VIRT_HARDWARE optional check.
HTH, Dan.
Ok, I'll add this check in AIO plugin. Has anybody already opened a bug about this issue?
-- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com
On 05/20/2013 04:46 PM, Ryan Wilkinson wrote:
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..
current check is for cpu family, it doesn't cover VT being disabled by bios (which is what i understood you failed on, and simply need to enable at bios and do a cold boot)
On Mon, May 20, 2013 at 3:05 AM, Sandro Bonazzola <sbonazzo@redhat.com <mailto:sbonazzo@redhat.com>> wrote:
Il 20/05/2013 10:02, Dan Kenigsberg ha scritto: > On Mon, May 20, 2013 at 10:34:35AM +0300, Itamar Heim wrote: >> On 05/20/2013 10:01 AM, Sandro Bonazzola wrote: >>> Il 17/05/2013 17:48, Itamar Heim ha scritto: >>>> On 05/17/2013 06:01 PM, Sandro Bonazzola wrote: >>>>> Hi, >>>>> looking at the logs seems you're trying to install all-in-one on a >>>>> host that doesn't support virtualization: >>>>> >>>>> 2013-05-17 07:57:56,749 ERROR >>>>> [org.ovirt.engine.core.bll.InstallerMessages] (VdsDeploy) Installation >>>>> ovirt.wilk.local: Failed to execute stage 'Setup validation': Hardware >>>>> does not support virtualization >>>>> >>>>> This seems to be the reason for >>>>> >>>>> Error: Host was found in a 'Failed' state. >>>> wasn't this the first step in AIO - to validate this? >>>> >>> AIO ask libvirtd about supported cpus, this is the log about the cpu >>> validation: >>> >>> 2013-05-17 07:54:31::INFO::all_in_one_100::203::root:: libvirt service >>> is started >>> 2013-05-17 07:54:31::DEBUG::setup_sequences::59::root:: running >>> getSupportedCpus >>> 2013-05-17 07:54:31::DEBUG::all_in_one_100::393::root:: Attempting to >>> load the caps vdsm module >>> 2013-05-17 07:54:32::DEBUG::all_in_one_100::403::root:: Supported CPU >>> models are: >>> 2013-05-17 07:54:32::DEBUG::all_in_one_100::405::root:: model_athlon >>> 2013-05-17 07:54:32::DEBUG::all_in_one_100::405::root:: model_Opteron_G1 >>> 2013-05-17 07:54:32::DEBUG::setup_sequences::59::root:: running getCPUFamily >>> 2013-05-17 07:54:32::DEBUG::all_in_one_100::414::root:: Determening the >>> CPU family supported by the host >>> 2013-05-17 07:54:32::DEBUG::all_in_one_100::434::root:: comparing >>> model_Westmere with supported models >>> 2013-05-17 07:54:32::DEBUG::all_in_one_100::434::root:: comparing >>> model_Nehalem with supported models >>> 2013-05-17 07:54:32::DEBUG::all_in_one_100::434::root:: comparing >>> model_Penryn with supported models >>> 2013-05-17 07:54:32::DEBUG::all_in_one_100::434::root:: comparing >>> model_Conroe with supported models >>> 2013-05-17 07:54:32::DEBUG::all_in_one_100::434::root:: comparing >>> model_Opteron_G3 with supported models >>> 2013-05-17 07:54:32::DEBUG::all_in_one_100::434::root:: comparing >>> model_Opteron_G2 with supported models >>> 2013-05-17 07:54:32::DEBUG::all_in_one_100::434::root:: comparing >>> model_Opteron_G1 with supported models >>> 2013-05-17 07:54:32::DEBUG::all_in_one_100::436::root:: Supported model >>> family is: AMD Opteron G1 >>> >>> so it passed cpu validation. >> ok, that's one part of cpu validation for the cpu model. VDSM (or >> the old bootstrap code) was also supposed to have one for VT enabled >> in bios. > The old bootstrap code indeed has virtEnabledInCpuAndBios(). > ovirt-host-deploy has a parallel VdsmEnv.CHECK_VIRT_HARDWARE optional > check. > > HTH, > Dan.
Ok, I'll add this check in AIO plugin. Has anybody already opened a bug about this issue?
-- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com <http://redhat.com>
Sandro, This is dup of the code at[1], but I don't of having this code duplicated... Alon [1] http://gerrit.ovirt.org/gitweb?p=ovirt-host-deploy.git;a=blob;f=src/plugins/... ----- Original Message -----
From: "Itamar Heim" <iheim@redhat.com> To: "Ryan Wilkinson" <ryanwilk@gmail.com> Cc: "Sandro Bonazzola" <sbonazzo@redhat.com>, "Dan Kenigsberg" <danken@redhat.com>, users@ovirt.org, "Alon Bar-Lev" <alonbl@redhat.com>, "Alex Lourie" <alourie@redhat.com> Sent: Monday, May 20, 2013 4:49:02 PM Subject: Re: [Users] all-in-one install fail
On 05/20/2013 04:46 PM, Ryan Wilkinson wrote:
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..
current check is for cpu family, it doesn't cover VT being disabled by bios (which is what i understood you failed on, and simply need to enable at bios and do a cold boot)
On Mon, May 20, 2013 at 3:05 AM, Sandro Bonazzola <sbonazzo@redhat.com <mailto:sbonazzo@redhat.com>> wrote:
Il 20/05/2013 10:02, Dan Kenigsberg ha scritto: > On Mon, May 20, 2013 at 10:34:35AM +0300, Itamar Heim wrote: >> On 05/20/2013 10:01 AM, Sandro Bonazzola wrote: >>> Il 17/05/2013 17:48, Itamar Heim ha scritto: >>>> On 05/17/2013 06:01 PM, Sandro Bonazzola wrote: >>>>> Hi, >>>>> looking at the logs seems you're trying to install all-in-one on a >>>>> host that doesn't support virtualization: >>>>> >>>>> 2013-05-17 07:57:56,749 ERROR >>>>> [org.ovirt.engine.core.bll.InstallerMessages] (VdsDeploy) Installation >>>>> ovirt.wilk.local: Failed to execute stage 'Setup validation': Hardware >>>>> does not support virtualization >>>>> >>>>> This seems to be the reason for >>>>> >>>>> Error: Host was found in a 'Failed' state. >>>> wasn't this the first step in AIO - to validate this? >>>> >>> AIO ask libvirtd about supported cpus, this is the log about the cpu >>> validation: >>> >>> 2013-05-17 07:54:31::INFO::all_in_one_100::203::root:: libvirt service >>> is started >>> 2013-05-17 07:54:31::DEBUG::setup_sequences::59::root:: running >>> getSupportedCpus >>> 2013-05-17 07:54:31::DEBUG::all_in_one_100::393::root:: Attempting to >>> load the caps vdsm module >>> 2013-05-17 07:54:32::DEBUG::all_in_one_100::403::root:: Supported CPU >>> models are: >>> 2013-05-17 07:54:32::DEBUG::all_in_one_100::405::root:: model_athlon >>> 2013-05-17 07:54:32::DEBUG::all_in_one_100::405::root:: model_Opteron_G1 >>> 2013-05-17 07:54:32::DEBUG::setup_sequences::59::root:: running getCPUFamily >>> 2013-05-17 07:54:32::DEBUG::all_in_one_100::414::root:: Determening the >>> CPU family supported by the host >>> 2013-05-17 07:54:32::DEBUG::all_in_one_100::434::root:: comparing >>> model_Westmere with supported models >>> 2013-05-17 07:54:32::DEBUG::all_in_one_100::434::root:: comparing >>> model_Nehalem with supported models >>> 2013-05-17 07:54:32::DEBUG::all_in_one_100::434::root:: comparing >>> model_Penryn with supported models >>> 2013-05-17 07:54:32::DEBUG::all_in_one_100::434::root:: comparing >>> model_Conroe with supported models >>> 2013-05-17 07:54:32::DEBUG::all_in_one_100::434::root:: comparing >>> model_Opteron_G3 with supported models >>> 2013-05-17 07:54:32::DEBUG::all_in_one_100::434::root:: comparing >>> model_Opteron_G2 with supported models >>> 2013-05-17 07:54:32::DEBUG::all_in_one_100::434::root:: comparing >>> model_Opteron_G1 with supported models >>> 2013-05-17 07:54:32::DEBUG::all_in_one_100::436::root:: Supported model >>> family is: AMD Opteron G1 >>> >>> so it passed cpu validation. >> ok, that's one part of cpu validation for the cpu model. VDSM (or >> the old bootstrap code) was also supposed to have one for VT >> enabled >> in bios. > The old bootstrap code indeed has virtEnabledInCpuAndBios(). > ovirt-host-deploy has a parallel VdsmEnv.CHECK_VIRT_HARDWARE > optional > check. > > HTH, > Dan.
Ok, I'll add this check in AIO plugin. Has anybody already opened a bug about this issue?
-- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com <http://redhat.com>
Il 20/05/2013 15:46, Ryan Wilkinson ha scritto:
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..
Your CPU passed validation during setup checking because it is a supported model but it seems that virtualization technology of your cpu is disabled by BIOS settings. Can you check you bios settings and enable virtualization support? -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com
Il 20/05/2013 11:05, Sandro Bonazzola ha scritto:
Il 20/05/2013 10:02, Dan Kenigsberg ha scritto:
On Mon, May 20, 2013 at 10:34:35AM +0300, Itamar Heim wrote:
Il 17/05/2013 17:48, Itamar Heim ha scritto:
On 05/17/2013 06:01 PM, Sandro Bonazzola wrote:
Hi, looking at the logs seems you're trying to install all-in-one on a host that doesn't support virtualization:
2013-05-17 07:57:56,749 ERROR [org.ovirt.engine.core.bll.InstallerMessages] (VdsDeploy) Installation ovirt.wilk.local: Failed to execute stage 'Setup validation': Hardware does not support virtualization
This seems to be the reason for
Error: Host was found in a 'Failed' state. wasn't this the first step in AIO - to validate this?
AIO ask libvirtd about supported cpus, this is the log about the cpu validation:
2013-05-17 07:54:31::INFO::all_in_one_100::203::root:: libvirt service is started 2013-05-17 07:54:31::DEBUG::setup_sequences::59::root:: running getSupportedCpus 2013-05-17 07:54:31::DEBUG::all_in_one_100::393::root:: Attempting to load the caps vdsm module 2013-05-17 07:54:32::DEBUG::all_in_one_100::403::root:: Supported CPU models are: 2013-05-17 07:54:32::DEBUG::all_in_one_100::405::root:: model_athlon 2013-05-17 07:54:32::DEBUG::all_in_one_100::405::root:: model_Opteron_G1 2013-05-17 07:54:32::DEBUG::setup_sequences::59::root:: running getCPUFamily 2013-05-17 07:54:32::DEBUG::all_in_one_100::414::root:: Determening the CPU family supported by the host 2013-05-17 07:54:32::DEBUG::all_in_one_100::434::root:: comparing model_Westmere with supported models 2013-05-17 07:54:32::DEBUG::all_in_one_100::434::root:: comparing model_Nehalem with supported models 2013-05-17 07:54:32::DEBUG::all_in_one_100::434::root:: comparing model_Penryn with supported models 2013-05-17 07:54:32::DEBUG::all_in_one_100::434::root:: comparing model_Conroe with supported models 2013-05-17 07:54:32::DEBUG::all_in_one_100::434::root:: comparing model_Opteron_G3 with supported models 2013-05-17 07:54:32::DEBUG::all_in_one_100::434::root:: comparing model_Opteron_G2 with supported models 2013-05-17 07:54:32::DEBUG::all_in_one_100::434::root:: comparing model_Opteron_G1 with supported models 2013-05-17 07:54:32::DEBUG::all_in_one_100::436::root:: Supported model family is: AMD Opteron G1
so it passed cpu validation. ok, that's one part of cpu validation for the cpu model. VDSM (or
On 05/20/2013 10:01 AM, Sandro Bonazzola wrote: the old bootstrap code) was also supposed to have one for VT enabled in bios. The old bootstrap code indeed has virtEnabledInCpuAndBios(). ovirt-host-deploy has a parallel VdsmEnv.CHECK_VIRT_HARDWARE optional check.
HTH, Dan. Ok, I'll add this check in AIO plugin.
Done, see http://gerrit.ovirt.org/15013 -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com
participants (5)
-
Alon Bar-Lev -
Dan Kenigsberg -
Itamar Heim -
Ryan Wilkinson -
Sandro Bonazzola