<tt>Eric Blake <eblake@redhat.com> wrote on 05/11/2010 03:31:10 PM: </tt> <tt>> > On 05/07/2010 03:39 PM, Stefan Berger wrote: > > This is a repost of a previously posted patch. > > > > Attached is a test for automatic testing of of the nwfilter rules as the > > are instantiated in form of ebtables, iptables and ip6tables rules on > > running VMs. > > > > The test automatically starts libvirtd from the build directory unless > > it finds libvirtd running. My hope is that one won't notice this. It > > uses virsh from the build directory to create two dummy VMs with random > > name suffixes. The VMs don't boot any OS but just stop in the BIOS. This > > is enough to run the nwfilter tests. Afterwards the nwfilter of the one > > VM are continuously modified and the instantiation is checked. The > > instantiation of rules of the 2nd VM are also continously checked to > > verify that the modifications on the 1st VM has had no effect on the > > instantiated rules of the 2nd VM. > > I'm still a bit wary of this patch. Is this something that can be done > with 'virsh -c test:///default' can do? Or can we at least copy how</tt> <tt>test doesn't support the functionality, so no, it cannot be used like that.</tt> <tt> > daemon-conf runs an instance of libvirtd pointing to an independent pid > and config file, whether or not the system libvirtd is running?</tt> <tt>yes, I am looking into this.</tt> <tt> > > Or should we be trying to do this as part of libvirt-tck instead?</tt> <tt>I know. Hurdle being Perl for me and I so far have had lots of problems getting that test suite to run; some problems were related just to compile the dependent libvirt perl project, others then with a perl dependency and my FC13 installation etc.</tt> <tt> Stefan</tt> <tt> > > -- > Eric Blake eblake@redhat.com +1-801-349-2682 > Libvirt virtualization library </tt><a href=http://libvirt.org/><tt>http://libvirt.org</tt></a><tt> > > [attachment "signature.asc" deleted by Stefan Berger/Watson/IBM] </tt>