Bug 615439

Summary: Virt Guide Chap 11.1 NAT: Guest Configuration confusion
Product: [Fedora] Fedora Documentation Reporter: Ronald L Humble <deadletterfile>
Component: virtualization-guideAssignee: Fedora Documentation Project <docs>
Status: CLOSED EOL QA Contact: Nobody's working on this, feel free to take it <nobody>
Severity: low Docs Contact:
Priority: low    
Version: develCC: jhradile, me
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: 2019-11-07 15:30:18 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:

Description Ronald L Humble 2010-07-16 18:10:27 UTC 
Description of problem: Virtualization Guide F13: Chapter 11.1
Used virt-install to move a VM from f12 to f13...perhaps without needed switches. VM networking was inactive. Went to above chapter 11.1 and Host Configuration section was extremely clear and followed. 

Problem: I have no idea what to do with the Guest Configuration section. Instructions seem to indicate a XML file on the VM should be edited/added. 

Solution: I rebooted my host f13 machine after host configuration and VM networking functioned. My problem is solved. 


Version-Release number of selected component (if applicable):
http://doc.fedoraproject.org/en-US/Fedora/13/html-single/Virtualization_Guide/index.html

How reproducible:


Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info:
Comment 2 Karsten Wade 2011-12-14 03:49:24 UTC 
Removing myself for these bug components as I'm either no longer involved in that aspect of the project, or no longer care to watch this particular bug. Sorry if you are caught in a maelstrom of bug changes as a result!
Comment 3 Petr Bokoc 2019-11-07 15:30:18 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.