1. These messages are appearing when the hypervisor is booting and up to now they have not caused any failure.
<snip>
libvirt: Network Driver error : Network not found: no network with matching name 'vdsm-203'
libvirt: Network Driver error : Network not found: no network with matching name 'vdsm-324'
libvirt: Network Driver error : Network not found: no network with matching name 'vdsm-195'
libvirt: Network Driver error : Network not found: no network with matching name 'vdsm-208'
libvirt: Network Driver error : Network not found: no network with matching name 'vdsm-330'
libvirt: Network Driver error : Network not found: no network with matching name 'vdsm-333'
libvirt: Network Driver error : Network not found: no network with matching name 'vdsm-192'
libvirt: Network Driver error : Network not found: no network with matching name 'vdsm-193'
libvirt: Network Driver error : Network not found: no network with matching name 'vdsm-229'
libvirt: Network Driver error : Network not found: no network with matching name 'vdsm-8'
libvirt: Network Driver error : Network not found: no network with matching name 'vdsm-100'
libvirt: Network Driver error : Network not found: no network with matching name 'vdsm-328'
libvirt: Network Driver error : Network not found: no network with matching name 'vdsm-221'
libvirt: Network Driver error : Network not found: no network with matching name 'vdsm-46'
libvirt: Network Driver error : Network not found: no network with matching name 'vdsm-rhevm'
libvirt: Network Driver error : Network not found: no network with matching name 'vdsm-29'
libvirt: Network Driver error : Network not found: no network with matching name 'vdsm-356'
libvirt: Network Driver error : Network not found: no network with matching name 'vdsm-3'
libvirt: Network Driver error : Network not found: no network with matching name 'vdsm-2'
libvirt: Network Driver error : Network not found: no network with matching name 'vdsm-5'
libvirt: Network Driver error : Network not found: no network with matching name 'vdsm-341'
libvirt: Network Driver error : Network not found: no network with matching name 'vdsm-368'
libvirt: Network Driver error : Network not found: no network with matching name 'vdsm-6'
libvirt: Network Driver error : Network not found: no network with matching name 'vdsm-9'
libvirt: Network Driver error : Network not found: no network with matching name 'vdsm-340'
libvirt: Network Driver error : Network not found: no network with matching name 'vdsm-188'
libvirt: Network Driver error : Network not found: no network with matching name 'vdsm-358'
libvirt: Network Driver error : Network not found: no network with matching name 'vdsm-361'
</snip>
2. Below messages in supervdsm.log :
<snip>
MainProcess|Thread-20::DEBUG::2015-08-11 08:57:27,631::libvirtconnection::143::root::(wrapper) Unknown libvirterror: ecode: 43 edom: 19 level: 2 message: Network not found: no network with matching name 'vdsm-rhevm'
MainProcess|Thread-39::DEBUG::2015-08-11 09:09:08,536::libvirtconnection::143::root::(wrapper) Unknown libvirterror: ecode: 43 edom: 19 level: 2 message: Network not found: no network with matching name 'vdsm-203'
.
.
.
.
MainThread::DEBUG::2015-09-29 14:09:26,331::libvirtconnection::143::root::(wrapper) Unknown libvirterror: ecode: 43 edom: 19 level: 2 message: Network not found: no network with matching name 'vdsm-358'
MainThread::DEBUG::2015-09-29 14:09:26,669::libvirtconnection::143::root::(wrapper) Unknown libvirterror: ecode: 43 edom: 19 level: 2 message: Network not found: no network with matching name 'vdsm-361'
</snip>
(In reply to Dan Kenigsberg from comment #7)
> Eddy, I believe that with your libvirt-db-removal patches, this little
> nastiness is finally gone. right?
Yes, it should no longer happen in the context of supervdsm.
We now just read existing defined networks from libvirt in order to 'upgrade' the configuration and clean them when we are done.
Only virt creates now libvirt networks and these networks lifetime is bound to the vnics connected to them.