Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 883232

Summary: Need updated guide to bridged networking with libvirt
Product: [Retired] Fedora Documentation Reporter: Nick Coghlan <ncoghlan>
Component: virtualization-guideAssignee: Fedora Documentation Project <docs>
Status: CLOSED EOL QA Contact: Fedora Docs QA <docs-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: develCC: zach
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-11-07 15:30:14 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Nick Coghlan 2012-12-04 05:49:50 UTC 
Description of problem:

The most recent description of using bridged networking with libvirt seems to be from Fedora 13 (https://docs.fedoraproject.org/en-US/Fedora/13/html/Virtualization_Guide/sect-Virtualization-Network_Configuration-Bridged_networking_with_libvirt.html) (Found via https://encrypted.google.com/search?q=fedora%2017%20bridge%20network%20manager%20connection)

Aside from the "service iptables save" command being obsolete (https://lists.fedoraproject.org/pipermail/devel/2012-February/162757.html), this guide still mostly works. However, there's probably a better way by now (bridged networking is needed sometimes so that guests can PXE boot of the main network).
Comment 1 Petr Bokoc 2019-11-07 15:30:14 UTC 
I'm closing this bug as part of a Bugzilla cleanup effort. The most likely reason is that the bug has been opened either against a component we no longer publish, or against Release Notes for an EOL release.