[ovirt-users] Single-machine hosted-engine routing is not working

Hello, I have oVirt 4.4 (latest that can be installed on RockyLinux 8.5) running on a laptop with a self-hosted engine. The setup was working fine after installation, but once I rebooted (after having shut down all the VMs including the hosted engine), I can no longer reach the oVirt console from any other computer on the same subnet. The hosted engine does respond to ping from the host machine. Logging onto the hosted engine from the serial console and I can only ping the host machine. Any other address on the subnet is unreachable. This seems to be some internal oVirt routing issue between the host and the virtual machine since stopping the firewall service makes no difference, neither on the host nor the hosted engine. The host address is 192.168.42.2 and the hosted engine is 192.168.42.250. broker.log says: engine_health::246::engine_health.EngineHealth::(_result_from_stats) VM is up on this host with healthy engine cpu_load_no_engine::142::cpu_load_no_engine.CpuLoadNoEngine::(calculate_load) System load total=0.0250, engine=0.0028, non-engine=0.0222 network::88::network.Network::(action) Successfully verified network status mem_free::51::mem_free.MemFree::(action) memFree: 26884 mgmt_bridge::65::mgmt_bridge.MgmtBridge::(action) Found bridge ovirtmgmt in up state engine_health::246::engine_health.EngineHealth::(_result_from_stats) VM is up on this host with healthy engine agent.log says: states::406::ovirt_hosted_engine_ha.agent.hosted_engine.HostedEngine::(consume) Engine vm running on localhost hosted_engine::517::ovirt_hosted_engine_ha.agent.hosted_engine.HostedEngine::(_monitoring_loop) Current state EngineUp (score: 3400) ovn-controller.log says: reconnect|INFO|ssl:192.168.42.250:6642: connected ofctrl|INFO|unix:/var/run/openvswitch/br-int.mgmt: connecting to switch rconn|INFO|unix:/var/run/openvswitch/br-int.mgmt: connecting... rconn|INFO|unix:/var/run/openvswitch/br-int.mgmt: connected pinctrl(ovn_pinctrl0)|INFO|unix:/var/run/openvswitch/br-int.mgmt: connecting to switch rconn(ovn_pinctrl0)|INFO|unix:/var/run/openvswitch/br-int.mgmt: connecting... rconn(ovn_pinctrl0)|INFO|unix:/var/run/openvswitch/br-int.mgmt: connected ovs-vswitchd.log says: connmgr|INFO|br-int: added service controller "punix:/var/run/openvswitch/br-int.mgmt" bridge|INFO|ovs-vswitchd (Open vSwitch) 2.11.8 memory|INFO|68900 kB peak resident set size after 10.0 seconds memory|INFO|handlers:5 ofconns:2 ports:1 revalidators:3 rules:9 connmgr|INFO|br-int<->unix#0: 6 flow_mods 10 s ago (5 adds, 1 deletes) The only actual error on the host is in ovsdb-server.log: jsonrpc|WARN|unix#13: receive error: Connection reset by peer reconnect|WARN|unix#13: connection dropped (Connection reset by peer) What else should I look at in order to figure out why the host no longer routes packets correctly from and to the hosted engine? Poltsi