Dear oVirt Community, It appears that oVirt self-hosted engine does not support network configurations based on systemd-networkd? Am I correct? Does oVirt self-hosted engine deployment support VXLAN interface to configure "ovirtmgmt" on top of it? My setup: - three bare-metal servers: two of them are CentOS 7 based, clean installation. the third one is Ubuntu based served as a storage. - all three of them have public Internet connectivity, via basic Ethernet. - in order to emulate internal network, VXLAN was configured between those three. Mainly for testing purposes. - network configuration was done using systemd-networkd, internal communications worked fine. - DNS server was configured on this internal network. worked as direct/reverse resolver. Thus, the main host which I tried to convert to self-hosted engine following https://www.ovirt.org/documentation/self-hosted/chap-Deploying_Self-Hosted_E... guide, has the following network interfaces (redacted): - eth0, static IPv4, connected to the Internet; - vxlan0, on top of eth0, has private IPv4, 192.168.200.1; - hosts names resolve via private VXLAN network using 192.168.200.254. I started deployment saying that: Engine FQDN:ovirt-e1.example.com Network Configuration:Static VM IP Address:192.168.200.250/24 Gateway Address:192.168.200.1 DNS Servers:192.168.200.254 hostname of this host on the management network: ovirt-h1.example.com Deployment fails with error "Host ovirt-h1.example.com installation failed. Failed to configure management network on the host." After failure the system (host) does not have "ovirtmgmt" bridge. The same situation was when the host moved from networkd configuration to "network-scripts" (with VXLAN support added). I suspect that the root cause of the problem is that ansible scenarios were not able to create "ovirtmgmt" bridge on top of vxlan0. No switching to VLAN-based management interface... (did not actually tried yet).