My Oracle Support Banner

OLVM: KVM Host Periodically Reports 'Not Responding' (Doc ID 2704306.1)

Last updated on AUGUST 31, 2020

Applies to:

Linux OS - Version Oracle Linux 7.7 with Unbreakable Enterprise Kernel [4.14.35] and later
Linux x86-64

Symptoms

Engine log reports below error:

2020-08-14 08:55:06,067+09 ERROR [org.ovirt.engine.core.bll.StopVmCommand] (EE-ManagedThreadFactory-engine-Thread-42) [887f9085-cc16-428c-9da5-23ece446c9f8] Command 'org.ovirt.engine.core.bll.StopVmCommand' 
failed: EngineException: org.ovirt.engine.core.vdsbroker.vdsbroker.VDSNetworkException: VDSGenericException: <strong>VDSNetworkException: Message timeout which can be caused by communication issues 
 (Failed with error VDS_NETWORK_ERROR and code 5022)</strong>
2020-08-14 08:55:06,067+09 WARN [org.ovirt.engine.core.vdsbroker.VdsManager] (EE-ManagedThreadFactory-engine-Thread-11) [887f9085-cc16-428c-9da5-23ece446c9f8] <strong>Host 'KVM_Host' is not responding.
</strong>
2020-08-14 08:55:07,424+09 INFO [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (EE-ManagedThreadFactory-engineScheduled-Thread-100) [20506ffd] EVENT_ID: VDS_DETECTED(13),
<strong>Status of host KVM_Host was set to Connecting.</strong>
2020-08-14 08:55:36,341+09 INFO [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (EE-ManagedThreadFactory-engineScheduled-Thread-89) [6ba94f96] EVENT_ID: VDS_DETECTED(13), 
<strong>Status of host KVM_Host was set to Up.</strong>
...
2020-08-14 09:10:21,717+09 ERROR [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (EE-ManagedThreadFactory-engine-Thread-47) [475b6daa-ad60-400c-8301-4802a2b435c4] EVENT_ID: 
VDS_BROKER_COMMAND_FAILURE(10,802), VDSM KVM_Host command DestroyVDS failed: <strong>Message timeout which can be caused by communication issues</strong>
2020-08-14 09:10:21,717+09 ERROR [org.ovirt.engine.core.bll.StopVmCommand] (EE-ManagedThreadFactory-engine-Thread-47) [475b6daa-ad60-400c-8301-4802a2b435c4] Command 'org.ovirt.engine.core.bll.StopVmCommand' 
failed: EngineException: org.ovirt.engine.core.vdsbroker.vdsbroker.VDSNetworkException: VDSGenericException: VDSNetworkException: <strong>Message timeout which can be caused by communication issues 
(Failed with error VDS_NETWORK_ERROR and code 5022)</strong>
2020-08-14 09:10:21,717+09 WARN [org.ovirt.engine.core.vdsbroker.VdsManager] (EE-ManagedThreadFactory-engine-Thread-48) [475b6daa-ad60-400c-8301-4802a2b435c4] <strong>Host 'KVM_Host' is not responding.</strong>
2020-08-14 09:10:21,719+09 WARN [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (EE-ManagedThreadFactory-engine-Thread-48) [475b6daa-ad60-400c-8301-4802a2b435c4] 
EVENT_ID: VDS_HOST_NOT_RESPONDING(9,027), Host KVM_Host is not responding. Host cannot be fenced automatically because power management for the host is disabled.
2020-08-14 09:10:52,409+09 INFO [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (EE-ManagedThreadFactory-engineScheduled-Thread-56) [49f39be8] EVENT_ID: VDS_DETECTED(13), 
<strong>Status of host KVM_Host was set to Up.</strong>

Cause

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


In this Document
Symptoms
Cause
Solution
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.