Bug 244693
| Summary: | Network device selection fails during new VM creation process | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Adam Huffman <bloch> | ||||
| Component: | virt-manager | Assignee: | Daniel Berrangé <berrange> | ||||
| Status: | CLOSED NOTABUG | QA Contact: | Martin Jenner <mjenner> | ||||
| Severity: | medium | Docs Contact: | |||||
| Priority: | low | ||||||
| Version: | 7 | CC: | crobinso | ||||
| Target Milestone: | --- | ||||||
| Target Release: | --- | ||||||
| Hardware: | x86_64 | ||||||
| OS: | Linux | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2008-03-12 20:10:43 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: |
|
||||||
|
Description
Adam Huffman
2007-06-18 15:45:16 UTC
Created attachment 157290 [details]
Image of network device page
If the 'Shared physical device' list doesn't have any devices listed, then none of your ethernet devices are members of a bridge. If you are using Xen, then the network-bridge script will make eth0 part of a bridge. The recommended way is to use the regular network scripts though. In /etc/sysconfig/network-scripts: the file ifcfg-peth0 should define the physical device, with something like DEVICE=peth0 ONBOOT=yes BRIDGE=eth0 HWADDR=XX:XX:XX:XX:XX:XX and the file ifcfg-eth0 should be defining the bridge device to which the physical device is enslaved: DEVICE=eth0 BOOTPROTO=dhcp ONBOOT=yes TYPE=Bridge If you have already got eth0 enslaved in a bridge & virt-manager dosn't work, please provide ifconfig -a and brctl show output. Should this 'ifcfg-peth0' file have been created automatically? I do have a
virbr0 device, but nothing appears to be using it:
eth0 Link encap:Ethernet HWaddr 00:18:8B:1D:9A:CB
inet addr:xx.xx.xx.xx Bcast:xx.xx.xx.255 Mask:255.255.255.0
inet6 addr: fe80::218:8bff:fe1d:9acb/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:1665844 errors:0 dropped:0 overruns:0 frame:0
TX packets:452804 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:471571008 (449.7 MiB) TX bytes:55414602 (52.8 MiB)
Interrupt:16
virbr0 Link encap:Ethernet HWaddr 00:00:00:00:00:00
inet addr:192.168.122.1 Bcast:192.168.122.255 Mask:255.255.255.0
inet6 addr: fe80::200:ff:fe00:0/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:56 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 b) TX bytes:10336 (10.0 KiB)
No, the default scripts in /etc/sysconfig/network-scripts do not setup eth0 in a bridged configuration. This is because bridging doesn't work for many scenarios (Wifi, networkmanager, any machines with dynamic networking in general), so the safe option is not to setup any bridged ethernet devs. The virbr0 is a simple NAT based transit for guest VMs whcih is safe to configure for out-of-box connectivity (virbr0 corresponds to "Virtual Networks" 'default' network in virt manager). That sounds fair enough, but shouldn't this be documented e.g. at http://fedoraproject.org/wiki/Docs/Fedora7VirtQuickStart? Or have I missed it? Incidentally, I've just tried using the 'default' network and that has crashed, but I think the problem is covered by other reports. change QA contact Hi, I'm closing this as NOTABUG since there doesn't seem to be an issue here. |