----- Original Message ----- > From: "Lucas Meneghel Rodrigues" <[email protected]> > To: "autotest" <[email protected]> > Cc: "Vimal Patel" <[email protected]>, "Vaclav Ehrlich" > <[email protected]>, [email protected] > Sent: Thursday, July 26, 2012 5:02:09 PM > Subject: Fix for issue #441 cherry picked to master > > Hi guys, > > I hope I got the email addresses right, since the spice guys are > still > not on the autotest upstream mailing list :) Yep, you got them right, pulled, we will give it a try, Thanks! (And yes according to description in the issue #441 It looks like the issue we are facing).
>Anyhow, I've cherry > picked: > > commit 94f9ca422a4ee7027330bf1e582a5aec67c7e751 > Author: Lucas Meneghel Rodrigues <[email protected]> > Date: Mon Jul 23 19:31:41 2012 -0300 > > virt.kvm_vm: Add nw interfaces to bridge unconditionally > > This is a solution for issue #441. > > In kvm_vm.create(), the process of attaching each one > of the nics on kvm_vm.virtnet currently happens only > if the nic doesn't have a tapfd key. However, on test > failure (and consequent vm destruction), this field > will continue to be filled up, therefore a new connection > to the bridge will never be stablished, making all > subsequent tests to fail. > > However, the old networking code used to stablish the > network interface-bridge connection regardless of the > state of the nic, when create() is called. Applying the > same logic proved to be an effective solution for the > problem, therefore it's implemented on this patch. > > CC: Chris Evich <[email protected]> > CC: Lukas Doktor <[email protected]> > Signed-off-by: Lucas Meneghel Rodrigues <[email protected]> > > Into master, so the spice guys can fix the issues they were having > with > their virt tests. Next was rebased against master accordingly. > > Cheers, > > Lucas > > _______________________________________________ Autotest mailing list [email protected] http://test.kernel.org/cgi-bin/mailman/listinfo/autotest
