Hi *, on one of my hosts two libvirtd/qemu vms are up and running without any problem. One vm is a Windows 2016 domain controller, the other one an Exchange 2016 Server. The last days I installed docker on the same host, created and started one container just for testing purposes. Everything seemed to work ok. A few days later I had to reboot the host due to a new kernel. I got no error or warning messages in my journal, but after a few hours the domain controller complained that it couldn't replicate partitions with its partner running on a different machine, and Exchange server couldn't reach any domain controller. ping, tracert and other network tools could reach every other machine, though. It took me some time to find out, that the problems were caused by docker. After stopping docker, everything worked as expected again - all windows machines could reach their partners again. I disabled docker, rebootet again and started docker afterwards manually. This time everything worked ok with both libvirtd and docker machines/containers were both up and running. It turned out, that starting docker and docker containers before libvirtd and its vms is causing the above mentioned network problems, starting them the other way round everything is working ok. I couldn't find out, though, why this is happening. Looking at the firewall rules I couldn't find anything unusual. Any hint, what is going on here? TIA. Bye. Michael. -- Michael Hirmke -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org