Yes, I can confirm the problem occurs on 0.9.1-1. I don't think it's a local configuration problem. Network and Network online targets both are reached before the libvirtd.service starts. Indeed, libvirtd.service declares that it must run after Network target is achieved. But it then goes on to do things that appear to disrupt the network. I cannot establish for sure that these are what causes xrdp to fail to start without debugging xrdp, which I am not in a position to do.
It seems to me that Network target semantics are not rich or specific enough to cover the virtual host case completely - if so, this is an issue that is larger than xrdp of course. But knowing this, it also seems that xrdp could insulate itself against transient errors that might occur during initialization. Also, I imagine that the test cases for xrdp should include configurations where libvirtd is running. Hope that helps. Cheers, David
