# Azamat H. Hackimov , 2010. msgid "" msgstr "" "Project-Id-Version: \n" "POT-Creation-Date: 2011-03-02 17:28+0500\n" "PO-Revision-Date: 2010-02-09 01:10+0500\n" "Last-Translator: Azamat H. Hackimov \n" "Language-Team: Russian \n" "Language: ru\n" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=UTF-8\n" "Content-Transfer-Encoding: 8bit\n" "Plural-Forms: nplurals=3; plural=(n%10==1 && n%100!=11 ? 0 : n%10>=2 && n" "%10<=4 && (n%100<10 || n%100>=20) ? 1 : 2);\n" "X-Generator: Lokalize 1.0\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 "swift@gentoo.org" #: ../../gentoo/xml/htdocs/doc/en//xen-guide.xml(mail):9 msgid "Sven Vermeulen" msgstr "Sven Vermeulen" #: ../../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 "4" msgstr "" #: ../../gentoo/xml/htdocs/doc/en//xen-guide.xml(date):24 msgid "2011-03-02" 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 Xen 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 if 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 decent documentation 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 "" "Domain0 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 CFLAGS 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 CFLAGS and build your system " "with a gcc lower than version 4, you do not have -Os 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" "~# nano -w /etc/make.conf\n" "(Add -mno-tls-direct-seg-refs ONLY if you have a 32-bit dom0)\n" "(You don't need this flag if you have a 64-bit dom0)\n" "CFLAGS=\"-O2 -march=pentium4 -pipe -mno-tls-direct-seg-refs\"\n" "\n" "~# emerge -e world\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" "~# emerge xen xen-tools xen-sources\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 /usr/src/linux-2.6.x.z-xen, will be " "our main running kernel (i.e. the one running domain 0). In the XEN " "section you'll find drivers for all kinds of input/output, each driver " "having a backend and frontend implementation available. For " "the domain 0 kernel you need to select the backend implementation: " "these are used by the other domains (who use the frontend 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 Xen-compatible at Processor type " "and features. If you're wondering about networking: each interface in a " "domain has a point-to-point link to an interface on domain 0 (called " "vifX.Y 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 --->\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 --->\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.) --->\n" " [*] PCI support\n" " [ ] Xen PCI Frontend Debugging\n" "\n" "Networking --->\n" " Networking options --->\n" " <*> 802.1d Ethernet Bridging\n" " Only required by bridged networking.\n" "\n" "XEN --->\n" " [*] Privileged Guest (domain 0)\n" " <*> Backend driver support\n" " <*> Block-device backend driver\n" " <*> Network-device backend driver\n" " <*> PCI-device backend driver\n" " PCI Backend Mode (Virtual PCI) --->\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.) --->\n" " [ ] PCI support\n" "\n" "Device Drivers --->\n" " SCSI device support --->\n" " < > SCSI device support\n" " Disabling SCSI support frees up the /dev/sd* device names\n" " for use as Xen virtual block devices.\n" "\n" "XEN --->\n" " [ ] Privileged Guest (domain 0)\n" " <*> Block-device frontend driver\n" " <*> 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" "~# mkdir -p ~/build/dom0 ~/build/domU\n" "~# make O=~/build/dom0 menuconfig\n" "(Configure the kernel)\n" "~# make O=~/build/dom0 && make O=~/build/dom0 modules_install\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 arch/ or any other directory) " "called vmlinuz. Copy it to /boot and then " "configure your bootloader to use the Xen hypervisor (one of the components " "installed previously) which is stored as /boot/xen.gz. 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" "~# /etc/init.d/xend start\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 xendomains to the default runlevel as well and create a symlink in /etc/xen/" "auto/ 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 XEN settings where drivers should now have their frontend " "implementation selected instead of the backend. Then build the kernel " "and place the resulting vmlinuz file where you want (we assume " "this is /mnt/data/xen/kernel):" 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" "~# make O=~/build/domU\n" "~# cp ~/build/domU/vmlinuz /mnt/data/xen/kernel/kernel-2.6.x.y-xen\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 dd and mke2fs (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" "~# dd if=/dev/zero of=/mnt/data/xen/disks/ext3root.img bs=1M count=2048\n" "~# mke2fs -j /mnt/data/xen/disks/ext3root.img\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 /mnt/data/xen/" "configs. 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" "~# nano -w /mnt/data/xen/configs/gentoo\n" "\n" "kernel = \"/mnt/data/xen/kernel/kernel-2.6.x.y-xen\"\n" "memory = 512\n" "name = \"gentoo\"\n" "(Map the disk image to the virtual /dev/sda1)\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" "(LVM Volume)\n" "disk = [ 'phy:lvm/xen-guest-root,sda1,w' ]\n" "\n" "(Physical Partition)\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 /etc/xen." 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 xm 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" "~# xm create /mnt/data/xen/configs/gentoo -c\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 Ctrl+]. You " "can always reconnect to the domains' console using xm console gentoo. " "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: " "routed and bridged." msgstr "" #: ../../gentoo/xml/htdocs/doc/en//xen-guide.xml(p):392 msgid "" "When selecting the routed 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 eth0. 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 bridged 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 netloop and netbk drivers are loaded. A " "quick hint: if you have netloop as a module, load it with " "nloopbacks=0 so that it doesn't create pointless interfaces to the " "loopback device. Then, edit your domain configuration file and add a vif 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" "~# nano -w /mnt/data/xen/configs/gentoo\n" "\n" "(Add the vif instruction)\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 eth0) and Xen will ensure " "that address 192.168.1.101 will be reachable from the administrative domain " "through interface veth1." msgstr "" #: ../../gentoo/xml/htdocs/doc/en//xen-guide.xml(p):438 msgid "" "This doesn't mean that the virtual eth0 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 /etc/xen/xend-config.sxp 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" "~# nano -w /etc/xen/xend-config.sxp\n" "\n" "(Comment out the following lines)\n" "#(network-script network-bridge)\n" "#(vif-script vif-bridge)\n" "\n" "(Enable the following lines)\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 netloop " "driver with nloopbacks=1 (or higher) as the additional loopback " "devices are used to create the bridge. For the other modules you still need " "the netbk module as well as briding functionality " "(bridge 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 vif construct:" msgstr "" #: ../../gentoo/xml/htdocs/doc/en//xen-guide.xml(pre):480 #, no-wrap msgid "" "\n" "~# nano -w /mnt/data/xen/configs/gentoo\n" "\n" "(Add the vif instruction)\n" "vif = [ 'ip=192.168.1.101, vifname=veth0' ]\n" msgstr "" #: ../../gentoo/xml/htdocs/doc/en//xen-guide.xml(p):487 msgid "" "Next edit /etc/xen/xend-config.sxp as follows to select bridged " "network configuration:" msgstr "" #: ../../gentoo/xml/htdocs/doc/en//xen-guide.xml(pre):492 #, no-wrap msgid "" "\n" "~# nano -w /etc/xen/xend-config.sxp\n" "\n" "(Enable the following lines)\n" "(network-script network-bridge)\n" "(vif-script vif-bridge)\n" "\n" "(Comment out the following lines if not done already)\n" "# (network-script network-route)\n" "# (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 ip route list). If you want to alter this behavior, edit the " "xend-config.sxp 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" "~# nano -w /etc/xen/xend-config.sxp\n" "\n" "(Edit the network-script line)\n" "(network-script 'network-bridge netdev=eth0 bridge=xenbr0 vifnum=0')\n" msgstr "" #: ../../gentoo/xml/htdocs/doc/en//xen-guide.xml(p):518 msgid "" "Once the configuration is done, restart the xend 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" "~# /etc/init.d/xend restart\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://tx.downloads.xensource.com/downloads/docs/user/" msgstr "" #: ../../gentoo/xml/htdocs/doc/en//xen-guide.xml(uri):538 msgid "Xen Users' Manual" msgstr "" #: ../../gentoo/xml/htdocs/doc/en//xen-guide.xml(uri:link):542 msgid "http://xen.xensource.com/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 "" "app-emulation/virt-manager 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 ""