------------------------------------------------------------
revno: 3735
committer: Adam Sommer <[EMAIL PROTECTED]>
branch nick: ubuntu-hardy
timestamp: Thu 2008-03-13 01:34:12 -0400
message:
Clarifications to libvirt section. Updates for Hardy to web-servers.xml,
mostly cosmetic changes to the XML which make the HTML render better, but also
some command and package updates.
modified:
generic/serverguide/C/virtualization.xml
generic/serverguide/C/web-servers.xml
=== modified file 'generic/serverguide/C/virtualization.xml'
--- a/generic/serverguide/C/virtualization.xml 2008-03-03 22:02:23 +0000
+++ b/generic/serverguide/C/virtualization.xml 2008-03-13 05:34:12 +0000
@@ -51,7 +51,7 @@
To install the necessary packages, from a terminal prompt enter:
</para>
<screen>
-<command>sudo apt-get install kvm libvirt-bin virt-viewer
python-virtinst</command>
+<command>sudo apt-get install kvm libvirt-bin</command>
</screen>
<para>
After installing <application>libvirt-bin</application>, the user used
to manage virtual machines will need to be added to
@@ -69,11 +69,37 @@
</para>
</note>
<para>
- You can now use the <application>virt-install</application> utility to
create a new virtual machine. There are several
- options available to configure the virtual environment. For example:
- </para>
-<screen>
-<command>virt-install -n web_devel -r 256 -f web_devel.img -s 4 -w
bridge:vnet0 -c jeos.iso -p</command>
+ You are now ready to install a <emphasis>Guest</emphasis> operating
system. Installing a virtual machine follows the same
+ process as installing the operating system directly on the hardware.
You either need a way to automate the installation, or
+ a keyboard and monitor will need to be attached to the machine. In the
case of virtual machines a Graphical User Interface (GUI)
+ is analogous to using a physical keyboard and mouse.
+ </para>
+ <para>
+ There are several ways to automate the Ubuntu installation process, for
example using
+ preseeds, kickstart, etc. Refer to the <ulink
url="https://help.ubuntu.com/&distro-rev;/installation-guide/";>Ubuntu
Installation Guide</ulink> for details.
+ </para>
+ <para>
+ A feature of <application>libvirt</application> is the ability to
connect to the virtual machine's console using <application>VNC</application>.
+ The <application>virt-viewer</application> application can be used to
connect to a virtual machine console see
+ <xref linkend="libvirt-virt-viewer"/> for more information.
+ </para>
+ <para>
+ Another way to install an Ubuntu virtual machine is to use
<application>ubuntu-vm-builder</application>. For details see <xref
linkend="ubuntu-vm-builder"/>
+ </para>
+ </sect2>
+ <sect2 id='libvirt-virt-install' status='review'>
+ <title>virt-install</title>
+ <para>
+ <application>virt-install</application> is part of the
<application>python-virtinst</application> package. To install it, from a
terminal prompt enter:
+ </para>
+<screen>
+<command>sudo apt-get install python-virtinst</command>
+</screen>
+ <para>
+ There are several options available when using
<application>virt-install</application>. For example:
+ </para>
+<screen>
+<command>virt-install -n web_devel -r 256 -f web_devel.img -s 4 -w
bridge:vnet0 -c jeos.iso --accelerate --vnc --noautoconsole</command>
</screen>
<itemizedlist>
<listitem>
@@ -111,13 +137,23 @@
</listitem>
<listitem>
<para>
- <emphasis>-p:</emphasis> creates the virtual machine as a
<emphasis>paravirtualized</emphasis> guest.
+ <emphasis>--accelerate:</emphasis> enables the kernel's acceleration
technologies.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <emphasis>--vnc:</emphasis> exports the guest's virtual console
using VNC.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <emphasis>--noautoconsole:</emphasis> will not automatically connect
to the virtual machine's console.
</para>
</listitem>
</itemizedlist>
<para>
- After launching <application>virt-install</application> the virtual
machine's console will open and you will be taken through the
- normal installation process for the guest operating system.
+ After launching <application>virt-install</application> you can connect
to the virtual machine's console either locally
+ using a GUI or with the <application>virt-viewer</application> utility.
</para>
</sect2>
<sect2 id="libvirt-management" status="review">
@@ -139,7 +175,15 @@
</listitem>
<listitem>
<para>
- To list start a virtual machine at boot:
+ To list start a virtual machine:
+ </para>
+<screen>
+<command>virsh -c qemu:///system start web_devel</command>
+</screen>
+ </listitem>
+ <listitem>
+ <para>
+ Similarly, to list start a virtual machine at boot:
</para>
<screen>
<command>virsh -c qemu:///system autostart web_devel</command>
@@ -190,7 +234,7 @@
</note>
</sect3>
<sect3 id="virt-manager" status="review">
- <title>virt-manager</title>
+ <title>Virtual Machine Manager</title>
<para>
The <application>virt-manager</application> package contains a
graphical utility to manage local and remote virtual machines.
To install virt-manager enter:
@@ -219,16 +263,33 @@
</note>
</sect3>
</sect2>
- <sect2 id="libvirt-virtmachine-console" status="review">
- <title>Virtual Machine Console</title>
- <para>
- Once a virtual machine is install and running you can connect to the
virtual machine's console using
- <application>virt-viewer</application>. As an example, from a terminal:
+ <sect2 id="libvirt-virt-viewer" status="review">
+ <title>Virtual Machine Viewer</title>
+ <para>
+ The <application>virt-viewer</application> application allows you to
connect to a virtual machine's console. <application>virt-viewer</application>
+ does require a GUI to interaface with the virtual machine.
+ </para>
+ <para>
+ To install <application>virt-viewer</application> from a terminal enter:
+ </para>
+<screen>
+<command>sudo apt-get install virt-viewer</command>
+</screen>
+ <para>
+ Once a virtual machine is installed and running you can connect to the
virtual machine's console using
+ by:
</para>
<screen>
<command>virt-viewer qemu:///system web_devel</command>
</screen>
<para>
+ Similar to <application>virt-manager</application>,
<application>virt-viewer</application> can connect to a remote host using
+ <emphasis>SSH</emphasis> as well:
+ </para>
+<screen>
+<command>virt-viewer -c qemu+ssh://hostname/system web_devel</command>
+</screen>
+ <para>
Be sure and replace <emphasis role="italic">web_devel</emphasis> with
the appropriate virtual machine name.
</para>
<para>
@@ -303,12 +364,20 @@
Also notice that the <emphasis>--mem 256</emphasis> option increases the
virtual machines memory from the default 128M.
</para>
<para>
- After the image creation process has finished a directory named <filename
role="directory">ubuntu-jeos-hardy-i386</filename> is created,
+ At the end of the image creation you will be prompted to confirm the
additional package installation.
+ After the image creation process has finished a directory named <filename
role="directory">ubuntu-jeos-&distro-short-codename;-i386</filename> is created,
and inside is the virtual machine image file named
<filename>root.qcow2</filename> and a shell script, used to start the virtual
machine,
named according to the image type.
</para>
<para>
Refer to the <application>ubuntu-vm-builder</application> man page for
more customization options.
</para>
+ <sect2 id="ubuntu-vm-builder-libvirt" status="review">
+ <title>Using ubuntu-vm-builder with libvirt</title>
+ <para>
+ Combining <application>ubuntu-vm-builder</application> with
<application>libvirt</application> provides a great environment for virtual
machine
+ creation and management.
+ </para>
+ </sect2>
</sect1>
</chapter>
=== modified file 'generic/serverguide/C/web-servers.xml'
--- a/generic/serverguide/C/web-servers.xml 2008-02-15 19:56:42 +0000
+++ b/generic/serverguide/C/web-servers.xml 2008-03-13 05:34:12 +0000
@@ -245,11 +245,15 @@
Some options are specified on a per-directory basis rather than
per-server.
Option is one of these directives. A Directory stanza
is enclosed in
XML-like tags, like so:
- <screen><command><Directory /var/www/mynewsite>
+ </para>
+<screen>
+<command><Directory /var/www/mynewsite>
...
-</Directory></command></screen>
- The Options directive within a Directory stanza accepts
one or more of the
- following values (among others), separated by spaces:
+</Directory></command>
+</screen>
+ <para>
+ The Options directive within a Directory stanza accepts one or more
of the
+ following values (among others), separated by spaces:
</para>
<itemizedlist spacing="compact">
<listitem>
@@ -269,7 +273,7 @@
Server-side includes allow an HTML file
to <emphasis>
include</emphasis> other files. This
is not a common option. See
<ulink
url="http://httpd.apache.org/docs/2.2/howto/ssi.html";>the Apache2
- SSI Howto</ulink> for mor
information.</para>
+ SSI Howto</ulink> for more
information.</para>
</listitem>
<listitem>
<para><emphasis
@@ -511,7 +515,7 @@
can enter the following command in the terminal prompt:
<screen>
-<command>sudo apt-get install php5-common php5 libapache2-mod-php5</command>
+<command>sudo apt-get install php5 libapache2-mod-php5</command>
</screen>
</para>
@@ -625,7 +629,7 @@
</para>
<para>
<screen>
-<command>sudo apt-get install squid squid-common</command>
+<command>sudo apt-get install squid</command>
</screen>
</para>
</sect2>
@@ -656,18 +660,18 @@
To set your Squid server to listen on TCP port 8888 instead
of the default TCP port 3128, change
the http_port directive as such:
</para>
- <para>
- http_port 8888
- </para>
+<programlisting>
+http_port 8888
+</programlisting>
</listitem>
<listitem>
<para>
Change the visible_hostname directive in order to give the
Squid server a specific hostname. This hostname
does not necessarily need to be the computer's hostname. In
this example it is set to <emphasis>weezie</emphasis>
</para>
- <para>
- visible_hostname weezie
- </para>
+<programlisting>
+visible_hostname weezie
+</programlisting>
</listitem>
<listitem>
<para>
@@ -678,16 +682,16 @@
<para>
Add the following to the <emphasis
role="bold">bottom</emphasis> of the ACL section of your
<filename>/etc/squid/squid.conf</filename> file:
</para>
- <para>
- acl fortytwo_network src 192.168.42.0/24
- </para>
+<programlisting>
+acl fortytwo_network src 192.168.42.0/24
+</programlisting>
<para>
Then, add the following to the <emphasis
role="bold">top</emphasis> of the http_access section of your
<filename>/etc/squid/squid.conf</filename> file:
</para>
- <para>
- http_access allow fortytwo_network
- </para>
+<programlisting>
+http_access allow fortytwo_network
+</programlisting>
</listitem>
<listitem>
<para>
@@ -698,17 +702,17 @@
<para>
Add the following to the <emphasis
role="bold">bottom</emphasis> of the ACL section of your
<filename>/etc/squid/squid.conf</filename> file:
</para>
- <para>
- acl biz_network src 10.1.42.0/24
- acl biz_hours time M T W T F 9:00-17:00
- </para>
+<programlisting>
+acl biz_network src 10.1.42.0/24
+acl biz_hours time M T W T F 9:00-17:00
+</programlisting>
<para>
Then, add the following to the <emphasis
role="bold">top</emphasis> of the http_access section of your
<filename>/etc/squid/squid.conf</filename> file:
</para>
- <para>
- http_access allow biz_network biz_hours
- </para>
+<programlisting>
+http_access allow biz_network biz_hours
+</programlisting>
</listitem>
</itemizedlist>
</para>
@@ -808,8 +812,8 @@
<application>Apache</application> process:
</para>
<screen>
-<command>chown -R www-data:www-data /path/to/rails/application/public</command>
-<command>chown -R www-data:www-data /path/to/rails/application/tmp</command>
+<command>sudo chown -R www-data:www-data
/path/to/rails/application/public</command>
+<command>sudo chown -R www-data:www-data
/path/to/rails/application/tmp</command>
</screen>
<para>Thats it! Now you have your Server ready for your
--
https://code.launchpad.net/~ubuntu-core-doc/ubuntu-doc/ubuntu-hardy
You are receiving this branch notification because you are subscribed to it.
--
ubuntu-doc-commits mailing list
ubuntu-doc-commits@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-doc-commits
