You didn't mention your CPU type.
Best Regards,
Strahil Nikolov
В сряда, 16 септември 2020 г., 20:44:23 Гринуич+3, Michael Blanton
<mblanton(a)vnet.net> написа:
Wondering if there are any suggestions here before I wipe these nodes
and go back to another Hypervisor.
On 9/14/2020 12:59 PM, Michael Blanton wrote:
Thanks for the quick response.
Ansible task reports them as Xeon 5130.
According to Intel Ark these fall in the Woodcrest family, which is
older the Nehalem.
Obviously the CPUs support virtualization.
I also confirmed the required extensions from the oVirt documents.
# grep -E 'svm|vmx' /proc/cpuinfo | grep n
Question for my lab:
So is this a situation where "Woodcrest" is simply not in the dictionary?
Is there a way to manually add that or "force" it, just to get the
engine to deploy? That way I can kick the tires on oVirt while I
consider an upgrade to my lab systems. Knowing ahead of time that it is
a "hack" and unsupported.
Question for product:
If this is an unsupported CPU, shouldn't the installer/Hosted Engine
Deployment flag that at the beginning of the process, not 45 minutes
later when trying to move the already created VM to shared storage?
Thanks again
On 9/14/2020 12:45 PM, Edward Berger wrote:
> What is the CPU? I'm asking because you said it was old servers, and
> at some point oVirt started filtering out old CPU types which were no
> longer supported under windows. There was also the case where if a
> certain bios option wasn't enabled (AES?) a westmere(supported)
> reported as an older model(unsupported).
>
>
> On Mon, Sep 14, 2020 at 12:20 PM <mblanton(a)vnet.net
> <mailto:mblanton@vnet.net>> wrote:
>
> I am attempting a new oVirt install. I have two nodes installed
> (with oVirt Node 4.4). I have NFS shared storage for the hosted
> engine.
> Both nodes are Dell quad core Xeon CPUs with 32GB of RAM. Both have
> been hypervisors before, XCP-NG and Proxmox. However I'm very
> interested to learn oVirt now.
>
> The hosted engine deployment (through cockpit) fails during the
> "Finish" stage.
> I do see the initial files created on the NFS storage.
>
> [ INFO ] TASK [ovirt.hosted_engine_setup : Convert CPU model name]
> [ ERROR ] fatal: [localhost]: FAILED! => {"msg": "The task
includes
> an option with an undefined variable. The error was: 'dict object'
> has no attribute ''\n\nThe error appears to be in
>
>
'/usr/share/ansible/roles/ovirt.hosted_engine_setup/tasks/create_target_vm/01_create_target_hosted_engine_vm.yml':
>
> line 105, column 16, but may\nbe elsewhere in the file depending on
> the exact syntax problem.\n\nThe offending line appears to be:\n\n#
> - debug: var=server_cpu_dict\n ^ here\n\nThere appears to be both
> 'k=v' shorthand syntax and YAML in this task. Only one syntax may be
> used.\n"}
>
> 2020-09-13 17:39:56,507+0000 ERROR ansible failed {
> "ansible_host": "localhost",
> "ansible_playbook":
> "/usr/share/ovirt-hosted-engine-setup/ansible/trigger_role.yml",
> "ansible_result": {
> "_ansible_no_log": false,
> "msg": "The task includes an option with an undefined
> variable. The error was: 'dict object' has no attribute ''
> \n\nThe error appears to be in
>
>
'/usr/share/ansible/roles/ovirt.hosted_engine_setup/tasks/create_target_vm/01_create_targ
>
> et_hosted_engine_vm.yml': line 105, column 16, but may\nbe elsewhere
> in the file depending on the exact syntax problem.\
> n\nThe offending line appears to be:\n\n# - debug:
> var=server_cpu_dict\n ^ here\n\nThere appears to be bo
> th 'k=v' shorthand syntax and YAML in this task. Only one syntax may
> be used.\n"
> },
> "ansible_task": "Convert CPU model name",
> "ansible_type": "task",
> "status": "FAILED",
> "task_duration": 1
> }
>
> I can see the host engine is created and running locally on the node.
> I can event SSH into the HostedEngineLocal instance.
>
> [root@ovirt-node01]# virsh --readonly list
> Id Name State
> -----------------------------------
> 1 HostedEngineLocal running
>
>
> Looking at the "Convert CPU model name" task:
>
>
https://github.com/oVirt/ovirt-ansible-hosted-engine-setup/blob/master/ta...
>
>
>
<
https://github.com/oVirt/ovirt-ansible-hosted-engine-setup/blob/master/ta...
>
>
> set_fact:
> cluster_cpu_model: "{{ server_cpu_dict[cluster_cpu.type] }}"
>
> server_cpu_dict is good, I can find that in the logs, cluster_cpu is
> undefined.
> But this is normal correct? The Cluster CPU type is "undefined"
> until the first host is added to the cluster.
> The error makes it seems that server_cpu_dict and not
> cluster_cpu.type is the problem.
> I'm not sure this is really the problem, but that is the only
> undefined variable I can find.
>
> Any advice or recommendation is appreciated
> -Thanks in advance
> _______________________________________________
> Users mailing list -- users(a)ovirt.org <mailto:users@ovirt.org>
> To unsubscribe send an email to users-leave(a)ovirt.org
> <mailto:users-leave@ovirt.org>
> Privacy Statement:
https://www.ovirt.org/privacy-policy.html
> <
https://www.ovirt.org/privacy-policy.html>
> oVirt Code of Conduct:
>
https://www.ovirt.org/community/about/community-guidelines/
> <
https://www.ovirt.org/community/about/community-guidelines/>
> List Archives:
>
_______________________________________________
Users mailing list -- users(a)ovirt.org
To unsubscribe send an email to users-leave(a)ovirt.org
Privacy Statement:
https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct:
https://www.ovirt.org/community/about/community-guidelines/
List Archives:
_______________________________________________
Users mailing list -- users(a)ovirt.org
To unsubscribe send an email to users-leave(a)ovirt.org
Privacy Statement: