Hm... then you need to play on a TEST ovirt with the options described in in https://www.ovirt.org/develop/developer-guide/engine/engine-config-options.h... Some of the more interesting options are: SSHInactivityTimoutSeconds TimeoutToResetVdsInSeconds VDSAttemptsToResetCount VdsRecoveryTimeoutInMintues VdsRefreshRate vdsTimeout Try them first in a test system before deploying on production. Best Regards, Strahil Nikolov В събота, 18 юли 2020 г., 10:40:14 Гринуич+3, lu.alfonsi@almaviva.it <lu.alfonsi@almaviva.it> написа: Hello, yes, root login is opened. No, I didn't make changes to the sshd_config The fact is that this issue happens from time to time. Let me give you more details: When the hosts go in "non responsive state", probably due to network errors, they remain in this state for a few hours. In the meantime, if we try to reach the hosts and the vm, we can connect to them correctly. So in my opinion, the ovirt manager, when it is not able to reach the hypervisors, set the server in the non responsive state, but it has issues when he tries to reconnect to it and to bring them up again. _______________________________________________ Users mailing list -- users@ovirt.org To unsubscribe send an email to users-leave@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: https://lists.ovirt.org/archives/list/users@ovirt.org/message/CTRGGZ3V46YMEL...