testdrive instances can't network to each other

Bug #595003 reported by sam tygier
12
This bug affects 2 people
Affects Status Importance Assigned to Milestone
TestDrive
Triaged
Wishlist
Unassigned

Bug Description

if i start 2 instances of test drive, they seem to each be on independent virtual networks. they both show in ifconfig
inet addr:10.0.2.15 Bcast:10.0.2.255 Mask:255.255.255.0
and even identical MAC address and IPV6 addresses

it would be great if each vm would appear to be on the same local network so that it is possible the test interaction between them.

Revision history for this message
Dustin Kirkland  (kirkland) wrote :

Confirming the bug, marking wishlist.

I have a solution to this, invovling bridging. However, it requires that kvm be launched with root priv's (or at least the bridging script be launched with root priv's). This isn't ideal, so I can't quite commit that to the branch yet.

However, I see your point and agree that it would be nice.

Changed in testdrive:
status: New → Triaged
importance: Undecided → Wishlist
Revision history for this message
sam tygier (samtygier) wrote :

could their be a --lan option. if you run 'testdive --lan' it will tell you that it needs root privileges, if you run 'sudo testdrive --lan' it works. and it would need to make sure it did not make any of the files it creates to be owned by root.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.