Cole Robinson
Sat, 30 Jan 2010 17:19:12 -0800
Hi, Dumping the live config of an empty bridge seems a bit off:
$ sudo ncftool ncftool> list eth0 foobar lo ncftool> dumpxml foobar <?xml version="1.0"?> <interface type="bridge" name="foobar"> <start mode="onboot"/> <bridge/> </interface> ncftool> dumpxml --live foobar <?xml version="1.0"?> <interface name="foobar" type="bridge"/> The lack of a <bridge> section upsets libvirt here: $ sudo virsh iface-dumpxml foobar error: XML description for bridge interface misses the bridge element is not well formed or invalid Also, I think it would be nice if --live started with the inactive interface config and added/updated info from there. For example, the <start> block is only listed for the inactive config: this means an app would need query both the inactive and live config to get a complete listing of the interface's settings. Seems like this could easily be done at the netcf level, and is more or less how libvirt works for active vs. inactive domain configs (obviously netcf isn't tied to libvirt, just trying to point out some precedent). Thanks, Cole _______________________________________________ netcf-devel mailing list netcf-devel@lists.fedorahosted.org https://fedorahosted.org/mailman/listinfo/netcf-devel