As part of the work on vdsm side for bug #1779527 it has been requested to open a bug on engine for getting rid of the oVirt Guest Agent socket.
Moving to verified forth to https://bugzilla.redhat.com/show_bug.cgi?id=1779527#c36 and because I see that ovirt.guest-agent channel is not being used anymore on RHEL8.2. 2020-08-13 10:04:41,867+0300 INFO (qgapoller/3) [vds] Failed to get guest info for vm=1d909cba-7fb0-457e-a374-75787f9 b4c4d, error: Guest agent is not responding: QEMU guest agent is not connected (qemuguestagent:393) 2020-08-13 10:04:48,025+0300 INFO (periodic/2) [vdsm.api] START repoStats(domains=()) from=internal, task_id=c07db927 -cce6-43b9-9e08-f7b7b82a6677 (api:48) 2020-08-13 10:04:48,026+0300 INFO (periodic/2) [vdsm.api] FINISH repoStats return={'5b910efa-da4b-44ab-b347-933b9e964 412': {'code': 0, 'lastCheck': '7.2', 'delay': '0.0070304', 'valid': True, 'version': 5, 'acquired': True, 'actual': T rue}} from=internal, task_id=c07db927-cce6-43b9-9e08-f7b7b82a6677 (api:54) 2020-08-13 10:04:48,173+0300 INFO (libvirt/events) [virt.vm] (vmId='1d909cba-7fb0-457e-a374-75787f9b4c4d') underlying process disconnected (vm:1006) 2020-08-13 10:04:48,174+0300 INFO (libvirt/events) [virt.vm] (vmId='1d909cba-7fb0-457e-a374-75787f9b4c4d') Release VM resources (vm:4629) 2020-08-13 10:04:48,174+0300 INFO (libvirt/events) [virt.vm] (vmId='1d909cba-7fb0-457e-a374-75787f9b4c4d') Stopping c onnection (guestagent:444) 2020-08-13 10:04:48,174+0300 INFO (libvirt/events) [virt.vm] (vmId='1d909cba-7fb0-457e-a374-75787f9b4c4d') Stopping c onnection (guestagent:444) I can clearly see that QEMU guest agent is used now instead of ovirt.guest-agent. ovirt-hosted-engine-setup-2.4.6-1.el8ev.noarch ovirt-hosted-engine-ha-2.4.4-1.el8ev.noarch vdsm-4.40.25-1.el8ev.x86_64
This bugzilla is included in oVirt 4.4.2 release, published on September 17th 2020. Since the problem described in this bug report should be resolved in oVirt 4.4.2 release, it has been closed with a resolution of CURRENT RELEASE. If the solution does not work for you, please open a new bug report.