On Fri, Apr 17, 2009 at 01:12:26PM +0200, Soren Hansen wrote:
On Fri, Apr 17, 2009 at 10:45:19AM +0100, Daniel P. Berrange wrote:
The problem with this approach is that the bridge name potentially ends up being different every time the virtual network is started. The bridge name needs to be stable, Why? I can't remember ever having to refer to it, and if I did, I can get that information at runtime by parsing the output from "virsh net-dumpxml <name of the network>". What am I not thinking of? :) The non-QEMU drivers I'm afraid.
Ah, I see. I've not spent much time with those. Longer term, would it perhaps make sense to let them specify the name of the network they want to use like we do for the QEMU driver? [...] Updated patch:
Okay makes sense, I just had to fix a couple of Tabs but it's in CVS, thanks ! Daniel -- Daniel Veillard | libxml Gnome XML XSLT toolkit http://xmlsoft.org/ daniel@veillard.com | Rpmfind RPM search engine http://rpmfind.net/ http://veillard.com/ | virtualization library http://libvirt.org/