On 06/01/2011, at 8:26 PM, Daniel Huhardeaux wrote: > Hello, > > got no reaction on this, I try again :-) Hmmm, just thought of a workaround if it helps. :) You already know that when libvirtd starts, it automatically starts the virtual networks that it has been told to. But, if you then shut libvirtd down, they're left running. So... my thought of a dodgy workaround is this... after libvirtd starts... and the virtual networks have started... restart libvirtd. I *think* that would then let libvirt bind to the new ip addresses. Reckon it's worth trying? Regards and best wishes, Justin Clift > > -------- Message original -------- > Sujet: libvirtd and listen_addr > Date : Sat, 01 Jan 2011 11:33:55 +0100 > De : Daniel Huhardeaux <tech@xxxxxxxxxx> > Pour : libvir-list@xxxxxxxxxx > > > > Hi, > > at first, best wishes to all for this new year. > > We have a request: would it be possible to start libvirtd listen_addr > *after* the VM network is up? > > We have VPN through different libvirt+kvm servers and want to virsh > connect to the private VM network address of each server instead of his > VPN IP. The problem is that libvirt doesn't start with unknown IP > address. If network would be already up, libvirt could listen on this > address. > > Regards > > libvirtd (libvirt) 0.8.3 - Debian stable + backports > -- > Daniel > > -- > libvir-list mailing list > libvir-list@xxxxxxxxxx > https://www.redhat.com/mailman/listinfo/libvir-list -- libvir-list mailing list libvir-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/libvir-list