Hi Konstantin, thanks for the reply. So... I just used the ovirt-node-ng-installer-4.5.4-2022120615.el9.iso install... no patches, no additional packages. I set 16 vCPUs and 64GB to the engine VM in the deploy... just it. I will reinstall and test the workaround you mentioned. I'll keep you posted here.
BR. Em qua., 5 de jul. de 2023 às 11:36, Volenbovskyi, Konstantin < [email protected]> escreveu: > Hi, > > I gave certain pointers in > https://www.mail-archive.com/[email protected]/msg72371.html , but the > person who wrote initial question haven’t provided any updates > > > > Several thoughts around that: > > 1. you had several attempts (log file you attached contains attempts > from 4th of July and below events are from 5th of July) and somehow I > think that in attempt below you haven’t specified amount of vCPUs and it > took the value ‘max’ > > | he_vcpus | max | The amount of CPUs used on the engine VM | > > 1. based on what you see in > https://gitlab.com/libvirt/libvirt/-/issues/324 > I am pretty sure that you can disable cgroups v2 > > and you will be 100% sure that you are dealing with this fault/this might > be acceptable workaround > > > > 1. the Libvirt versions specified in the commit addressing that > > start with v9.0.0 > <https://gitlab.com/libvirt/libvirt/-/commits/v9.0.0?ref_type=tags> > > Hmm, so you use CentOS Stream 9 and > https://mirror.stream.centos.org/9-stream/AppStream/x86_64/os/Packages/ > it is Libvirt 9. > > But maybe Libvirt here comes from ovirt repo?... > > > > > > BR, > > Konstantin > > > > > > *Von: *Jorge Visentini <[email protected]> > *Datum: *Mittwoch, 5. Juli 2023 um 15:59 > *An: *users <[email protected]> > *Betreff: *[ovirt-users] ovirt 4.5.4 deploy self-hosted engine > > > > Hi. > > > > I'm trying to deploy the engine but I'm having some errors that I couldn't > identify. > I don't know if it's incompatibility with my hardware or some libvirt bug. > > > > Jul 05 10:06:21 ksmmi1r02ovirt36.kosmo.cloud > ansible-async_wrapper.py[690916]: 690917 still running (48505) > > Jul 05 10:06:21 ksmmi1r02ovirt36.kosmo.cloud libvirtd[701878]: Domain id=1 > name='HostedEngineLocal' uuid=922a156c-7f4c-4815-a645-54ed07 794451 is > tainted: custom-ga-command > > Jul 05 10:06:21 ksmmi1r02ovirt36.kosmo.cloud virtlogd[630980]: Client hit > max requests limit 1. This may result in keep-alive timeouts. Consider > tuning the max_client_requests server parameter > > Jul 05 10:06:22 ksmmi1r02ovirt36.kosmo.cloud libvirtd[701878]: Invalid > value '-1' for 'cpu.max': Invalid argument > > Jul 05 10:06:26 ksmmi1r02ovirt36.kosmo.cloud > ansible-async_wrapper.py[690916]: 690917 still running (48500) > > Jul 05 10:06:31 ksmmi1r02ovirt36.kosmo.cloud > ansible-async_wrapper.py[690916]: 690917 still running (48495) > > Jul 05 10:06:31 ksmmi1r02ovirt36.kosmo.cloud systemd[1]: > systemd-timedated.service: Deactivated successfully. > > Jul 05 10:06:36 ksmmi1r02ovirt36.kosmo.cloud > ansible-async_wrapper.py[690916]: 690917 still running (48490) > > Jul 05 10:06:37 ksmmi1r02ovirt36.kosmo.cloud libvirtd[701878]: Invalid > value '-1' for 'cpu.max': Invalid argument > > Jul 05 10:06:41 ksmmi1r02ovirt36.kosmo.cloud > ansible-async_wrapper.py[690916]: 690917 still running (48485) > > Jul 05 10:06:46 ksmmi1r02ovirt36.kosmo.cloud > ansible-async_wrapper.py[690916]: 690917 still running (48480) > > Jul 05 10:06:51 ksmmi1r02ovirt36.kosmo.cloud > ansible-async_wrapper.py[690916]: 690917 still running (48475) > > Jul 05 10:06:52 ksmmi1r02ovirt36.kosmo.cloud libvirtd[701878]: Invalid > value '-1' for 'cpu.max': Invalid argument > > Jul 05 10:06:56 ksmmi1r02ovirt36.kosmo.cloud > ansible-async_wrapper.py[690916]: 690917 still running (48470) > > Jul 05 10:07:01 ksmmi1r02ovirt36.kosmo.cloud > ansible-async_wrapper.py[690916]: 690917 still running (48465) > > > > *My config:* > > *CPU:* 2 x Intel(R) Xeon(R) Platinum 8276M CPU @ 2.20GHz > > *Memory:* 4TB > > *Disk:* 120GB RAID 1 > > *ISO:* ovirt-node-ng-installer-4.5.4-2022120615.el9.iso > > > > *Packages:* > > kernel-5.14.0-202.el9.x86_64 > > libvirt-8.9.0-2.el9.x86_64 > > centos-release-ovirt45-9.1-3.el9s.noarch > > python3-ovirt-engine-sdk4-4.6.0-1.el9.x86_64 > > ovirt-imageio-common-2.4.7-1.el9.x86_64 > > ovirt-imageio-client-2.4.7-1.el9.x86_64 > > ovirt-openvswitch-ovn-2.15-4.el9.noarch > > ovirt-openvswitch-ovn-common-2.15-4.el9.noarch > > ovirt-imageio-daemon-2.4.7-1.el9.x86_64 > > ovirt-openvswitch-ovn-host-2.15-4.el9.noarch > > python3-ovirt-setup-lib-1.3.3-1.el9.noarch > > ovirt-vmconsole-1.0.9-1.el9.noarch > > ovirt-vmconsole-host-1.0.9-1.el9.noarch > > ovirt-openvswitch-2.15-4.el9.noarch > > python3-ovirt-node-ng-nodectl-4.4.2-1.el9.noarch > > ovirt-node-ng-nodectl-4.4.2-1.el9.noarch > > ovirt-ansible-collection-3.0.0-1.el9.noarch > > ovirt-python-openvswitch-2.15-4.el9.noarch > > ovirt-openvswitch-ipsec-2.15-4.el9.noarch > > ovirt-hosted-engine-ha-2.5.0-1.el9.noarch > > ovirt-provider-ovn-driver-1.2.36-1.el9.noarch > > ovirt-host-dependencies-4.5.0-3.el9.x86_64 > > ovirt-hosted-engine-setup-2.7.0-1.el9.noarch > > ovirt-host-4.5.0-3.el9.x86_64 > > ovirt-release-host-node-4.5.4-1.el9.x86_64 > > ovirt-node-ng-image-update-placeholder-4.5.4-1.el9.noarch > > ovirt-engine-appliance-4.5-20221206125848.1.el9.x86_64 > > > For better understanding, the deploy log is attached. > I appreciate any tips that help me. > > > > Thank you! > > -- > > Att, > > Jorge Visentini > +55 55 98432-9868 > -- Att, Jorge Visentini +55 55 98432-9868
_______________________________________________ Users mailing list -- [email protected] To unsubscribe send an email to [email protected] Privacy Statement: https://www.ovirt.org/privacy-policy.html oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/[email protected]/message/X37O7ZCX26JX65V64C53AVW7BJ2UQ3JF/
