Test Day:2010-04-08 Virtualization NetworkInterface
From FedoraProject
| DATE | TIME | WHERE |
| Thursday Apr 08, 2010 | All day | #fedora-test-day (webchat) |
Contents |
[edit] What to test?
This part of today's Fedora Test Day will focus on network interface management using virt-manager.
Testing will focus on managing interface lifecycle (start and stop interfaces), creating new logical interfaces like bridges and bonds, and enumerate existing interfaces on the libvirt host. Also, it is unknown how well these test cases will interact with NetworkManager: any feedback on success or failure with NetworkManager running will be greatly appreciated.
If you come to this page after the test day is completed, your testing is still valuable, and you can use the information on this page to provide feedback.
See also: http://fedoraproject.org/wiki/Features/Shared_Network_Interface
[edit] Who's available
Cole Robinson is your host for today.
The following people have also agreed to be available for testing, workarounds, bug fixes, and general discussion:
- Eric Blake
- add your name here
[edit] What's needed to test
- A fully updated Fedora 13 testing machine (or 2). See instructions on the main test day page.
- A network card, and the option mess with networking!
[edit] Test Cases
Interface management with virt-manager is mostly exposed via: Edit->Host Details->Network Interfaces. We will call this the 'interface viewer'
- Starting and stopping an existing interface: Select an interface from the interface viewer, use the start and stop button on the bottom list to bring interfaces up and down.
- Bridging an existing interface: From the interface viewer, click the '+' button, and follow the on screen options to bridge an existing interface. Make sure to start the interface after finishing the creation step. WARNING: There is a known bug with creating bridges from existing interfaces: the IP configuration from the original interface will not be setup for the bridge (if the original eth0 was using dynamic IPv4, this is lost when bridging eth0). This is fixed in latest virt-manager which will be queued for F13 post GA, since it is a substantial backport.
- Enumerating bridges on a remote connection: After creating your bridge, connect to your local machine 'remotely'. You can do this via File->Add Connection from the main virt-manager windows: select connection type 'Remote tunnel over SSH', and use localhost for the hostname (this will require root SSH credentials). Once connected, start the 'New VM' wizard, fill in any values and navigate to the final page. Under advanced options, ensure that the newly created bridge device is listed as a network option. You do not need to actually kick off an install for this to be verified, so just use PXE as an install method and the wizard shouldn't complain.
- Create other logical network interfaces (bonds, vlans): Go wild with the 'New Interface' wizard, see if you can trigger any bugs or hit any unexpected issues.
[edit] Issues that were identified
| Tester | Description | Bug references | Status |
| #XXXXX | ASSIGNED |
