summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorSandra McCann <scmccann2000@gmail.com>2015-04-10 09:26:20 -0400
committerSandra McCann <scmccann2000@gmail.com>2015-04-10 09:26:20 -0400
commit415e2f367ee47d49c419a6913863307fb44c7bf7 (patch)
tree59199e2f5f4ffcc7ed06d9a0858a7dde7673542c
parente196e567cbaae1b0a9859f329db7c866083b2c7b (diff)
downloadvirtualization-getting-started-guide-smccann_virtmanager.tar.gz
virtualization-getting-started-guide-smccann_virtmanager.tar.xz
virtualization-getting-started-guide-smccann_virtmanager.zip
added ulinks to networking and virt deploy guides -NOT release-independent linkssmccann_virtmanager
-rw-r--r--en-US/Guest_Installation_Virt_Manager.xml6
1 files changed, 3 insertions, 3 deletions
diff --git a/en-US/Guest_Installation_Virt_Manager.xml b/en-US/Guest_Installation_Virt_Manager.xml
index 0600e3b..176c56c 100644
--- a/en-US/Guest_Installation_Virt_Manager.xml
+++ b/en-US/Guest_Installation_Virt_Manager.xml
@@ -96,7 +96,7 @@ Group: Virtualization
</section>
<section>
<title>Network Support</title>
- <para>By default libvirt creates a private network for your guests on the host machine. This private network will use a 192.168.x.x subnet and not be reachable directly from the network the host machine is on, but virtual guests can use the host machine as a gateway and can connect out with it. If you need to provide services on your guests that are reachable through other machines on your host network you can use iptables DNAT rules to forward in specific ports, or you can setup a Bridged env.
+ <para>By default libvirt creates a private network for your guests on the host machine. This private network will use a 192.168.x.x subnet and not be reachable directly from the network the host machine is on, but virtual guests can use the host machine as a gateway and can connect out with it. If you need to provide services on your guests that are reachable through other machines on your host network you can use firewalld to forward in specific ports, or you can setup a Bridged env. See the <ulink url="http://docs.fedoraproject.org/en-US/Fedora/21/html/Networking_Guide/index.html">Networking Guide</ulink> for more details.
</para>
</section>
<section id="Guest_Installation_Virt_Manager-Creating_guests_with_virt_manager">
@@ -214,10 +214,10 @@ Group: Virtualization
<para>
This method uses a Preboot eXecution Environment (PXE) server to
install the guest virtual machine. Setting up a PXE server is covered in the
- <citetitle>Deployment Guide</citetitle>. To install via network boot,
+ <ulink url="http://docs.fedoraproject.org/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/index.html">Virtualization Deployment and Administration Guide</ulink>. To install via network boot,
the guest must have a routable IP address or shared network device.
For information on the required networking configuration for PXE
- installation, refer to the <citetitle>Deployment Guide</citetitle>.
+ installation, refer to the <ulink url="http://docs.fedoraproject.org/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/index.html">Virtualization Deployment and Administration Guide</ulink>.
</para>
</listitem>
</varlistentry>