Revision as of 20:36, 16 September 2009

Description

This test case verifies that Xen DomU networking works correctly, including the ability to attach/detach network devices.

From the dom0, attach a new virbr0 type interface to the rawhide domU
```
$> virsh attach-interface rawhide bridge virbr0
```
Inside the guest, run
```
$> ifconfig
```
You should be able to see it. It will probably eth1, assuming you already had eth0 setup from installation.

Trying pinging the gateway from it

$>ifconfig eth1 192.168.122.10 netmask 255.255.255.0

$> ping -I eth1 -c 2 192.168.122.1

From the dom0, disconnect the interface from the rawhide guest
```
$> virsh detach-interface rawhide bridge
```

Try adding at least 16 with something like this

$>for i in `seq 1 15` ; do virsh attach-interface rawhide bridge virbr0 ; done

Now repeat the steps but with type xenbr0, i.e. use
```
$> virsh attach-interface rawhide bridge xenbr0
```
to attach.

The network devices should be presented to the domU on attach-interface, and removed from the guest on detach-interface.
The rawhide guest should be able to use the network interfaces.

@@ Line 3: / Line 3: @@
 |actions=
 # From the dom0, attach a new virbr0 type interface to the rawhide domU <pre>$> virsh attach-interface rawhide bridge virbr0</pre>
-# Inside the guest, run <pre>$> ifconfig</pre>  You should be able to see it.
+# Inside the guest, run <pre>$> ifconfig</pre>  You should be able to see it. It will probably eth1, assuming you already had eth0 setup from installation.
-# Trying pinging the gateway from it <pre>$> ping -I eth? -c 2 192.168.122.1 </pre>
+# Trying pinging the gateway from it <pre>$>ifconfig eth1 192.168.122.10 netmask 255.255.255.0</pre><pre>$> ping -I eth1 -c 2 192.168.122.1 </pre>
 # From the dom0, disconnect the interface from the rawhide guest <pre>$> virsh detach-interface rawhide bridge</pre>
 # Try adding at least 16 with something like this <pre>$>for i in `seq 1 15` ; do virsh attach-interface rawhide bridge virbr0 ; done</pre>