Maybe this is the rathole cause? [root@medusa system]# systemctl status vdsmd.service ● vdsmd.service - Virtual Desktop Server Manager Loaded: loaded (/usr/lib/systemd/system/vdsmd.service; enabled; vendor preset: disabled) Active: active (running) since Fri 2021-01-15 10:53:56 EST; 5s ago Process: 32306 ExecStartPre=/usr/libexec/vdsm/vdsmd_init_common.sh --pre-start (code=exited, status=0/SUCCESS) Main PID: 32364 (vdsmd) Tasks: 77 (limit: 410161) Memory: 77.1M CGroup: /system.slice/vdsmd.service ├─32364 /usr/bin/python3 /usr/share/vdsm/vdsmd ├─32480 /usr/libexec/ioprocess --read-pipe-fd 44 --write-pipe-fd 43 --max-threads 10 --max-queued-requests 10 ├─32488 /usr/libexec/ioprocess --read-pipe-fd 50 --write-pipe-fd 49 --max-threads 10 --max-queued-requests 10 ├─32494 /usr/libexec/ioprocess --read-pipe-fd 55 --write-pipe-fd 54 --max-threads 10 --max-queued-requests 10 ├─32501 /usr/libexec/ioprocess --read-pipe-fd 61 --write-pipe-fd 60 --max-threads 10 --max-queued-requests 10 └─32514 /usr/libexec/ioprocess --read-pipe-fd 65 --write-pipe-fd 61 --max-threads 10 --max-queued-requests 10 Jan 15 10:53:55 medusa.penguinpages.local vdsmd_init_common.sh[32306]: vdsm: Running nwfilter Jan 15 10:53:55 medusa.penguinpages.local vdsmd_init_common.sh[32306]: vdsm: Running dummybr Jan 15 10:53:56 medusa.penguinpages.local vdsmd_init_common.sh[32306]: vdsm: Running tune_system Jan 15 10:53:56 medusa.penguinpages.local vdsmd_init_common.sh[32306]: vdsm: Running test_space Jan 15 10:53:56 medusa.penguinpages.local vdsmd_init_common.sh[32306]: vdsm: Running test_lo Jan 15 10:53:56 medusa.penguinpages.local systemd[1]: Started Virtual Desktop Server Manager. Jan 15 10:53:57 medusa.penguinpages.local vdsm[32364]: WARN MOM not available. Error: [Errno 111] Connection refused Jan 15 10:53:57 medusa.penguinpages.local vdsm[32364]: WARN MOM not available, KSM stats will be missing. Error: Jan 15 10:53:57 medusa.penguinpages.local vdsm[32364]: WARN Failed to retrieve Hosted Engine HA info, is Hosted Engine setup finished? Jan 15 10:53:59 medusa.penguinpages.local vdsm[32364]: WARN Not ready yet, ignoring event '|virt|VM_status|69ab4f82-1a53-42c8-afca-210a3a2715f1' args={'69ab4f82-1a53-42c8-afca-210a3a2715f1': {'status': 'Down', 'vmId': '69ab4f82-1a53> [root@medusa system]# I googled around and the hits talk about re-running engine.. is their some kind of flow diagram of how to get oVirt back on its feet if it dies like this? I feel like I am poking in the dark here.