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
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
On 01/06/2011 10:14 AM, 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
On 01/05/2011 01:10 AM, Laine Stump wrote:
On 01/04/2011 06:44 PM, Stefan Berger wrote:
v2:
- added test cases using 'ip addr ...' and 'ip route ...' commands
This patch adds a couple of test cases for the recently added network
ipv6 support.
I don't really feel qualified to do a good
v2:
- added test cases using 'ip addr ...' and 'ip route ...' commands
This patch adds a couple of test cases for the recently added network
ipv6 support.
Signed-off-by: Stefan Bergerstef...@us.ibm.com
---
scripts/networks/networkxml2hostout/tck-testnet-3.dat | 39 +
On 01/04/2011 06:44 PM, Stefan Berger wrote:
v2:
- added test cases using 'ip addr ...' and 'ip route ...' commands
This patch adds a couple of test cases for the recently added network
ipv6 support.
I don't really feel qualified to do a good review of patches for
libvirt-tck, but since
