Bug 438809
| Summary: | virt-manager doesn't detect network bridge correctly | ||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Adam Tkac <atkac> | ||||||||||||||||||||
| Component: | virt-manager | Assignee: | Daniel Berrangé <berrange> | ||||||||||||||||||||
| Status: | CLOSED NOTABUG | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||||||||||||||||
| Severity: | low | Docs Contact: | |||||||||||||||||||||
| Priority: | low | ||||||||||||||||||||||
| Version: | 9 | CC: | crobinso, hbrock, ovasik | ||||||||||||||||||||
| Target Milestone: | --- | ||||||||||||||||||||||
| Target Release: | --- | ||||||||||||||||||||||
| Hardware: | All | ||||||||||||||||||||||
| OS: | Linux | ||||||||||||||||||||||
| Whiteboard: | |||||||||||||||||||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||||||||||||||||||
| Doc Text: | Story Points: | --- | |||||||||||||||||||||
| Clone Of: | Environment: | ||||||||||||||||||||||
| Last Closed: | 2008-05-27 11:01:29 UTC | Type: | --- | ||||||||||||||||||||
| Regression: | --- | Mount Type: | --- | ||||||||||||||||||||
| Documentation: | --- | CRM: | |||||||||||||||||||||
| Verified Versions: | Category: | --- | |||||||||||||||||||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||||||||||||||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||||||||||||||||||
| Embargoed: | |||||||||||||||||||||||
| Attachments: |
|
||||||||||||||||||||||
Hi, can you attach ~/.virt-manager/virt-manager.log? Thanks. It is nothing interesting there: [St, 02 led 2008 13:25:10 virt-manager 16569] INFO (virt-manager:125) Application startup [St, 02 led 2008 13:25:11 virt-manager 16570] DEBUG (engine:69) About to connect to uris [] It might be libvirt problem but I'm not able to track where exactly problem is. Any hints how get more useful debug information? There should be much more than that - please make sure you are connected to a hypervisor and have the new VM wizard open. Then capture the logfile & attach the whole file to this ticket. Created attachment 300051 [details]
log file
In previous attempt I looked into my home dir instead /root.
Can you attach the output of these commands: ls /sys/class/net/*/* ifconfig -a brctl show and also tell me what kernel you are running Created attachment 300402 [details]
brctl show
Created attachment 300403 [details]
ifconfig -a
Created attachment 300404 [details]
ls /sys/class/net/*/*
uname -rvm 2.6.25-0.185.rc7.git6.fc9.i686 #1 SMP Tue Apr 1 13:48:40 EDT 2008 i686 Created attachment 302725 [details]
Screenshot of virt-manager network selection
Argggg - original comment didn't attach! We are running into the same problem - we have two bridged networks, xenbr0 and xenbr1 - these are not being displayed correctly (or at all) in virt-manager, as you can see from the screenshot in the previous comment. kernel-2.6.18-53.1.14.el5xen virt-manager-0.4.0-3.el5 I will attach brctl, virt-manager.log and ifconfig -a output Created attachment 302726 [details]
Output of ls /sys/class/net/*/*
Created attachment 302727 [details]
Output of ifconfig -a
Created attachment 302728 [details]
Output of brctl show
Created attachment 302729 [details]
virt-manager.log
Comment #11, your log file indicates a known issue (see bug 436276). Changing version to '9' as part of upcoming Fedora 9 GA. More information and reason for this action is here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping After more investigation and some configuration hacking it works again, closing. |
Description of problem: When I want create guest with bridged network interface "Network device" field is gray (peth0 not bridged) but peth0 is network bridge Version-Release number of selected component (if applicable): $rpm -q virt-manager libvirt virt-manager-0.5.4-2.fc9.i386 libvirt-0.4.1-4.fc9.i386 How reproducible: always Steps to Reproduce: 1. setup network bridge through /etc/sysconfig/network-scripts/ifcfg-{peth0,eth0} 2. try create guest with bridged networking Actual results: Device field is gray and tells that peth0 is not bridged Expected results: not gray device Additional info: I'm using same configuration long time and this became broken during last month (I'm able to find when exactly). $ /usr/sbin/brctl show bridge name bridge id STP enabled interfaces peth0 8000.00188b2be4d9 no eth0 vnet0 When I run guest which was created some time ago networking works as expected (I'm able to ping guest from outside). Let me know if you need more info (network configuration etc)