QA:Testcase Virtualization XenDomU Network

From FedoraProject

(Difference between revisions)
Jump to: navigation, search
Line 3: Line 3:
 
|actions=
 
|actions=
 
# From the dom0, attach a new virbr0 type interface to the rawhide domU <pre>$> virsh attach-interface rawhide bridge virbr0</pre>
 
# 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. It will probably be eth1, assuming you already had eth0 setup from installation.
+
# Inside the guest run <pre>$> ifconfig</pre>  You should be able to see it. It will probably be eth1, assuming you already had eth0 setup from installation.
# Trying pinging the gateway from it <pre>$> ifconfig eth1 192.168.122.10 netmask 255.255.255.0
+
# 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>
$> 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 [--mac <mac>]</pre> If you don't specify the mac address you may remove eth0 instead.
# From the dom0, disconnect the interface from the rawhide guest <pre>$> virsh detach-interface rawhide bridge [--mac <mac>]</pre> If you don't specify the mac address, then you may remove eth0 instead.
+
 
# 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>
 
# 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>
# Now repeat the steps but with type xenbr0, i.e. use <pre>$> virsh attach-interface rawhide bridge xenbr0</pre> to attach.
+
# Now you can repeat the steps but with type xenbr0, that is using <pre>$> virsh attach-interface rawhide bridge xenbr0</pre>. Note, this will require you configure the interface differently, possibly with dhcp. That's most easily done with the ifup/down scripts in /etc/sysconfig/network-scripts.
 
|results=
 
|results=
 
# The network devices should be presented to the domU on attach-interface, and removed from the guest on detach-interface.
 
# The network devices should be presented to the domU on attach-interface, and removed from the guest on detach-interface.

Revision as of 20:43, 16 September 2009

Description

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


How to test

  1. From the dom0, attach a new virbr0 type interface to the rawhide domU
    $> virsh attach-interface rawhide bridge virbr0
  2. Inside the guest run
    $> ifconfig
    You should be able to see it. It will probably be eth1, assuming you already had eth0 setup from installation.
  3. 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
  4. From the dom0, disconnect the interface from the rawhide guest
    $> virsh detach-interface rawhide bridge [--mac <mac>]
    If you don't specify the mac address you may remove eth0 instead.
  5. Try adding at least 16 with something like this
    $> for i in `seq 1 15` ; do virsh attach-interface rawhide bridge virbr0 ; done
  6. Now you can repeat the steps but with type xenbr0, that is using
    $> virsh attach-interface rawhide bridge xenbr0
    . Note, this will require you configure the interface differently, possibly with dhcp. That's most easily done with the ifup/down scripts in /etc/sysconfig/network-scripts.

Expected Results

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