path: root/doc/gettext/el/xen-guide.xml.po

msgid ""
msgstr ""
"Project-Id-Version: PACKAGE VERSION\n"
"POT-Creation-Date: 2011-08-02 23:45+0600\n"
"PO-Revision-Date: 2011-01-21 01:40+0500\n"
"Last-Translator: Automatically generated\n"
"Language-Team: none\n"
"Language: el\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
"Plural-Forms: nplurals=2; plural=(n != 1);\n"

#: ../../gentoo/xml/htdocs/doc/en//xen-guide.xml(title):6
msgid "Configuring Gentoo with Xen"
msgstr ""

#: ../../gentoo/xml/htdocs/doc/en//xen-guide.xml(author:title):8
msgid "Author"
msgstr ""

#: ../../gentoo/xml/htdocs/doc/en//xen-guide.xml(mail:link):9
msgid "swift@gentoo.org"
msgstr ""

#: ../../gentoo/xml/htdocs/doc/en//xen-guide.xml(mail):9
msgid "Sven Vermeulen"
msgstr ""

#: ../../gentoo/xml/htdocs/doc/en//xen-guide.xml(author:title):11
msgid "Editor"
msgstr ""

#: ../../gentoo/xml/htdocs/doc/en//xen-guide.xml(mail:link):12
msgid "nightmorph"
msgstr ""

#: ../../gentoo/xml/htdocs/doc/en//xen-guide.xml(abstract):15
msgid "This guide describes how to start using Xen on your Gentoo system"
msgstr ""

#: ../../gentoo/xml/htdocs/doc/en//xen-guide.xml(version):23
msgid "5"
msgstr ""

#: ../../gentoo/xml/htdocs/doc/en//xen-guide.xml(date):24
msgid "2011-06-07"
msgstr ""

#: ../../gentoo/xml/htdocs/doc/en//xen-guide.xml(title):27
#: ../../gentoo/xml/htdocs/doc/en//xen-guide.xml(title):58
#: ../../gentoo/xml/htdocs/doc/en//xen-guide.xml(title):384
msgid "Introduction"
msgstr ""

#: ../../gentoo/xml/htdocs/doc/en//xen-guide.xml(p):31
msgid ""
"The <uri link=\"http://www.xensource.com/\">Xen</uri> technology allows you "
"to run multiple operating systems on a single physical system, govern "
"resource consumption and even migrate domains (which are the virtual "
"environments in which a guest operating system runs) from one Xen-powered "
"system to another. Xen requires the host operating system to support Xen "
"(which, in this case, will be a Linux kernel) but guest operating systems "
"can run unmodified <e>if</e> your hardware supports Intel Virtualization "
"Technology (VT-x) or AMD Virtualization Technology (SVM). Otherwise your "
"guest operating systems must also support Xen."
msgstr ""

#: ../../gentoo/xml/htdocs/doc/en//xen-guide.xml(p):42
msgid ""
"This guide will talk you through the configuration steps necessary to get "
"Xen up and running on Gentoo Linux. We will not discuss Xen itself (the Xen "
"project has <uri link=\"http://www.cl.cam.ac.uk/research/srg/netos/xen/"
"readmes/user\">decent documentation</uri> available) nor will we talk about "
"specialized setups that might be very interesting for Xen setups but are not "
"Xen-related (like exporting Portage through NFS, booting Linux using PXE, "
"etc.)"
msgstr ""

#: ../../gentoo/xml/htdocs/doc/en//xen-guide.xml(title):56
msgid "Preparing Domain0"
msgstr ""

#: ../../gentoo/xml/htdocs/doc/en//xen-guide.xml(p):61
msgid ""
"<e>Domain0</e> is the primary domain under Xen, hosting the host operating "
"system which governs all other domains. In this chapter we will prepare an "
"existing Gentoo installation to become the host operating system in this "
"domain and build the Xen-powered kernel so that Gentoo is ready to host "
"other Xen domains."
msgstr ""

#: ../../gentoo/xml/htdocs/doc/en//xen-guide.xml(title):72
msgid "Rebuilding the Gentoo Installation?"
msgstr ""

#: ../../gentoo/xml/htdocs/doc/en//xen-guide.xml(p):75
msgid ""
"A dramatic change that might be necessary is to rebuild the entire Gentoo "
"installation with a different <c>CFLAGS</c> setting. Guest operating systems "
"running under Xen might otherwise see major performance degradation. If you, "
"however, are planning on checking out Xen rather than installing it for "
"production use and are not terribly fond of rebuilding all programs, you can "
"skip this step. In this case you will notice performance degradation but you "
"will still be able to use Xen."
msgstr ""

#: ../../gentoo/xml/htdocs/doc/en//xen-guide.xml(impo):85
msgid ""
"It is advised that, if you change your <c>CFLAGS</c> and build your system "
"with a gcc lower than version 4, you do not have <c>-Os</c> set as it has "
"been reported to produce broken code."
msgstr ""

#: ../../gentoo/xml/htdocs/doc/en//xen-guide.xml(pre:caption):91
msgid "Editing the CFLAGS and rebuild the Gentoo installation"
msgstr ""

#: ../../gentoo/xml/htdocs/doc/en//xen-guide.xml(pre):91
#, no-wrap
msgid ""
"\n"
"~# <i>nano -w /etc/make.conf</i>\n"
"<comment>(Add -mno-tls-direct-seg-refs ONLY if you have a 32-bit dom0)</comment>\n"
"<comment>(You don't need this flag if you have a 64-bit dom0)</comment>\n"
"CFLAGS=\"-O2 -march=pentium4 -pipe <i>-mno-tls-direct-seg-refs</i>\"\n"
"\n"
"~# <i>emerge -e world</i>\n"
msgstr ""

#: ../../gentoo/xml/htdocs/doc/en//xen-guide.xml(p):100
msgid ""
"If you boot your system using an initial ramdisk (initrd) you need to "
"rebuild the initrd as well (which is best done by running all steps you "
"would do when you rebuild your kernel)."
msgstr ""

#: ../../gentoo/xml/htdocs/doc/en//xen-guide.xml(title):109
#: ../../gentoo/xml/htdocs/doc/en//xen-guide.xml(pre:caption):117
msgid "Installing Xen"
msgstr ""

#: ../../gentoo/xml/htdocs/doc/en//xen-guide.xml(p):112
msgid ""
"Xen actually contains many components, so you'll need to install a few "
"packages."
msgstr ""

#: ../../gentoo/xml/htdocs/doc/en//xen-guide.xml(pre):117
#, no-wrap
msgid ""
"\n"
"~# <i>emerge xen xen-tools xen-sources</i>\n"
msgstr ""

#: ../../gentoo/xml/htdocs/doc/en//xen-guide.xml(title):124
#: ../../gentoo/xml/htdocs/doc/en//xen-guide.xml(pre:caption):206
#: ../../gentoo/xml/htdocs/doc/en//xen-guide.xml(title):259
msgid "Building the Kernel"
msgstr ""

#: ../../gentoo/xml/htdocs/doc/en//xen-guide.xml(p):127
msgid ""
"Next we'll build the Linux kernel with Xen support. This kernel, whose "
"sources are available at <path>/usr/src/linux-2.6.x.z-xen</path>, will be "
"our main running kernel (i.e. the one running domain 0). In the <c>XEN</c> "
"section you'll find drivers for all kinds of input/output, each driver "
"having a <e>backend</e> and <e>frontend</e> implementation available. For "
"the domain 0 kernel you need to select the <e>backend</e> implementation: "
"these are used by the other domains (who use the <e>frontend</e> drivers) to "
"communicate directly with the hardware."
msgstr ""

#: ../../gentoo/xml/htdocs/doc/en//xen-guide.xml(p):138
msgid ""
"Of course, don't forget to select <c>Xen-compatible</c> at <c>Processor type "
"and features</c>. If you're wondering about networking: each interface in a "
"domain has a point-to-point link to an interface on domain 0 (called "
"<path>vifX.Y</path> where X is the domain number and Y the Yth interface of "
"that domain), so you can configure your network the way you want (bridging, "
"NAT, etc.)"
msgstr ""

#: ../../gentoo/xml/htdocs/doc/en//xen-guide.xml(pre:caption):147
msgid "Enabling Xen Support for i386 Kernels"
msgstr ""

#: ../../gentoo/xml/htdocs/doc/en//xen-guide.xml(pre):147
#, no-wrap
msgid ""
"\n"
"Processor type and features  ---&gt;\n"
"      Subarchitecture Type (Xen-compatible)\n"
msgstr ""

#: ../../gentoo/xml/htdocs/doc/en//xen-guide.xml(pre:caption):152
msgid "Enabling Xen Support for x86_64 Kernels"
msgstr ""

#: ../../gentoo/xml/htdocs/doc/en//xen-guide.xml(pre):152
#, no-wrap
msgid ""
"\n"
"Processor type and features  ---&gt;\n"
"      Subarchitecture Type (PC-compatible)\n"
"  [*] Enable Xen compatible kernel\n"
"  [*] Support for hot-pluggable CPUs\n"
msgstr ""

#: ../../gentoo/xml/htdocs/doc/en//xen-guide.xml(pre:caption):159
msgid "Domain-0 Kernel Config"
msgstr ""

#: ../../gentoo/xml/htdocs/doc/en//xen-guide.xml(pre):159
#, no-wrap
msgid ""
"\n"
"Bus options (PCI etc.)  ---&gt;\n"
"  [*] PCI support\n"
"  [ ]   Xen PCI Frontend Debugging\n"
"\n"
"Networking  ---&gt;\n"
"  Networking options  ---&gt;\n"
"    &lt;*&gt; 802.1d Ethernet Bridging\n"
"    <comment>Only required by bridged networking.</comment>\n"
"\n"
"XEN  ---&gt;\n"
"  [*] Privileged Guest (domain 0)\n"
"  &lt;*&gt; Backend driver support\n"
"  &lt;*&gt;   Block-device backend driver\n"
"  &lt;*&gt;   Network-device backend driver\n"
"  &lt;*&gt;   PCI-device backend driver\n"
"           PCI Backend Mode (Virtual PCI) ---&gt;\n"
"  [*] Scrub memory before freeing it to Xen\n"
"  [*] Disable serial port drivers\n"
"      Xen version compatibility (3.0.4 and later)\n"
msgstr ""

#: ../../gentoo/xml/htdocs/doc/en//xen-guide.xml(pre:caption):181
msgid "Domain-U Kernel Config"
msgstr ""

#: ../../gentoo/xml/htdocs/doc/en//xen-guide.xml(pre):181
#, no-wrap
msgid ""
"\n"
"Bus options (PCI etc.)  ---&gt;\n"
"  [ ] PCI support\n"
"\n"
"Device Drivers  ---&gt;\n"
"  SCSI device support  ---&gt;\n"
"    &lt; &gt; SCSI device support\n"
"    <comment>Disabling SCSI support frees up the /dev/sd* device names\n"
"    for use as Xen virtual block devices.</comment>\n"
"\n"
"XEN  ---&gt;\n"
"  [ ] Privileged Guest (domain 0)\n"
"  &lt;*&gt; Block-device frontend driver\n"
"  &lt;*&gt; Network-device frontend driver\n"
"  [*] Scrub memory before freeing it to Xen\n"
"  [*] Disable serial port drivers\n"
"      Xen version compatibility (3.0.4 and later)\n"
msgstr ""

#: ../../gentoo/xml/htdocs/doc/en//xen-guide.xml(p):200
msgid ""
"A nice hint is to have the kernel make process store its intermediate object "
"files elsewhere so that you can reuse the same kernel tree to build "
"different configurations:"
msgstr ""

#: ../../gentoo/xml/htdocs/doc/en//xen-guide.xml(pre):206
#, no-wrap
msgid ""
"\n"
"~# <i>mkdir -p ~/build/dom0 ~/build/domU</i>\n"
"~# <i>make O=~/build/dom0 menuconfig</i>\n"
"<comment>(Configure the kernel)</comment>\n"
"~# <i>make O=~/build/dom0 &amp;&amp; make O=~/build/dom0 modules_install</i>\n"
msgstr ""

#: ../../gentoo/xml/htdocs/doc/en//xen-guide.xml(p):213
msgid ""
"Once the kernel is built you'll find the kernel image immediately in the "
"build directory (not inside <path>arch/</path> or any other directory) "
"called <path>vmlinuz</path>. Copy it to <path>/boot</path> and then "
"configure your bootloader to use the Xen hypervisor (one of the components "
"installed previously) which is stored as <path>/boot/xen.gz</path>. In the "
"bootloader configuration, add your newly built kernel as the kernel that Xen "
"should boot. For instance, for GRUB:"
msgstr ""

#: ../../gentoo/xml/htdocs/doc/en//xen-guide.xml(pre:caption):223
msgid "GRUB Configuration for Xen"
msgstr ""

#: ../../gentoo/xml/htdocs/doc/en//xen-guide.xml(pre):223
#, no-wrap
msgid ""
"\n"
"title Xen 3.0 / Gentoo Linux 2.6.x.y\n"
"root (hd0,0)\n"
"kernel /boot/xen.gz\n"
"module /boot/kernel-2.6.x.y-xen0 root=/dev/hda3\n"
msgstr ""

#: ../../gentoo/xml/htdocs/doc/en//xen-guide.xml(p):230
msgid ""
"Now reboot your system into Xen. Once you are booted, you need to load the "
"Xen daemon:"
msgstr ""

#: ../../gentoo/xml/htdocs/doc/en//xen-guide.xml(pre:caption):235
msgid "Loading the Xen daemon"
msgstr ""

#: ../../gentoo/xml/htdocs/doc/en//xen-guide.xml(pre):235
#, no-wrap
msgid ""
"\n"
"~# <i>/etc/init.d/xend start</i>\n"
msgstr ""

#: ../../gentoo/xml/htdocs/doc/en//xen-guide.xml(p):239
msgid ""
"Now check if you can do whatever you normally do on your system. If this is "
"the case, you can edit your bootloader configuration to always boot into Xen "
"and add the Xen deamon to the default runlevel so that it is started "
"automatically next time you boot."
msgstr ""

#: ../../gentoo/xml/htdocs/doc/en//xen-guide.xml(note):246
msgid ""
"If you wish to start guest domains automatically on boot add <c>xendomains</"
"c> to the default runlevel as well and create a symlink in <path>/etc/xen/"
"auto/</path> to the Xen configuration files for the domains you wish to "
"start."
msgstr ""

#: ../../gentoo/xml/htdocs/doc/en//xen-guide.xml(title):257
msgid "Creating an Unpriviledged Domain"
msgstr ""

#: ../../gentoo/xml/htdocs/doc/en//xen-guide.xml(p):262
msgid ""
"Go to the Xen-powered Linux kernel source and update the configuration. It "
"is wise to keep as many topics as possible similar to the main kernel except "
"the <c>XEN</c> settings where drivers should now have their <e>frontend</e> "
"implementation selected instead of the <e>backend</e>. Then build the kernel "
"and place the resulting <path>vmlinuz</path> file where you want (we assume "
"this is <path>/mnt/data/xen/kernel</path>):"
msgstr ""

#: ../../gentoo/xml/htdocs/doc/en//xen-guide.xml(pre:caption):271
msgid "Building the guest kernel"
msgstr ""

#: ../../gentoo/xml/htdocs/doc/en//xen-guide.xml(pre):271
#, no-wrap
msgid ""
"\n"
"~# <i>make O=~/build/domU</i>\n"
"~# <i>cp ~/build/domU/vmlinuz /mnt/data/xen/kernel/kernel-2.6.x.y-xen</i>\n"
msgstr ""

#: ../../gentoo/xml/htdocs/doc/en//xen-guide.xml(p):276
msgid ""
"It is also possible to create a single kernel image for both the "
"administrative domain and the unpriviledged domain. More information about "
"this can be found in the Xen user manual."
msgstr ""

#: ../../gentoo/xml/htdocs/doc/en//xen-guide.xml(title):285
msgid "Creating the Domain Disks"
msgstr ""

#: ../../gentoo/xml/htdocs/doc/en//xen-guide.xml(p):288
msgid ""
"For best performance, it is best to dedicate a partition (or logical volume) "
"to a domain rather than a file based filesystem. However, if you are going "
"to use Xen primarily for tests using a file based filesystem does have its "
"advantages (especially regarding maintenance)."
msgstr ""

#: ../../gentoo/xml/htdocs/doc/en//xen-guide.xml(p):295
msgid ""
"You can create a file based filesystem using <c>dd</c> and <c>mke2fs</c> (or "
"any other file system creation tool). For instance, to create a 2Gbyte ext3 "
"filesystem:"
msgstr ""

#: ../../gentoo/xml/htdocs/doc/en//xen-guide.xml(pre:caption):301
msgid "Creating a file based filesystem"
msgstr ""

#: ../../gentoo/xml/htdocs/doc/en//xen-guide.xml(pre):301
#, no-wrap
msgid ""
"\n"
"~# <i>dd if=/dev/zero of=/mnt/data/xen/disks/ext3root.img bs=1M count=2048</i>\n"
"~# <i>mke2fs -j /mnt/data/xen/disks/ext3root.img</i>\n"
msgstr ""

#: ../../gentoo/xml/htdocs/doc/en//xen-guide.xml(title):309
msgid "Configuring a Domain"
msgstr ""

#: ../../gentoo/xml/htdocs/doc/en//xen-guide.xml(p):312
msgid ""
"Next we create a Xen configuration file for a domain. You can store these "
"configuration files where you want, for instance at <path>/mnt/data/xen/"
"configs</path>. As an example, we create a configuration file for a small "
"Gentoo environment which uses the disk image we created previously:"
msgstr ""

#: ../../gentoo/xml/htdocs/doc/en//xen-guide.xml(pre:caption):320
msgid "Creating a domain configuration file"
msgstr ""

#: ../../gentoo/xml/htdocs/doc/en//xen-guide.xml(pre):320
#, no-wrap
msgid ""
"\n"
"~# <i>nano -w /mnt/data/xen/configs/gentoo</i>\n"
"\n"
"kernel = \"/mnt/data/xen/kernel/kernel-2.6.x.y-xen\"\n"
"memory = 512\n"
"name   = \"gentoo\"\n"
"<comment>(Map the disk image to the virtual /dev/sda1)</comment>\n"
"disk   = ['file:/mnt/data/xen/disks/ext3root.img,sda1,w']\n"
"root   = \"/dev/sda1 ro\"\n"
msgstr ""

#: ../../gentoo/xml/htdocs/doc/en//xen-guide.xml(p):331
msgid ""
"If you are using a block device (such as an lvm volume or partition) for the "
"disk use 'phy:' instead of 'file:' and leave off /dev. For example:"
msgstr ""

#: ../../gentoo/xml/htdocs/doc/en//xen-guide.xml(pre:caption):336
msgid "Using a block device"
msgstr ""

#: ../../gentoo/xml/htdocs/doc/en//xen-guide.xml(pre):336
#, no-wrap
msgid ""
"\n"
"<comment>(LVM Volume)</comment>\n"
"disk = [ 'phy:lvm/xen-guest-root,sda1,w' ]\n"
"\n"
"<comment>(Physical Partition)</comment>\n"
"disk = [ 'phy:sdb6,sda1,w' ]\n"
msgstr ""

#: ../../gentoo/xml/htdocs/doc/en//xen-guide.xml(p):344
msgid "You can find example configuration files in <path>/etc/xen</path>."
msgstr ""

#: ../../gentoo/xml/htdocs/doc/en//xen-guide.xml(title):351
msgid "Launching the New Domain"
msgstr ""

#: ../../gentoo/xml/htdocs/doc/en//xen-guide.xml(p):354
msgid ""
"Now we're all set and we can launch the new domain. If the disk image "
"contained an operating system, we could just create and attach the domain "
"using the <c>xm</c> command (Xen manager):"
msgstr ""

#: ../../gentoo/xml/htdocs/doc/en//xen-guide.xml(pre:caption):360
msgid "Creating and starting a new domain"
msgstr ""

#: ../../gentoo/xml/htdocs/doc/en//xen-guide.xml(pre):360
#, no-wrap
msgid ""
"\n"
"~# <i>xm create /mnt/data/xen/configs/gentoo -c</i>\n"
msgstr ""

#: ../../gentoo/xml/htdocs/doc/en//xen-guide.xml(p):364
msgid ""
"The domain would be booted inside the terminal in which you executed the "
"command. However, in our case, the disk image is empty so the domain won't "
"boot up in anything useful. To fix this, you can loop-mount the image and "
"install Gentoo as you're used to."
msgstr ""

#: ../../gentoo/xml/htdocs/doc/en//xen-guide.xml(p):371
msgid ""
"If you want to disconnect from the domain, press <path>Ctrl+]</path>. You "
"can always reconnect to the domains' console using <c>xm console gentoo</c>. "
"However, there is only one console per domain, so only use it when you can't "
"access the domain otherwise (for instance, through SSH)."
msgstr ""

#: ../../gentoo/xml/htdocs/doc/en//xen-guide.xml(title):382
msgid "Networking on Unpriviledged Domains"
msgstr ""

#: ../../gentoo/xml/htdocs/doc/en//xen-guide.xml(p):387
msgid ""
"Xen supports at least two ways of configuring your (virtual) network: "
"<e>routed</e> and <e>bridged</e>."
msgstr ""

#: ../../gentoo/xml/htdocs/doc/en//xen-guide.xml(p):392
msgid ""
"When selecting the <e>routed</e> approach, the interface inside your "
"unpriviledged domain is connected to the virtual interface on your "
"administrative domain. On your administrative domain (domain 0), the virtual "
"interface is linked together with <path>eth0</path>. The interface inside "
"your unpriviledged domain should have an IP address on the same network as "
"the interface on the administrative domain. Any communication to that IP "
"address can only occur from the administrative domain, unless you set up "
"specific routing rules."
msgstr ""

#: ../../gentoo/xml/htdocs/doc/en//xen-guide.xml(p):403
msgid ""
"When selecting the <e>bridged</e> approach, your default network interface "
"on the administrative domain becomes a bridge which accepts connections to "
"the virtual domains as well as to the IP address your administrative domain "
"has."
msgstr ""

#: ../../gentoo/xml/htdocs/doc/en//xen-guide.xml(title):412
msgid "Regular Routed Interfaces"
msgstr ""

#: ../../gentoo/xml/htdocs/doc/en//xen-guide.xml(p):415
msgid ""
"Before you set up the interface on your unpriviledged domain, make sure that "
"Xen's <path>netloop</path> and <path>netbk</path> drivers are loaded. A "
"quick hint: if you have <path>netloop</path> as a module, load it with "
"<c>nloopbacks=0</c> so that it doesn't create pointless interfaces to the "
"loopback device. Then, edit your domain configuration file and add a <c>vif</"
"c> instruction to it."
msgstr ""

#: ../../gentoo/xml/htdocs/doc/en//xen-guide.xml(pre:caption):424
#: ../../gentoo/xml/htdocs/doc/en//xen-guide.xml(pre:caption):480
msgid "Configuring a virtual interface"
msgstr ""

#: ../../gentoo/xml/htdocs/doc/en//xen-guide.xml(pre):424
#, no-wrap
msgid ""
"\n"
"~# <i>nano -w /mnt/data/xen/configs/gentoo</i>\n"
"\n"
"<comment>(Add the vif instruction)</comment>\n"
"vif    = [ 'ip=192.168.1.101, vifname=veth1' ]\n"
msgstr ""

#: ../../gentoo/xml/htdocs/doc/en//xen-guide.xml(p):431
msgid ""
"In the above example, the interface will be created for the unpriviledged "
"domain (in which it will be called <path>eth0</path>) and Xen will ensure "
"that address 192.168.1.101 will be reachable from the administrative domain "
"through interface <path>veth1</path>."
msgstr ""

#: ../../gentoo/xml/htdocs/doc/en//xen-guide.xml(p):438
msgid ""
"This doesn't mean that the virtual <path>eth0</path> interface will "
"automatically have IP 192.168.1.101 assigned to it, but rather that, if you "
"don't give it that IP, it will not be connected with the administrative "
"domain and thus cannot be reached."
msgstr ""

#: ../../gentoo/xml/htdocs/doc/en//xen-guide.xml(p):445
msgid ""
"Now edit <path>/etc/xen/xend-config.sxp</path> as follows to select routed "
"network configuration:"
msgstr ""

#: ../../gentoo/xml/htdocs/doc/en//xen-guide.xml(pre:caption):450
#: ../../gentoo/xml/htdocs/doc/en//xen-guide.xml(pre:caption):492
msgid "Editing xend-config.sxp"
msgstr ""

#: ../../gentoo/xml/htdocs/doc/en//xen-guide.xml(pre):450
#, no-wrap
msgid ""
"\n"
"~# <i>nano -w /etc/xen/xend-config.sxp</i>\n"
"\n"
"<comment>(Comment out the following lines)</comment>\n"
"<i>#</i>(network-script network-bridge)\n"
"<i>#</i>(vif-script vif-bridge)\n"
"\n"
"<comment>(Enable the following lines)</comment>\n"
"(network-script network-route)\n"
"(vif-script vif-route)\n"
msgstr ""

#: ../../gentoo/xml/htdocs/doc/en//xen-guide.xml(title):465
msgid "Bridged Interfaces"
msgstr ""

#: ../../gentoo/xml/htdocs/doc/en//xen-guide.xml(p):468
msgid ""
"Unlike the routed interfaces you now need to load the <path>netloop</path> "
"driver with <c>nloopbacks=1</c> (or higher) as the additional loopback "
"devices are used to create the bridge. For the other modules you still need "
"the <path>netbk</path> module as well as briding functionality "
"(<path>bridge</path> module if build as such)."
msgstr ""

#: ../../gentoo/xml/htdocs/doc/en//xen-guide.xml(p):476
msgid "Now edit your virtual domain and add the <c>vif</c> construct:"
msgstr ""

#: ../../gentoo/xml/htdocs/doc/en//xen-guide.xml(pre):480
#, no-wrap
msgid ""
"\n"
"~# <i>nano -w /mnt/data/xen/configs/gentoo</i>\n"
"\n"
"<comment>(Add the vif instruction)</comment>\n"
"vif    = [ 'ip=192.168.1.101, vifname=veth0' ]\n"
msgstr ""

#: ../../gentoo/xml/htdocs/doc/en//xen-guide.xml(p):487
msgid ""
"Next edit <path>/etc/xen/xend-config.sxp</path> as follows to select bridged "
"network configuration:"
msgstr ""

#: ../../gentoo/xml/htdocs/doc/en//xen-guide.xml(pre):492
#, no-wrap
msgid ""
"\n"
"~# <i>nano -w /etc/xen/xend-config.sxp</i>\n"
"\n"
"<comment>(Enable the following lines)</comment>\n"
"(network-script network-bridge)\n"
"(vif-script vif-bridge)\n"
"\n"
"<comment>(Comment out the following lines if not done already)</comment>\n"
"<i>#</i> (network-script network-route)\n"
"<i>#</i> (vif-script vif-route)\n"
msgstr ""

#: ../../gentoo/xml/htdocs/doc/en//xen-guide.xml(p):504
msgid ""
"By default, the bridge will contain whatever interface is configured to be "
"the default interface (the device that is listed under the default route "
"through <c>ip route list</c>). If you want to alter this behavior, edit the "
"<path>xend-config.sxp</path> as follows:"
msgstr ""

#: ../../gentoo/xml/htdocs/doc/en//xen-guide.xml(pre:caption):511
msgid "Editing xend-config.sxp to change bridge configuration"
msgstr ""

#: ../../gentoo/xml/htdocs/doc/en//xen-guide.xml(pre):511
#, no-wrap
msgid ""
"\n"
"~# <i>nano -w /etc/xen/xend-config.sxp</i>\n"
"\n"
"<comment>(Edit the network-script line)</comment>\n"
"(network-script <i>'</i>network-bridge <i>netdev=eth0 bridge=xenbr0 vifnum=0'</i>)\n"
msgstr ""

#: ../../gentoo/xml/htdocs/doc/en//xen-guide.xml(p):518
msgid ""
"Once the configuration is done, restart the <c>xend</c> init script to have "
"Xen build the bridge:"
msgstr ""

#: ../../gentoo/xml/htdocs/doc/en//xen-guide.xml(pre:caption):523
msgid "Restarting the xend daemon"
msgstr ""

#: ../../gentoo/xml/htdocs/doc/en//xen-guide.xml(pre):523
#, no-wrap
msgid ""
"\n"
"~# <i>/etc/init.d/xend restart</i>\n"
msgstr ""

#: ../../gentoo/xml/htdocs/doc/en//xen-guide.xml(title):531
msgid "Further Resources"
msgstr ""

#: ../../gentoo/xml/htdocs/doc/en//xen-guide.xml(title):533
msgid "Xen Documentation"
msgstr ""

#: ../../gentoo/xml/htdocs/doc/en//xen-guide.xml(uri:link):538
msgid "http://bits.xensource.com/Xen/docs/user.pdf"
msgstr ""

#: ../../gentoo/xml/htdocs/doc/en//xen-guide.xml(uri):538
msgid "Xen Users' Manual (PDF)"
msgstr ""

#: ../../gentoo/xml/htdocs/doc/en//xen-guide.xml(uri:link):542
msgid "http://www.xen.org/support/documentation.html"
msgstr ""

#: ../../gentoo/xml/htdocs/doc/en//xen-guide.xml(uri):542
msgid "Xen Community Documentation"
msgstr ""

#: ../../gentoo/xml/htdocs/doc/en//xen-guide.xml(uri:link):546
msgid "http://wiki.xensource.com/xenwiki/"
msgstr ""

#: ../../gentoo/xml/htdocs/doc/en//xen-guide.xml(uri):546
msgid "Xen Wiki"
msgstr ""

#: ../../gentoo/xml/htdocs/doc/en//xen-guide.xml(title):553
msgid "Xen Tools"
msgstr ""

#: ../../gentoo/xml/htdocs/doc/en//xen-guide.xml(li):557
msgid ""
"<uri link=\"http://virt-manager.et.redhat.com/\">app-emulation/virt-manager</"
"uri> is a graphical tool for administering virtual machines"
msgstr ""

#. Place here names of translator, one per line. Format should be NAME; ROLE; E-MAIL
#: ../../gentoo/xml/htdocs/doc/en//xen-guide.xml(None):0
msgid "translator-credits"
msgstr ""