Date: Tue, 21 Feb 2012 21:53:48 GMT From: Rene Ladan <rene@FreeBSD.org> To: Perforce Change Reviews <perforce@FreeBSD.org> Subject: PERFORCE change 206684 for review Message-ID: <201202212153.q1LLrmM3025067@skunkworks.freebsd.org>
next in thread | raw e-mail | index | archive | help
http://p4web.freebsd.org/@@206684?ac=10 Change 206684 by rene@rene_acer on 2012/02/21 21:53:08 IFC Affected files ... .. //depot/projects/docproj_nl/en_US.ISO8859-1/books/developers-handbook/testing/chapter.sgml#4 integrate .. //depot/projects/docproj_nl/en_US.ISO8859-1/books/handbook/mail/chapter.sgml#11 integrate .. //depot/projects/docproj_nl/en_US.ISO8859-1/books/handbook/virtualization/chapter.sgml#14 integrate .. //depot/projects/docproj_nl/nl_NL.ISO8859-1/books/handbook/linuxemu/chapter.sgml#25 integrate .. //depot/projects/docproj_nl/nl_NL.ISO8859-1/books/handbook/mac/chapter.sgml#23 integrate .. //depot/projects/docproj_nl/nl_NL.ISO8859-1/books/handbook/ports/chapter.sgml#31 integrate .. //depot/projects/docproj_nl/nl_NL.ISO8859-1/books/handbook/security/chapter.sgml#37 integrate .. //depot/projects/docproj_nl/www/en/index.xsl#14 integrate .. //depot/projects/docproj_nl/www/en/where.sgml#18 integrate .. //depot/projects/docproj_nl/www/nl/where.sgml#37 integrate .. //depot/projects/docproj_nl/www/share/sgml/news.xml#132 integrate .. //depot/projects/docproj_nl/www/share/sgml/release.ent#43 integrate Differences ... ==== //depot/projects/docproj_nl/en_US.ISO8859-1/books/developers-handbook/testing/chapter.sgml#4 (text+ko) ==== @@ -1,7 +1,7 @@ <!-- The FreeBSD Documentation Project - $FreeBSD: doc/en_US.ISO8859-1/books/developers-handbook/testing/chapter.sgml,v 1.4 2012/02/19 00:59:04 gjb Exp $ + $FreeBSD: doc/en_US.ISO8859-1/books/developers-handbook/testing/chapter.sgml,v 1.6 2012/02/21 04:01:43 gjb Exp $ --> <chapter id="testing"> @@ -32,11 +32,12 @@ </listitem> <listitem> - <para>Run in single user mode. E.g. &man.cron.8;, and - other daemons only add noise. The &man.sshd.8; daemon can - also cause problems. If ssh access is required during test + <para>Run in single user mode. E.g., &man.cron.8;, and other + daemons only add noise. The &man.sshd.8; daemon can also + cause problems. If ssh access is required during testing either disable the SSHv1 key regeneration, or kill the - parent <command>sshd</command> daemon during the tests.</para> + parent <command>sshd</command> daemon during the + tests.</para> </listitem> <listitem> @@ -75,9 +76,9 @@ reinitialize with <command>newfs</command> and mount). To get 100% reproducibility, populate the file system from a &man.dd.1; file (i.e.: <command>dd - if=<filename>myimage</filename> of=<filename - class="devicefile">/dev/ad0s1h</filename> - bs=1m</command>)</para> + if=<filename>myimage</filename> of=<filename + class="devicefile">/dev/ad0s1h</filename> + bs=1m</command>)</para> </listitem> <listitem> @@ -139,7 +140,7 @@ <para>Try to keep the temperature as stable as possible around the machine. This affects both quartz crystals and disk drive algorithms. To get real stable clock, consider - stabilized clock injection. E.g. get a OCXO + PLL, inject + stabilized clock injection. E.g., get a OCXO + PLL, inject output into clock circuits instead of motherboard xtal. Contact &a.phk; for more information about this.</para> </listitem> @@ -176,11 +177,12 @@ disable <varname>background_fsck</varname> in <filename>/etc/rc.conf</filename> unless the benchmark is not started at least 60+<quote><command>fsck</command> - runtime</quote> seconds after the boot, as &man.rc.8; wakes - up and checks if <command>fsck</command> needs to run on any - file systems when background <command>fsck</command> is - enabled. Likewise, make sure there are no snapshots lying - around unless the benchmark is a test with snapshots.</para> + runtime</quote> seconds after the boot, as &man.rc.8; + wakes up and checks if <command>fsck</command> needs to run + on any file systems when background <command>fsck</command> + is enabled. Likewise, make sure there are no snapshots + lying around unless the benchmark is a test with + snapshots.</para> </listitem> <listitem> ==== //depot/projects/docproj_nl/en_US.ISO8859-1/books/handbook/mail/chapter.sgml#11 (text+ko) ==== @@ -1,7 +1,7 @@ <!-- The FreeBSD Documentation Project - $FreeBSD: doc/en_US.ISO8859-1/books/handbook/mail/chapter.sgml,v 1.145 2012/02/15 18:37:26 eadler Exp $ + $FreeBSD: doc/en_US.ISO8859-1/books/handbook/mail/chapter.sgml,v 1.146 2012/02/21 00:08:43 eadler Exp $ --> <chapter id="mail"> @@ -356,7 +356,7 @@ </sect3> <sect3 id="local"> - <title>Accessing local mailboxes</title> + <title>Accessing Local Mailboxes</title> <para>Mailboxes may be accessed locally by directly utilizing <acronym>MUA</acronym>s on the server on which the mailbox @@ -550,7 +550,7 @@ <para>The file format is simple; the mailbox name on the left side of the colon is expanded to the target(s) on the right. The - first example simply expands the mailbox <username>root</username> + first example expands the mailbox <username>root</username> to the mailbox <username>localuser</username>, which is then looked up again in the aliases database. If no match is found, then the message is delivered to the local user @@ -673,7 +673,7 @@ <para>However, for a variety of reasons, some system administrators want to change their system's MTA. These - reasons range from simply wanting to try out another MTA to + reasons range from merely wanting to try out another MTA to needing a specific feature or package which relies on another mailer. Fortunately, whatever the reason, FreeBSD makes it easy to make the change.</para> @@ -952,7 +952,7 @@ deliver the mail it will try to connect to you (<hostid role="domainname">example.com</hostid>) over the modem link. It will most likely time out because you are not online. The program <application>sendmail</application> will automatically deliver it to the - secondary MX site, i.e. your Internet provider (<hostid role="domainname">example.net</hostid>). The secondary MX + secondary MX site, i.e., your Internet provider (<hostid role="domainname">example.net</hostid>). The secondary MX site will then periodically try to connect to your host and deliver the mail to the primary MX host (<hostid role="domainname">example.com</hostid>).</para> @@ -1037,8 +1037,8 @@ locally, or would like to use a point and click client/system on another machine or even another ISP. It is also very useful if you only have one or two email - accounts set up. If there is a large number of addresses - to add, you can simply open this file in your favorite + accounts set up. If there are a large number of addresses + to add, open this file in your favorite text editor and then add the domains, one per line:</para> <programlisting>your.isp.example.com @@ -1355,7 +1355,7 @@ <para>Final hint: if you are uncertain whether some particular mail routing would work, remember the <option>-bt</option> option to <application>sendmail</application>. It starts <application>sendmail</application> in <emphasis>address test - mode</emphasis>; simply enter <literal>3,0</literal>, followed + mode</emphasis>; enter <literal>3,0</literal>, followed by the address you wish to test for the mail routing. The last line tells you the used internal mail agent, the destination host this agent will be called with, and the (possibly @@ -1727,9 +1727,8 @@ will be discussed later in this chapter (<xref linkend="mail-fetchmail">).</para> - <para>In order to send and receive email, simply invoke the - <command>mail</command> command as per the following - example:</para> + <para>In order to send and receive email, run + <command>mail</command>:</para> <screen>&prompt.user; <userinput>mail</userinput></screen> @@ -1884,8 +1883,8 @@ </imageobject> </mediaobject> - <para>In order to read an email, simply select it using the cursor - keys, and press the <keycap>Enter</keycap> key. An example of + <para>In order to read an email, select it using the cursor + keys and press the <keycap>Enter</keycap> key. An example of <application>mutt</application> displaying email can be seen below:</para> ==== //depot/projects/docproj_nl/en_US.ISO8859-1/books/handbook/virtualization/chapter.sgml#14 (text+ko) ==== @@ -1,14 +1,14 @@ <!-- The FreeBSD Documentation Project - $FreeBSD: doc/en_US.ISO8859-1/books/handbook/virtualization/chapter.sgml,v 1.30 2012/02/18 05:33:57 eadler Exp $ + $FreeBSD: doc/en_US.ISO8859-1/books/handbook/virtualization/chapter.sgml,v 1.32 2012/02/21 03:48:23 wblock Exp $ --> <chapter id="virtualization"> <chapterinfo> <authorgroup> <author> - <firstname>Murray</firstname> + <firstname>Murray</firstname> <surname>Stokely</surname> <contrib>Contributed by </contrib> </author> @@ -17,16 +17,16 @@ </chapterinfo> <title>Virtualization</title> - + <sect1 id="virtualization-synopsis"> <title>Synopsis</title> - + <para>Virtualization software allows multiple operating systems to run simultaneously on the same computer. Such software systems for PCs often involve a host operating system which runs the virtualization software and supports any number of guest operating systems.</para> - + <para>After reading this chapter, you will know:</para> <itemizedlist> @@ -36,8 +36,8 @@ </listitem> <listitem> - <para>How to install &os; on an &intel;-based &apple; &macintosh; - computer.</para> + <para>How to install &os; on an &intel;-based &apple; + &macintosh; computer.</para> </listitem> <!-- @@ -45,7 +45,8 @@ Hide all information regarding Xen under FreeBSD. <listitem> - <para>How to install &os; on Linux with <application>&xen;</application>.</para> + <para>How to install &os; on Linux with + <application>&xen;</application>.</para> </listitem> --> <listitem> @@ -68,214 +69,216 @@ linkend="basics">).</para> </listitem> - <listitem><para>Know how to install &os; (<xref - linkend="install">).</para></listitem> + <listitem> + <para>Know how to install &os; (<xref + linkend="install">).</para> + </listitem> - <listitem><para>Know how to set up your network connection (<xref - linkend="advanced-networking">).</para></listitem> + <listitem> + <para>Know how to set up your network connection (<xref + linkend="advanced-networking">).</para> + </listitem> - <listitem><para>Know how to install additional third-party - software (<xref linkend="ports">).</para></listitem> + <listitem> + <para>Know how to install additional third-party + software (<xref linkend="ports">).</para> + </listitem> </itemizedlist> - </sect1> - - <sect1 id="virtualization-guest"> <title>&os; as a Guest OS</title> <sect2 id="virtualization-guest-parallels"> <title>Parallels on MacOS</title> - <para><application>Parallels Desktop</application> for &mac; is a - commercial software product available for &intel; based &apple; - &mac; computers running &macos; 10.4.6 or higher. &os; is a - fully supported guest operating system. - Once <application>Parallels</application> has been installed on &macos; - X, the user must configure a virtual machine and then install - the desired guest operating system.</para> + <para><application>Parallels Desktop</application> for &mac; is + a commercial software product available for &intel; based + &apple; &mac; computers running &macos; 10.4.6 or higher. + &os; is a fully supported guest operating system. Once + <application>Parallels</application> has been installed on + &macos; X, the user must configure a virtual machine and then + install the desired guest operating system.</para> - <sect3 id="virtualization-guest-parallels-install"> - <title>Installing &os; on Parallels/&macos; X</title> + <sect3 id="virtualization-guest-parallels-install"> + <title>Installing &os; on Parallels/&macos; X</title> - <para>The first step in installing &os; on &macos; - X/<application>Parallels</application> is to create a new virtual - machine for installing &os;. Select <guimenuitem>&os;</guimenuitem> - as the <guimenu>Guest OS Type</guimenu> when prompted:</para> + <para>The first step in installing &os; on &macos; + X/<application>Parallels</application> is to create a new + virtual machine for installing &os;. Select + <guimenuitem>&os;</guimenuitem> as the <guimenu>Guest OS + Type</guimenu> when prompted:</para> - <mediaobject> - <imageobject> - <imagedata fileref="virtualization/parallels-freebsd1"> - </imageobject> - </mediaobject> + <mediaobject> + <imageobject> + <imagedata fileref="virtualization/parallels-freebsd1"> + </imageobject> + </mediaobject> - <para>And choose a reasonable amount of disk and - memory depending on your plans for this virtual &os; - instance. 4GB of disk space and 512MB of RAM work well for most - uses of &os; under <application>Parallels</application>:</para> + <para>And choose a reasonable amount of disk and memory + depending on your plans for this virtual &os; instance. + 4GB of disk space and 512MB of RAM work well for most uses + of &os; under <application>Parallels</application>:</para> - <mediaobject> - <imageobject> - <imagedata fileref="virtualization/parallels-freebsd2"> - </imageobject> - </mediaobject> + <mediaobject> + <imageobject> + <imagedata fileref="virtualization/parallels-freebsd2"> + </imageobject> + </mediaobject> - <mediaobject> - <imageobject> - <imagedata fileref="virtualization/parallels-freebsd3"> - </imageobject> - </mediaobject> + <mediaobject> + <imageobject> + <imagedata fileref="virtualization/parallels-freebsd3"> + </imageobject> + </mediaobject> - <mediaobject> - <imageobject> - <imagedata fileref="virtualization/parallels-freebsd4"> - </imageobject> - </mediaobject> + <mediaobject> + <imageobject> + <imagedata fileref="virtualization/parallels-freebsd4"> + </imageobject> + </mediaobject> - <mediaobject> - <imageobject> - <imagedata fileref="virtualization/parallels-freebsd5"> - </imageobject> - </mediaobject> + <mediaobject> + <imageobject> + <imagedata fileref="virtualization/parallels-freebsd5"> + </imageobject> + </mediaobject> - <para>Select the type of networking and a network - interface:</para> + <para>Select the type of networking and a network + interface:</para> - <mediaobject> - <imageobject> - <imagedata fileref="virtualization/parallels-freebsd6"> - </imageobject> - </mediaobject> + <mediaobject> + <imageobject> + <imagedata fileref="virtualization/parallels-freebsd6"> + </imageobject> + </mediaobject> - <mediaobject> - <imageobject> - <imagedata fileref="virtualization/parallels-freebsd7"> - </imageobject> - </mediaobject> + <mediaobject> + <imageobject> + <imagedata fileref="virtualization/parallels-freebsd7"> + </imageobject> + </mediaobject> - <para>Save and finish the configuration:</para> + <para>Save and finish the configuration:</para> - <mediaobject> - <imageobject> - <imagedata fileref="virtualization/parallels-freebsd8"> - </imageobject> - </mediaobject> + <mediaobject> + <imageobject> + <imagedata fileref="virtualization/parallels-freebsd8"> + </imageobject> + </mediaobject> - <mediaobject> - <imageobject> - <imagedata fileref="virtualization/parallels-freebsd9"> - </imageobject> - </mediaobject> + <mediaobject> + <imageobject> + <imagedata fileref="virtualization/parallels-freebsd9"> + </imageobject> + </mediaobject> - <para>After your &os; virtual machine has been created, - you will need to install &os; on it. This is best done - with an official &os; CDROM or with an ISO image - downloaded from an official FTP site. When you have the - appropriate ISO image on your local &mac; filesystem or a - CDROM in your &mac;'s CD drive, click on the disc icon in the - bottom right corner of your &os; - <application>Parallels</application> window. This - will bring up a window that allows you to associate the - CDROM drive in your virtual machine with an ISO file on - disk or with your real CDROM drive.</para> + <para>After your &os; virtual machine has been created, you + will need to install &os; on it. This is best done with an + official &os; CDROM or with an ISO image downloaded from an + official FTP site. When you have the appropriate ISO image + on your local &mac; filesystem or a CDROM in your &mac;'s CD + drive, click on the disc icon in the bottom right corner of + your &os; <application>Parallels</application> window. This + will bring up a window that allows you to associate the + CDROM drive in your virtual machine with an ISO file on disk + or with your real CDROM drive.</para> - <mediaobject> - <imageobject> - <imagedata fileref="virtualization/parallels-freebsd11"> - </imageobject> - </mediaobject> + <mediaobject> + <imageobject> + <imagedata fileref="virtualization/parallels-freebsd11"> + </imageobject> + </mediaobject> - <para>Once you have made this association with your CDROM - source, reboot your &os; virtual machine as normal by - clicking the reboot icon. - <application>Parallels</application> will reboot with a - special BIOS that first checks if you have a CDROM just as a - normal BIOS would do.</para> + <para>Once you have made this association with your CDROM + source, reboot your &os; virtual machine as normal by + clicking the reboot icon. + <application>Parallels</application> will reboot with a + special BIOS that first checks if you have a CDROM just as a + normal BIOS would do.</para> - <mediaobject> - <imageobject> - <imagedata fileref="virtualization/parallels-freebsd10"> - </imageobject> - </mediaobject> + <mediaobject> + <imageobject> + <imagedata fileref="virtualization/parallels-freebsd10"> + </imageobject> + </mediaobject> - <para>In this case it will find the &os; installation media - and begin a normal <application>sysinstall</application> based - installation as described in <xref linkend="install">. You - may install, but do not attempt to configure X11 at - this time.</para> + <para>In this case it will find the &os; installation media + and begin a normal <application>sysinstall</application> + based installation as described in <xref + linkend="install">. You may install, but do not attempt + to configure X11 at this time.</para> - <mediaobject> - <imageobject> - <imagedata fileref="virtualization/parallels-freebsd12"> - </imageobject> - </mediaobject> + <mediaobject> + <imageobject> + <imagedata fileref="virtualization/parallels-freebsd12"> + </imageobject> + </mediaobject> - <para>When you have finished the installation, reboot - into your newly installed &os; virtual machine.</para> + <para>When you have finished the installation, reboot into + your newly installed &os; virtual machine.</para> - <mediaobject> - <imageobject> - <imagedata fileref="virtualization/parallels-freebsd13"> - </imageobject> - </mediaobject> - </sect3> + <mediaobject> + <imageobject> + <imagedata fileref="virtualization/parallels-freebsd13"> + </imageobject> + </mediaobject> + </sect3> - <sect3 id="virtualization-guest-parallels-configure"> - <title>Configuring &os; on &macos; X/Parallels</title> + <sect3 id="virtualization-guest-parallels-configure"> + <title>Configuring &os; on &macos; X/Parallels</title> - <para>After &os; has been successfully installed on &macos; - X with <application>Parallels</application>, there are a number - of configuration steps that can be taken to optimize the system - for virtualized operation.</para> + <para>After &os; has been successfully installed on &macos; + X with <application>Parallels</application>, there are a + number of configuration steps that can be taken to + optimize the system for virtualized operation.</para> - <procedure> - <step> - <title>Set Boot Loader Variables</title> + <procedure> + <step> + <title>Set Boot Loader Variables</title> - <para>The most important step is to reduce the - <option>kern.hz</option> tunable to reduce the CPU utilization - of &os; under the <application>Parallels</application> - environment. This is accomplished by adding the following - line to <filename>/boot/loader.conf</filename>:</para> + <para>The most important step is to reduce the + <option>kern.hz</option> tunable to reduce the CPU + utilization of &os; under the <application>Parallels + </application> environment. This is accomplished by + adding the following line to <filename> + /boot/loader.conf</filename>:</para> - <programlisting>kern.hz=100</programlisting> + <programlisting>kern.hz=100</programlisting> - <para>Without this setting, an idle &os; - <application>Parallels</application> guest - OS will use roughly 15% of the CPU of a single - processor &imac;. After this change the usage will be - closer to a mere 5%.</para> - </step> + <para>Without this setting, an idle &os; + <application>Parallels</application> guest + OS will use roughly 15% of the CPU of a single + processor &imac;. After this change the usage will be + closer to a mere 5%.</para> + </step> - <step> - <title>Create a New Kernel Configuration File</title> + <step> + <title>Create a New Kernel Configuration File</title> - <para>You can remove all of the SCSI, FireWire, and USB - device drivers. <application>Parallels</application> - provides a virtual network - adapter used by the &man.ed.4; driver, so - all other network devices except for - &man.ed.4; and &man.miibus.4; can be - removed from the kernel.</para> - </step> + <para>You can remove all of the SCSI, FireWire, and USB + device drivers. <application>Parallels</application> + provides a virtual network + adapter used by the &man.ed.4; driver, so + all other network devices except for + &man.ed.4; and &man.miibus.4; can be + removed from the kernel.</para> + </step> - <step> - <title>Configure Networking</title> + <step> + <title>Configure Networking</title> - <para>The most basic networking setup involves simply - using DHCP to connect your virtual machine to the same - local area network as your host &mac;. This can be - accomplished by adding - <literal>ifconfig_ed0="DHCP"</literal> to - <filename>/etc/rc.conf</filename>. More advanced - networking setups are described in <xref - linkend="advanced-networking">.</para> - </step> - </procedure> - + <para>The most basic networking setup involves simply + using DHCP to connect your virtual machine to the same + local area network as your host &mac;. This can be + accomplished by adding + <literal>ifconfig_ed0="DHCP"</literal> to + <filename>/etc/rc.conf</filename>. More advanced + networking setups are described in + <xref linkend="advanced-networking">.</para> + </step> + </procedure> </sect3> - </sect2> <!-- Deactive/hide this section as the instruction in there do NOT work anyore: @@ -289,23 +292,23 @@ <sect2info> <authorgroup> <author> - <firstname>Fukang</firstname> + <firstname>Fukang</firstname> <surname>Chen (Loader)</surname> <contrib>Contributed by </contrib> - </author> - </authorgroup> - + </author> + </authorgroup> </sect2info> <title>&os; with &xen; on Linux</title> - <para>The <application>&xen;</application> hypervisor is an open - source paravirtualization product which is now supported by the - commercial XenSource company. Guest operating systems are known - as domU domains, and the host operating system is known as dom0. - The first step in running a virtual &os; instance under Linux - is to install <application>&xen;</application> for Linux dom0. - The host operating system will be a Slackware Linux + <para>The <application>&xen;</application> hypervisor is an + open source paravirtualization product which is now + supported by the commercial XenSource company. Guest + operating systems are known as domU domains, and the host + operating system is known as dom0. The first step in + running a virtual &os; instance under Linux is to install + <application>&xen;</application> for Linux dom0. The host + operating system will be a Slackware Linux distribution.</para> <sect3 id="xen-slackware-dom0"> @@ -316,9 +319,9 @@ <title>Download &xen; 3.0 from XenSource</title> <para>Download <ulink - url="http://bits.xensource.com/oss-xen/release/3.0.4-1/src.tgz/xen-3.0.4_1-src.tgz">xen-3.0.4_1-src.tgz</ulink>; - from <ulink url="http://www.xensource.com/"></ulink>.</para>; - + url="http://bits.xensource.com/oss-xen/release/3.0.4-1/src.tgz/xen-3.0.4_1-src.tgz">xen-3.0.4_1-src.tgz</ulink>; + from <ulink + url="http://www.xensource.com/"></ulink>.</para>; </step> <step> @@ -328,17 +331,18 @@ &prompt.root; <userinput>KERNELS="linux-2.6-xen0 linux-2.6-xenU" make world</userinput> &prompt.root; <userinput>make install</userinput></screen> - <note> - <para>To re-compile the kernel for dom0:</para> + <note> + <para>To re-compile the kernel for dom0:</para> - <screen>&prompt.root; <userinput>cd xen-3.0.4_1-src/linux-2.6.16.33-xen0</userinput> + <screen>&prompt.root; <userinput>cd xen-3.0.4_1-src/linux-2.6.16.33-xen0</userinput> &prompt.root; <userinput>make menuconfig</userinput> &prompt.root; <userinput>make</userinput> &prompt.root; <userinput>make install</userinput></screen> - <para>Older version of <application>&xen;</application> may need to specify - <command>make ARCH=xen menuconfig</command></para> - </note> + <para>Older version of + <application>&xen;</application> may need to specify + <command>make ARCH=xen menuconfig</command></para> + </note> </step> <step> @@ -351,10 +355,10 @@ root (hd0,0) kernel /boot/xen-3.0.4-1.gz dom0_mem=262144 module /boot/vmlinuz-2.6.16.33-xen0 root=/dev/hda1 ro</programlisting> - </step> + </step> - <step> - <title>Reboot your computer into &xen;</title> + <step> + <title>Reboot your computer into &xen;</title> <para>First, edit <filename>/etc/xen/xend-config.sxp</filename>, and add @@ -365,45 +369,50 @@ <para>Then, we can launch <application>&xen;</application>:</para> - <screen>&prompt.root; <userinput>/etc/init.d/xend start</userinput> + <screen>&prompt.root; <userinput>/etc/init.d/xend start</userinput> &prompt.root; <userinput>/etc/init.d/xendomains start</userinput></screen> <para>Our dom0 is running:</para> - <screen>&prompt.root; <userinput>xm list</userinput> + <screen>&prompt.root; <userinput>xm list</userinput> Name ID Mem VCPUs State Time(s) Domain-0 0 256 1 r––––– 54452.9</screen> - </step> - </procedure> - </sect3> + </step> + </procedure> + </sect3> - <sect3> - <title>&os; 7-CURRENT domU</title> + <sect3> + <title>&os; 7-CURRENT domU</title> - <para>Download the &os; domU kernel for <application>&xen; 3.0</application> and - disk image from <ulink - url="http://www.fsmware.com/">http://www.fsmware.com/</ulink></para>; + <para>Download the &os; domU kernel for + <application>&xen; 3.0</application> and disk image from + <ulink + url="http://www.fsmware.com/">http://www.fsmware.com/</ulink></para>; - <itemizedlist> - <listitem> - <para><ulink url="http://www.fsmware.com/xenofreebsd/7.0/download/kernel-current">kernel-current</ulink></para>; - </listitem> + <itemizedlist> + <listitem> + <para><ulink + url="http://www.fsmware.com/xenofreebsd/7.0/download/kernel-current">kernel-current</ulink></para>; + </listitem> - <listitem> - <para><ulink url="http://www.fsmware.com/xenofreebsd/7.0/download/mdroot-7.0.bz2">mdroot-7.0.bz2</ulink></para>; - </listitem> + <listitem> + <para><ulink + url="http://www.fsmware.com/xenofreebsd/7.0/download/mdroot-7.0.bz2">mdroot-7.0.bz2</ulink></para>; + </listitem> - <listitem> - <para><ulink url="http://www.fsmware.com/xenofreebsd/7.0/download/config/xmexample1.bsd">xmexample1.bsd</ulink></para>; - </listitem> - </itemizedlist> + <listitem> + <para><ulink + url="http://www.fsmware.com/xenofreebsd/7.0/download/config/xmexample1.bsd">xmexample1.bsd</ulink></para>; + </listitem> + </itemizedlist> - <para>Put the configuration file <filename>xmexample1.bsd</filename> - into <filename>/etc/xen/</filename> and modify the related - entries about where the kernel and the disk image are stored. - It should look like the following:</para> + <para>Put the configuration file + <filename>xmexample1.bsd</filename> into + <filename>/etc/xen/</filename> and modify the related + entries about where the kernel and the disk image are + stored. It should look like the following:</para> - <programlisting>kernel = "/opt/kernel-current" + <programlisting>kernel = "/opt/kernel-current" memory = 256 name = "freebsd" vif = [ '' ] @@ -414,18 +423,19 @@ extra += ",kern.hz=100" extra += ",vfs.root.mountfrom=ufs:/dev/xbd769a"</programlisting> - <para>The <filename>mdroot-7.0.bz2</filename> file should be - uncompressed.</para> + <para>The <filename>mdroot-7.0.bz2</filename> file should + be uncompressed.</para> - <para>Next, the __xen_guest section in <filename>kernel-current</filename> - needs to be altered to add the VIRT_BASE that - <application>&xen; 3.0.3</application> requires:</para> + <para>Next, the __xen_guest section in + <filename>kernel-current</filename> needs to be altered to + add the VIRT_BASE that + <application>&xen; 3.0.3</application> requires:</para> - <screen>&prompt.root; <userinput>objcopy kernel-current -R __xen_guest</userinput> + <screen>&prompt.root; <userinput>objcopy kernel-current -R __xen_guest</userinput> &prompt.root; <userinput>perl -e 'print "LOADER=generic,GUEST_OS=freebsd,GUEST_VER=7.0,XEN_VER=xen-3.0,BSD_SYMTAB,VIRT_BASE=0xC0000000\x00"' > tmp</userinput> &prompt.root; <userinput>objcopy kernel-current ––add-section __xen_guest=tmp</userinput></screen> - <screen>&prompt.root; <userinput>objdump -j __xen_guest -s kernel-current</userinput> + <screen>&prompt.root; <userinput>objdump -j __xen_guest -s kernel-current</userinput> kernel-current: file format elf32-i386 @@ -437,9 +447,10 @@ 0040 445f5359 4d544142 2c564952 545f4241 D_SYMTAB,VIRT_BA 0050 53453d30 78433030 30303030 3000 SE=0xC0000000. </screen> - <para>We are, now, ready to create and launch our domU:</para> + <para>We are, now, ready to create and launch our + domU:</para> - <screen>&prompt.root; <userinput>xm create /etc/xen/xmexample1.bsd -c</userinput> + <screen>&prompt.root; <userinput>xm create /etc/xen/xmexample1.bsd -c</userinput> Using config file "/etc/xen/xmexample1.bsd". Started domain freebsd WARNING: loader(8) metadata is missing! @@ -463,7 +474,7 @@ Timecounters tick every 10.000 msec [XEN] Initialising virtual ethernet driver. xn0: Ethernet address: 00:16:3e:6b:de:3a -[XEN] +[XEN] Trying to mount root from ufs:/dev/xbd769a WARNING: / was not properly dismounted Loading configuration files. @@ -473,9 +484,9 @@ /dev/xbd769a: 18859 files, 140370 used, 113473 free (10769 frags, 12838 blocks, 4.2% fragmentation) Setting hostname: demo.freebsd.org. lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> mtu 16384 - inet6 ::1 prefixlen 128 - inet6 fe80::1%lo0 prefixlen 64 scopeid 0x2 - inet 127.0.0.1 netmask 0xff000000 + inet6 ::1 prefixlen 128 + inet6 fe80::1%lo0 prefixlen 64 scopeid 0x2 + inet 127.0.0.1 netmask 0xff000000 Additional routing options:. Mounting NFS file systems:. Starting syslogd. @@ -500,481 +511,491 @@ login: </screen> - <para>The domU should run the &os; 7.0-CURRENT - kernel:</para> + <para>The domU should run the &os; 7.0-CURRENT + kernel:</para> - <screen>&prompt.root; <userinput>uname -a</userinput> -FreeBSD demo.freebsd.org 7.0-CURRENT FreeBSD 7.0-CURRENT #113: Wed Jan 4 06:25:43 UTC 2006 + <screen>&prompt.root; <userinput>uname -a</userinput> +FreeBSD demo.freebsd.org 7.0-CURRENT FreeBSD 7.0-CURRENT #113: Wed Jan 4 06:25:43 UTC 2006 kmacy@freebsd7.gateway.2wire.net:/usr/home/kmacy/p4/freebsd7_xen3/src/sys/i386-xen/compile/XENCONF i386</screen> - <para>The network can now be configured on the domU. The &os; - domU will use a specific interface called - <devicename>xn0</devicename>:</para> + <para>The network can now be configured on the domU. The + &os; domU will use a specific interface called + <devicename>xn0</devicename>:</para> - <screen>&prompt.root; <userinput>ifconfig xn0 10.10.10.200 netmask 255.0.0.0</userinput> + <screen>&prompt.root; <userinput>ifconfig xn0 10.10.10.200 netmask 255.0.0.0</userinput> &prompt.root; <userinput>ifconfig</userinput> xn0: flags=843<UP,BROADCAST,RUNNING,SIMPLEX> mtu 1500 inet 10.10.10.200 netmask 0xff000000 broadcast 10.255.255.255 ether 00:16:3e:6b:de:3a lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> mtu 16384 - inet6 ::1 prefixlen 128 - inet6 fe80::1%lo0 prefixlen 64 scopeid 0x2 + inet6 ::1 prefixlen 128 + inet6 fe80::1%lo0 prefixlen 64 scopeid 0x2 inet 127.0.0.1 netmask 0xff000000 </screen> - <para>On dom0 Slackware, some <application>&xen;</application> - dependant network interfaces should show up:</para> + <para>On dom0 Slackware, some + <application>&xen;</application> dependant network + interfaces should show up:</para> - <screen>&prompt.root; <userinput>ifconfig</userinput> -eth0 Link encap:Ethernet HWaddr 00:07:E9:A0:02:C2 - inet addr:10.10.10.130 Bcast:0.0.0.0 Mask:255.0.0.0 - UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 - RX packets:815 errors:0 dropped:0 overruns:0 frame:0 - TX packets:1400 errors:0 dropped:0 overruns:0 carrier:0 - collisions:0 txqueuelen:0 - RX bytes:204857 (200.0 KiB) TX bytes:129915 (126.8 KiB) + <screen>&prompt.root; <userinput>ifconfig</userinput> +eth0 Link encap:Ethernet HWaddr 00:07:E9:A0:02:C2 + inet addr:10.10.10.130 Bcast:0.0.0.0 Mask:255.0.0.0 + UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 + RX packets:815 errors:0 dropped:0 overruns:0 frame:0 + TX packets:1400 errors:0 dropped:0 overruns:0 carrier:0 + collisions:0 txqueuelen:0 + RX bytes:204857 (200.0 KiB) TX bytes:129915 (126.8 KiB) -lo Link encap:Local Loopback - inet addr:127.0.0.1 Mask:255.0.0.0 - UP LOOPBACK RUNNING MTU:16436 Metric:1 - RX packets:99 errors:0 dropped:0 overruns:0 frame:0 - TX packets:99 errors:0 dropped:0 overruns:0 carrier:0 - collisions:0 txqueuelen:0 - RX bytes:9744 (9.5 KiB) TX bytes:9744 (9.5 KiB) +lo Link encap:Local Loopback + inet addr:127.0.0.1 Mask:255.0.0.0 + UP LOOPBACK RUNNING MTU:16436 Metric:1 + RX packets:99 errors:0 dropped:0 overruns:0 frame:0 + TX packets:99 errors:0 dropped:0 overruns:0 carrier:0 + collisions:0 txqueuelen:0 + RX bytes:9744 (9.5 KiB) TX bytes:9744 (9.5 KiB) -peth0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF - UP BROADCAST RUNNING NOARP MTU:1500 Metric:1 - RX packets:1853349 errors:0 dropped:0 overruns:0 frame:0 - TX packets:952923 errors:0 dropped:0 overruns:0 carrier:0 - collisions:0 txqueuelen:1000 - RX bytes:2432115831 (2.2 GiB) TX bytes:86528526 (82.5 MiB) - Base address:0xc000 Memory:ef020000-ef040000 +peth0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF + UP BROADCAST RUNNING NOARP MTU:1500 Metric:1 + RX packets:1853349 errors:0 dropped:0 overruns:0 frame:0 + TX packets:952923 errors:0 dropped:0 overruns:0 carrier:0 + collisions:0 txqueuelen:1000 + RX bytes:2432115831 (2.2 GiB) TX bytes:86528526 (82.5 MiB) + Base address:0xc000 Memory:ef020000-ef040000 -vif0.1 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF - UP BROADCAST RUNNING NOARP MTU:1500 Metric:1 - RX packets:1400 errors:0 dropped:0 overruns:0 frame:0 - TX packets:815 errors:0 dropped:0 overruns:0 carrier:0 - collisions:0 txqueuelen:0 - RX bytes:129915 (126.8 KiB) TX bytes:204857 (200.0 KiB) +vif0.1 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF + UP BROADCAST RUNNING NOARP MTU:1500 Metric:1 + RX packets:1400 errors:0 dropped:0 overruns:0 frame:0 + TX packets:815 errors:0 dropped:0 overruns:0 carrier:0 + collisions:0 txqueuelen:0 + RX bytes:129915 (126.8 KiB) TX bytes:204857 (200.0 KiB) -vif1.0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF - UP BROADCAST RUNNING NOARP MTU:1500 Metric:1 - RX packets:3 errors:0 dropped:0 overruns:0 frame:0 - TX packets:2 errors:0 dropped:157 overruns:0 carrier:0 - collisions:0 txqueuelen:1 - RX bytes:140 (140.0 b) TX bytes:158 (158.0 b) +vif1.0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF + UP BROADCAST RUNNING NOARP MTU:1500 Metric:1 + RX packets:3 errors:0 dropped:0 overruns:0 frame:0 + TX packets:2 errors:0 dropped:157 overruns:0 carrier:0 + collisions:0 txqueuelen:1 + RX bytes:140 (140.0 b) TX bytes:158 (158.0 b) -xenbr1 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF - UP BROADCAST RUNNING NOARP MTU:1500 Metric:1 - RX packets:4 errors:0 dropped:0 overruns:0 frame:0 - TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 - collisions:0 txqueuelen:0 - RX bytes:112 (112.0 b) TX bytes:0 (0.0 b)</screen> +xenbr1 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF + UP BROADCAST RUNNING NOARP MTU:1500 Metric:1 + RX packets:4 errors:0 dropped:0 overruns:0 frame:0 + TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 + collisions:0 txqueuelen:0 + RX bytes:112 (112.0 b) TX bytes:0 (0.0 b)</screen> <screen>&prompt.root; <userinput>brctl show</userinput> bridge name bridge id STP enabled interfaces xenbr1 8000.feffffffffff no vif0.1 peth0 vif1.0</screen> - </sect3> - - </sect2> + </sect3> + </sect2> --> <sect2 id="virtualization-guest-virtualpc"> <title>Virtual PC on &windows;</title> <para><application>Virtual PC</application> for &windows; is a - µsoft; software product available for free download. See <ulink - url="http://www.microsoft.com/windows/downloads/virtualpc/sysreq.mspx">; - system requirements</ulink>. Once <application>Virtual PC</application> - has been installed on µsoft.windows;, the user must configure a - virtual machine and then install the desired guest operating - system.</para> + µsoft; software product available for free download. + See <ulink + url="http://www.microsoft.com/windows/downloads/virtualpc/sysreq.mspx">; + system requirements</ulink>. Once <application> Virtual PC >>> TRUNCATED FOR MAIL (1000 lines) <<<
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201202212153.q1LLrmM3025067>