On Thu, Jan 06, 2011 at 08:14:01AM -0700, Eric Blake wrote: > On 01/05/2011 06:02 PM, Stefan Berger wrote: > >> Looks like I need to be careful where I run the libvirt-tck, as one of > >> the networks chosen for testing will clobber the route to an important > >> internal network (10.0.0.0/8) for the duration of the test. > > We could choose the private network 172.16.0.0/12 instead, if that helps > > for most people. > > Would it make sense to choose a subnet of one of the reserved private > ranges, to further reduce the likelihood of collisions; maybe something > like: > > 172.28.0.0/16 I think the choice of subnet should be added to the configuration file. A default of 127.28.0.0/16 is fine, as long as people can override it easily if it causes trouble. The Sys::Virt::TCK->generic_network method would then return you a Sys::Virt::TCK::NetworkBuilder instance with the ip details filled in from the config file. So all test cases should 'just work' if they use the convenience APIs for building network XML. Daniel -- libvir-list mailing list libvir-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/libvir-list