# SOME DESCRIPTIVE TITLE. # msgid "" msgstr "" "Project-Id-Version: Fedora Virtualization Guide\n" "Report-Msgid-Bugs-To: http://bugs.kde.org\n" "POT-Creation-Date: 2009-09-23 16:39+0000\n" "PO-Revision-Date: 2011-08-21 12:03+0000\n" "Last-Translator: FULL NAME \n" "Language-Team: Danish \n" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=UTF-8\n" "Content-Transfer-Encoding: 8bit\n" "Language: da\n" "Plural-Forms: nplurals=2; plural=(n != 1)\n" #. Tag: title #: Tips_and_Tricks.xml:6 #, no-c-format msgid "Tips and tricks" msgstr "" #. Tag: para #: Tips_and_Tricks.xml:63 #, no-c-format msgid "" "This chapter contain useful hints and tips to improve virtualization " "performance, scale and stability." msgstr "" #. Tag: title #: Tips_and_Tricks.xml:67 #, no-c-format msgid "Automatically starting guests" msgstr "" #. Tag: para #: Tips_and_Tricks.xml:68 #, no-c-format msgid "" "This section covers how to make virtualized guests start automatically " "during the host system's boot phase." msgstr "" #. Tag: para #: Tips_and_Tricks.xml:71 #, no-c-format msgid "" "This example uses virsh to set a guest, " "TestServer, to automatically start when the host " "boots." msgstr "" #. Tag: screen #: Tips_and_Tricks.xml:75 #, no-c-format msgid "" "# virsh autostart TestServer\n" "Domain TestServer marked as autostarted" msgstr "" #. Tag: para #: Tips_and_Tricks.xml:76 #, no-c-format msgid "The guest now automatically starts with the host." msgstr "" #. Tag: para #: Tips_and_Tricks.xml:79 #, no-c-format msgid "" "To stop a guest automatically booting use the " "--disable parameter" msgstr "" #. Tag: screen #: Tips_and_Tricks.xml:83 #, no-c-format msgid "" "# virsh autostart --disable TestServer\n" "Domain TestServer unmarked as autostarted" msgstr "" #. Tag: para #: Tips_and_Tricks.xml:84 #, no-c-format msgid "The guest no longer automatically starts with the host." msgstr "" #. Tag: title #: Tips_and_Tricks.xml:90 #, no-c-format msgid "Changing between the KVM and Xen hypervisors" msgstr "" #. Tag: para #: Tips_and_Tricks.xml:91 #, no-c-format msgid "This section covers changing between the KVM and Xen hypervisors." msgstr "" #. Tag: para #: Tips_and_Tricks.xml:94 #, no-c-format msgid "Red Hat only supports one active hypervisor at a time." msgstr "" #. Tag: title #: Tips_and_Tricks.xml:98 #, no-c-format msgid "Migrating virtualized guests between hypervisors" msgstr "" #. Tag: para #: Tips_and_Tricks.xml:99 #, no-c-format msgid "" "Presently, there is no application for switching Xen-based guests to KVM or " "KVM-based guests to Xen. Guests can only be used on the hypervisor type that" " they were created on." msgstr "" #. Tag: title #: Tips_and_Tricks.xml:104 Tips_and_Tricks.xml:378 #, no-c-format msgid "Warning" msgstr "" #. Tag: para #: Tips_and_Tricks.xml:105 #, no-c-format msgid "" "This procedure is only available for the Intel 64 or AMD64 version of Red " "Hat Enterprise Linux 5.4 or newer. No other configurations or Red Hat " "Enterprise Linux versions are supported. KVM is not available in versions " "earlier than Red Hat Enterprise Linux 5.4." msgstr "" #. Tag: title #: Tips_and_Tricks.xml:110 #, no-c-format msgid "Xen to KVM" msgstr "" #. Tag: para #: Tips_and_Tricks.xml:111 #, no-c-format msgid "" "The following procedure covers changing from the Xen hypervisor to the KVM " "hypervisor. This procedure assumes the kernel-xen package" " is installed and enabled." msgstr "" #. Tag: title #: Tips_and_Tricks.xml:116 #, no-c-format msgid "Install the KVM package" msgstr "" #. Tag: para #: Tips_and_Tricks.xml:117 #, no-c-format msgid "" "Install the kvm package if you have not already done so." msgstr "" #. Tag: screen #: Tips_and_Tricks.xml:121 #, no-c-format msgid "# yum install kvm" msgstr "" #. Tag: title #: Tips_and_Tricks.xml:124 Tips_and_Tricks.xml:182 #, no-c-format msgid "Verify which kernel is in use" msgstr "" #. Tag: para #: Tips_and_Tricks.xml:125 #, no-c-format msgid "" "The kernel-xen package may be installed. Use the " "uname command to determine which kernel is running:" msgstr "" #. Tag: screen #: Tips_and_Tricks.xml:129 Tips_and_Tricks.xml:213 #, no-c-format msgid "" "$ uname -r\n" "2.6.18-159.el5xen" msgstr "" #. Tag: para #: Tips_and_Tricks.xml:130 #, no-c-format msgid "" "The present kernel, \"2.6.18-159.el5xen\", is running on " "the system. If the default kernel, \"2.6.18-159.el5\", is" " running you can skip the substep." msgstr "" #. Tag: title #: Tips_and_Tricks.xml:135 #, no-c-format msgid "Changing the Xen kernel to the default kernel" msgstr "" #. Tag: para #: Tips_and_Tricks.xml:136 Tips_and_Tricks.xml:194 #, no-c-format msgid "" "The grub.conf file determines which kernel is booted. " "To change the default kernel edit the " "/boot/grub/grub.conf file as shown below." msgstr "" #. Tag: screen #: Tips_and_Tricks.xml:140 Tips_and_Tricks.xml:203 #, no-c-format msgid "" "default=1\n" "timeout=5\n" "splashimage=(hd0,0)/grub/splash.xpm.gz\n" "hiddenmenu\n" "title Red Hat Enterprise Linux Server (2.6.18-159.el5)\n" " root (hd0,0)\n" " kernel /vmlinuz-2.6.18-159.el5 ro root=/dev/VolGroup00/LogVol00 rhgb quiet\n" " initrd /initrd-2.6.18-159.el5.img\n" "title Red Hat Enterprise Linux Server (2.6.18-159.el5xen)\n" " root (hd0,0)\n" " kernel /xen.gz-2.6.18-159.el5\n" " module /vmlinuz-2.6.18-159.el5xen ro root=/dev/VolGroup00/LogVol00 rhgb quiet\n" " module /initrd-2.6.18-159.el5xen.img" msgstr "" #. Tag: para #: Tips_and_Tricks.xml:141 #, no-c-format msgid "" "Notice the default=1 parameter. This is " "instructing the GRUB boot loader to boot the second entry, the Xen kernel. " "Change the default to 0 (or the number for the " "default kernel):" msgstr "" #. Tag: screen #: Tips_and_Tricks.xml:145 Tips_and_Tricks.xml:198 #, no-c-format msgid "" "default=0\n" "timeout=5\n" "splashimage=(hd0,0)/grub/splash.xpm.gz\n" "hiddenmenu\n" "title Red Hat Enterprise Linux Server (2.6.18-159.el5)\n" " root (hd0,0)\n" " kernel /vmlinuz-2.6.18-159.el5 ro root=/dev/VolGroup00/LogVol00 rhgb quiet\n" " initrd /initrd-2.6.18-159.el5.img\n" "title Red Hat Enterprise Linux Server (2.6.18-159.el5xen)\n" " root (hd0,0)\n" " kernel /xen.gz-2.6.18-159.el5\n" " module /vmlinuz-2.6.18-159.el5xen ro root=/dev/VolGroup00/LogVol00 rhgb quiet\n" " module /initrd-2.6.18-159.el5xen.img" msgstr "" #. Tag: title #: Tips_and_Tricks.xml:150 Tips_and_Tricks.xml:208 #, no-c-format msgid "Reboot to load the new kernel" msgstr "" #. Tag: para #: Tips_and_Tricks.xml:151 #, no-c-format msgid "" "Reboot the system. The computer will restart with the default kernel. The " "KVM module should be automatically loaded with the kernel. Verify KVM is " "running:" msgstr "" #. Tag: screen #: Tips_and_Tricks.xml:155 #, no-c-format msgid "" "$ lsmod | grep kvm\n" "kvm_intel 85992 1 \n" "kvm 222368 2 ksm,kvm_intel" msgstr "" #. Tag: para #: Tips_and_Tricks.xml:156 #, no-c-format msgid "" "The kvm module and either the " "kvm_intel module or the kvm_amd module" " are present if everything worked." msgstr "" #. Tag: title #: Tips_and_Tricks.xml:165 #, no-c-format msgid "KVM to Xen" msgstr "" #. Tag: para #: Tips_and_Tricks.xml:166 #, no-c-format msgid "" "The following procedure covers changing from the KVM hypervisor to the Xen " "hypervisor. This procedure assumes the kvm package is " "installed and enabled." msgstr "" #. Tag: title #: Tips_and_Tricks.xml:171 #, no-c-format msgid "Install the Xen packages" msgstr "" #. Tag: para #: Tips_and_Tricks.xml:172 #, no-c-format msgid "" "Install the kernel-xen and xen package" " if you have not already done so." msgstr "" #. Tag: screen #: Tips_and_Tricks.xml:176 #, no-c-format msgid "# yum install kernel-xen xen" msgstr "" #. Tag: para #: Tips_and_Tricks.xml:177 #, no-c-format msgid "" "The kernel-xen package may be installed but disabled." msgstr "" #. Tag: para #: Tips_and_Tricks.xml:183 #, no-c-format msgid "" "Use the uname command to determine which kernel is " "running." msgstr "" #. Tag: screen #: Tips_and_Tricks.xml:187 #, no-c-format msgid "" "$ uname -r\n" "2.6.18-159.el5" msgstr "" #. Tag: para #: Tips_and_Tricks.xml:188 #, no-c-format msgid "" "The present kernel, \"2.6.18-159.el5\", is running on the" " system. This is the default kernel. If the kernel has " "xen on the end (for example, " "2.6.18-159.el5xen) then the Xen kernel is running and you" " can skip the substep." msgstr "" #. Tag: title #: Tips_and_Tricks.xml:193 #, no-c-format msgid "Changing the default kernel to the Xen kernel" msgstr "" #. Tag: para #: Tips_and_Tricks.xml:199 #, no-c-format msgid "" "Notice the default=0 parameter. This is " "instructing the GRUB boot loader to boot the first entry, the default " "kernel. Change the default to 1 (or the number for " "the Xen kernel):" msgstr "" #. Tag: para #: Tips_and_Tricks.xml:209 #, no-c-format msgid "" "Reboot the system. The computer will restart with the Xen kernel. Verify " "with the uname command:" msgstr "" #. Tag: para #: Tips_and_Tricks.xml:214 #, no-c-format msgid "" "If the output has xen on the end the Xen " "kernel is running." msgstr "" #. Tag: title #: Tips_and_Tricks.xml:225 #, no-c-format msgid "Using qemu-img" msgstr "" #. Tag: para #: Tips_and_Tricks.xml:226 #, no-c-format msgid "" "The qemu-img command line tool is used for formatting " "various file systems used by Xen and KVM. qemu-img should" " be used for formatting virtualized guest images, additional storage devices" " and network storage. qemu-img options and usages are " "listed below." msgstr "" #. Tag: title #: Tips_and_Tricks.xml:230 #, no-c-format msgid "Formatting and creating new images or devices" msgstr "" #. Tag: para #: Tips_and_Tricks.xml:231 #, no-c-format msgid "Create the new disk image filename of size size and format format." msgstr "" #. Tag: screen #: Tips_and_Tricks.xml:236 #, no-c-format msgid "" "# qemu-img create [-6] [-e] [-b base_image] [-f format] filename [size]" msgstr "" #. Tag: para #: Tips_and_Tricks.xml:237 #, no-c-format msgid "" "If base_image is specified, then the image will record only the differences " "from base_image. No size needs to be specified in this case. base_image will" " never be modified unless you use the \"commit\" monitor command." msgstr "" #. Tag: title #: Tips_and_Tricks.xml:243 #, no-c-format msgid "Convert an existing image to another format" msgstr "" #. Tag: para #: Tips_and_Tricks.xml:244 #, no-c-format msgid "" "The convert option is used for converting a recognized format to another " "image format." msgstr "" #. Tag: para #: Tips_and_Tricks.xml:248 #, no-c-format msgid "Command format:" msgstr "" #. Tag: screen #: Tips_and_Tricks.xml:252 #, no-c-format msgid "" "# qemu-img convert [-c] [-e] [-f format] filename [-O output_format] " "output_filename" msgstr "" #. Tag: para #: Tips_and_Tricks.xml:253 #, no-c-format msgid "" "convert the disk image filename to disk image output_filename using format " "output_format. it can be optionally encrypted (\"-e\" option) or compressed " "(\"-c\" option)." msgstr "" #. Tag: para #: Tips_and_Tricks.xml:256 #, no-c-format msgid "" "only the format \"qcow\" supports encryption or compression. the compression" " is read-only. it means that if a compressed sector is rewritten, then it is" " rewritten as uncompressed data." msgstr "" #. Tag: para #: Tips_and_Tricks.xml:259 #, no-c-format msgid "" "The encryption uses the AES format with very secure 128 bit keys. use a long" " password (16 characters) to get maximum protection." msgstr "" #. Tag: para #: Tips_and_Tricks.xml:262 #, no-c-format msgid "" "image conversion is also useful to get smaller image when using a format " "which can grow, such as qcow or cow. " "The empty sectors are detected and suppressed from the destination image." msgstr "" #. Tag: title #: Tips_and_Tricks.xml:266 #, no-c-format msgid "getting image information" msgstr "" #. Tag: para #: Tips_and_Tricks.xml:267 #, no-c-format msgid "" "the info parameter displays information about a disk " "image. the format for the info option is as follows:" msgstr "" #. Tag: screen #: Tips_and_Tricks.xml:272 #, no-c-format msgid "# qemu-img info [-f format] filename" msgstr "" #. Tag: para #: Tips_and_Tricks.xml:273 #, no-c-format msgid "" "give information about the disk image filename. use it in particular to know" " the size reserved on disk which can be different from the displayed size. " "if vm snapshots are stored in the disk image, they are displayed too." msgstr "" #. Tag: title #: Tips_and_Tricks.xml:277 #, no-c-format msgid "Supported formats" msgstr "" #. Tag: para #: Tips_and_Tricks.xml:278 #, no-c-format msgid "" "The format of an image is usually guessed automatically. The following " "formats are supported:" msgstr "" #. Tag: command #: Tips_and_Tricks.xml:284 #, no-c-format msgid "raw" msgstr "" #. Tag: para #: Tips_and_Tricks.xml:286 #, no-c-format msgid "" "Raw disk image format (default). This format has the advantage of being " "simple and easily exportable to all other emulators. If your file system " "supports holes (for example in ext2 or ext3 on Linux or NTFS on Windows), " "then only the written sectors will reserve space. Use qemu-img " "info to know the real size used by the image or ls " "-ls on Unix/Linux." msgstr "" #. Tag: command #: Tips_and_Tricks.xml:292 #, no-c-format msgid "qcow2" msgstr "" #. Tag: para #: Tips_and_Tricks.xml:294 #, no-c-format msgid "" "QEMU image format, the most versatile format. Use it to have smaller images " "(useful if your file system does not supports holes, for example: on " "Windows), optional AES encryption, zlib based compression and support of " "multiple VM snapshots." msgstr "" #. Tag: command #: Tips_and_Tricks.xml:300 #, no-c-format msgid "qcow" msgstr "" #. Tag: para #: Tips_and_Tricks.xml:302 #, no-c-format msgid "" "Old QEMU image format. Only included for compatibility with older versions." msgstr "" #. Tag: command #: Tips_and_Tricks.xml:308 #, no-c-format msgid "cow" msgstr "" #. Tag: para #: Tips_and_Tricks.xml:310 #, no-c-format msgid "" "User Mode Linux Copy On Write image format. The cow " "format is included only for compatibility with previous versions. It does " "not work with Windows." msgstr "" #. Tag: command #: Tips_and_Tricks.xml:316 #, no-c-format msgid "vmdk" msgstr "" #. Tag: para #: Tips_and_Tricks.xml:318 #, no-c-format msgid "VMware 3 and 4 compatible image format." msgstr "" #. Tag: command #: Tips_and_Tricks.xml:324 #, no-c-format msgid "cloop" msgstr "" #. Tag: para #: Tips_and_Tricks.xml:326 #, no-c-format msgid "" "Linux Compressed Loop image, useful only to reuse directly compressed CD-ROM" " images present for example in the Knoppix CD-ROMs." msgstr "" #. Tag: title #: Tips_and_Tricks.xml:335 #, no-c-format msgid "Overcommitting with KVM" msgstr "" #. Tag: para #: Tips_and_Tricks.xml:336 #, no-c-format msgid "" "The KVM hypervisor supports overcommitting CPUs and overcommitting memory. " "Overcommitting is allocating more virtualized CPUs or memory than there are " "physical resources on the system. With CPU overcommit, under-utilized " "virtualized servers or desktops can run on fewer servers which saves power " "and money." msgstr "" #. Tag: title #: Tips_and_Tricks.xml:340 #, no-c-format msgid "Xen support" msgstr "" #. Tag: para #: Tips_and_Tricks.xml:341 #, no-c-format msgid "" "CPU overcommitting is not supported for the Xen hypervisor. Overcommitting " "CPUs with the Xen hypervisor may cause system instability and crashes of the" " host and virtualized guests." msgstr "" #. Tag: title #: Tips_and_Tricks.xml:363 #, no-c-format msgid "Overcommitting memory" msgstr "" #. Tag: para #: Tips_and_Tricks.xml:364 #, no-c-format msgid "" "Most operating systems and applications do not use 100% of the available RAM" " all the time. This behavior can be exploited with KVM to use more memory " "for virtualized guests than what is physically available." msgstr "" #. Tag: para #: Tips_and_Tricks.xml:368 #, no-c-format msgid "" "With KVM, virtual machines are Linux processes. Guests on the KVM hypervisor" " do not have blocks of physical RAM assigned to them instead they function " "as processes. Each process is allocated memory when it requests more memory." " KVM uses this to allocate memory for guests when the guest operating system" " requests more or less memory. The guest only uses slightly more physical " "memory than the virtualized operating system appears to use." msgstr "" #. Tag: para #: Tips_and_Tricks.xml:371 #, no-c-format msgid "" "When physical memory is nearly completely used or a process is inactive for " "some time, Linux moves the process's memory to swap. Swap is usually a " "partition on a hard disk drive or solid state drive which Linux uses to " "extend virtual memory. Swap is significantly slower than RAM." msgstr "" #. Tag: para #: Tips_and_Tricks.xml:374 #, no-c-format msgid "" "As KVM virtual machines are Linux processes, memory used by virtualized " "guests can be put into swap if the guest is idle or not in heavy use. Memory" " can be committed over the total size of the swap and physical RAM. This can" " cause issues if virtualized guests use their total RAM. Without sufficient " "swap space for the virtual machine processes to be swapped to the " "pdflush process starts. pdflush kills " "processes to free memory so the system does not crash. " "pdflush may destroy virtualized guests or other system " "processes which may cause file system errors and may leave virtualized " "guests unbootable." msgstr "" #. Tag: para #: Tips_and_Tricks.xml:379 #, no-c-format msgid "" "If sufficient swap is not available guest operating systems will be forcibly" " shut down. This may leave guests inoperable. Avoid this by never " "overcommitting more memory than there is swap available." msgstr "" #. Tag: para #: Tips_and_Tricks.xml:383 #, no-c-format msgid "" "The swap partition is used for swapping underused memory to the hard drive " "to speed up memory performance. The default size of the swap partition is " "calculated from amount of RAM and overcommit ratio. It is recommended to " "make your swap partition larger if you intend to overcommit memory with KVM." " A recommended overcommit ratio is 50% (0.5). The formula used is:" msgstr "" #. Tag: screen #: Tips_and_Tricks.xml:387 #, no-c-format msgid "(0.5 * RAM) + (overcommit ratio * RAM) = Recommended swap size" msgstr "" #. Tag: para #: Tips_and_Tricks.xml:388 #, no-c-format msgid "" "Red Hat Knowledgebase has" " an article on safely and efficiently determining the size of the swap " "partition." msgstr "" #. Tag: para #: Tips_and_Tricks.xml:391 #, no-c-format msgid "" "It is possible to run with an overcommit ratio of ten times the number of " "virtualized guests over the the physical RAM. This only works with certain " "application loads (for example desktop virtualization with under 100% " "usage). Setting overcommit ratios is not a hard formula, you must test and " "customize the ratio for your environment." msgstr "" #. Tag: title #: Tips_and_Tricks.xml:395 #, no-c-format msgid "Overcommitting virtualized CPUs" msgstr "" #. Tag: para #: Tips_and_Tricks.xml:396 #, no-c-format msgid "" "The KVM hypervisor supports overcommitting virtualized CPUs. Virtualized " "CPUs can be overcommitted as far as load limits of virtualized guests allow." " Use caution when overcommitting VCPUs as loads near 100% may cause dropped " "requests or unusable response times." msgstr "" #. Tag: para #: Tips_and_Tricks.xml:400 #, no-c-format msgid "" "Virtualized CPUs are overcommitted best when each virtualized guest only has" " a single VCPU. The Linux scheduler is very efficient with this type of " "load. KVM should safely support guests with loads under 100% at a ratio of 5" " VCPUs Overcommitting single VCPU virtualized guests is not an issue." msgstr "" #. Tag: para #: Tips_and_Tricks.xml:403 #, no-c-format msgid "" "You cannot overcommit symmetric multiprocessing guests on more than the " "physical number of processing cores. For example a guest with four VCPUs " "should not be run on a host with a dual core processor. Overcommitting " "symmetric multiprocessing guests in over the physical number of processing " "cores will cause significant performance degradation." msgstr "" #. Tag: para #: Tips_and_Tricks.xml:406 #, no-c-format msgid "" "Assigning guests VCPUs up to the number of physical cores is appropriate and" " works as expected. For example, running virtualized guests with four VCPUs " "on a quad core host. Guests with less than 100% loads should function " "effectively in this setup." msgstr "" #. Tag: title #: Tips_and_Tricks.xml:410 #, no-c-format msgid "Always test first" msgstr "" #. Tag: para #: Tips_and_Tricks.xml:411 #, no-c-format msgid "" "Do not overcommit memory or CPUs in a production environment without " "extensive testing. Applications which use 100% of memory or processing " "resources may become unstable in overcommitted environments. Test before " "deploying." msgstr "" #. Tag: title #: Tips_and_Tricks.xml:418 #, no-c-format msgid "Modifying /etc/grub.conf" msgstr "" #. Tag: para #: Tips_and_Tricks.xml:419 #, no-c-format msgid "" "This section describes how to safely and correctly change your " "/etc/grub.conf file to use the virtualization kernel. " "You must use the xen kernel to use the Xen " "hypervisor. Copy your existing xen kernel entry " "make sure you copy all of the important lines or your system will panic upon" " boot (initrd will have a length of " "'0'). If you require xen" " hypervisor specific values you must append them to the " "xen line of your grub entry." msgstr "" #. Tag: para #: Tips_and_Tricks.xml:422 #, no-c-format msgid "" "The output below is an example of a grub.conf entry " "from a system running the kernel-xen package. The " "grub.conf on your system may vary. The important part " "in the example below is the section from the title line " "to the next new line." msgstr "" #. Tag: screen #: Tips_and_Tricks.xml:426 #, no-c-format msgid "" "#boot=/dev/sda\n" "default=0\n" "timeout=15\n" "#splashimage=(hd0,0)/grub/splash.xpm.gz hiddenmenu\n" "serial --unit=0 --speed=115200 --word=8 --parity=no --stop=1\n" "terminal --timeout=10 serial console\n" "\n" "title Red Hat Enterprise Linux Server (2.6.17-1.2519.4.21.el5xen)\n" " root (hd0,0)\n" " kernel /xen.gz-2.6.17-1.2519.4.21.el5 com1=115200,8n1\n" " module /vmlinuz-2.6.17-1.2519.4.21.el5xen ro root=/dev/VolGroup00/LogVol00\n" " module /initrd-2.6.17-1.2519.4.21.el5xen.img" msgstr "" #. Tag: title #: Tips_and_Tricks.xml:428 #, no-c-format msgid "An important point regarding editing grub.conf..." msgstr "" #. Tag: para #: Tips_and_Tricks.xml:429 #, no-c-format msgid "" "Your grub.conf could look very different if it has been" " manually edited before or copied from an example. Read for " "more information on using virtualization and grub." msgstr "" #. Tag: para #: Tips_and_Tricks.xml:433 #, no-c-format msgid "" "To set the amount of memory assigned to your host system at boot time to " "256MB you need to append dom0_mem=256M to " "the xen line in your " "grub.conf. A modified version of the grub configuration" " file in the previous example:" msgstr "" #. Tag: screen #: Tips_and_Tricks.xml:437 #, no-c-format msgid "" "#boot=/dev/sda\n" "default=0\n" "timeout=15\n" "#splashimage=(hd0,0)/grub/splash.xpm.gz\n" "hiddenmenu\n" "serial --unit=0 --speed=115200 --word=8 --parity=no --stop=1\n" "terminal --timeout=10 serial console\n" "\n" "title Red Hat Enterprise Linux Server (2.6.17-1.2519.4.21.el5xen)\n" " root (hd0,0)\n" " kernel /xen.gz-2.6.17-1.2519.4.21.el5 com1=115200,8n1 dom0_mem=256MB\n" " module /vmlinuz-2.6.17-1.2519.4.21.el5xen ro\n" " root=/dev/VolGroup00/LogVol00\n" " module /initrd-2.6.17-1.2519.4.21.el5xen.img" msgstr "" #. Tag: title #: Tips_and_Tricks.xml:441 #, no-c-format msgid "Verifying virtualization extensions" msgstr "" #. Tag: para #: Tips_and_Tricks.xml:442 #, no-c-format msgid "" "Use this section to determine whether your system has the hardware " "virtualization extensions. Virtualization extensions (Intel VT or AMD-V) are" " required for full virtualization." msgstr "" #. Tag: title #: Tips_and_Tricks.xml:446 #, no-c-format msgid "Can I use virtualization without the virtualization extensions?" msgstr "" #. Tag: para #: Tips_and_Tricks.xml:447 #, no-c-format msgid "" "If hardware virtualization extensions are not present you can use Xen para-" "virtualization with the Red Hat kernel-xen package." msgstr "" #. Tag: para #: Tips_and_Tricks.xml:451 #, no-c-format msgid "" "Run the following command to verify the CPU virtualization extensions are " "available:" msgstr "" #. Tag: screen #: Tips_and_Tricks.xml:455 #, no-c-format msgid "$ grep -E 'svm|vmx' /proc/cpuinfo" msgstr "" #. Tag: para #: Tips_and_Tricks.xml:456 #, no-c-format msgid "" "The following output contains a vmx entry " "indicating an Intel processor with the Intel VT extensions:" msgstr "" #. Tag: screen #: Tips_and_Tricks.xml:460 #, no-c-format msgid "" "flags : fpu tsc msr pae mce cx8 apic mtrr mca cmov pat pse36 clflush \n" " dts acpi mmx fxsr sse sse2 ss ht tm syscall lm constant_tsc pni monitor ds_cpl\n" " vmx est tm2 cx16 xtpr lahf_lm" msgstr "" #. Tag: para #: Tips_and_Tricks.xml:461 #, no-c-format msgid "" "The following output contains an svm entry " "indicating an AMD processor with the AMD-V extensions:" msgstr "" #. Tag: screen #: Tips_and_Tricks.xml:465 #, no-c-format msgid "" "flags : fpu tsc msr pae mce cx8 apic mtrr mca cmov pat pse36 clflush\n" " mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt lm 3dnowext 3dnow pni cx16\n" " lahf_lm cmp_legacy svm cr8legacy ts fid vid ttp tm stc" msgstr "" #. Tag: para #: Tips_and_Tricks.xml:466 #, no-c-format msgid "" "The \"flags:\" content may appear multiple " "times for each hyperthread, core or CPU on in the system." msgstr "" #. Tag: para #: Tips_and_Tricks.xml:469 #, no-c-format msgid "" "The virtualization extensions may be disabled in the BIOS. If the extensions" " do not appear or full virtualization does not work refer to ." msgstr "" #. Tag: title #: Tips_and_Tricks.xml:475 #, no-c-format msgid "Identifying guest type and implementation" msgstr "" #. Tag: para #: Tips_and_Tricks.xml:476 #, no-c-format msgid "" "The script below can identify if the environment an application or script is" " running in is a para-virtualized, a fully virtualized guest or on the " "hypervisor." msgstr "" #. Tag: screen #: Tips_and_Tricks.xml:480 #, no-c-format msgid "" "#!/bin/bash\n" "declare -i IS_HVM=0\n" "declare -i IS_PARA=0\n" "check_hvm()\n" "{\n" " IS_X86HVM=\"$(strings /proc/acpi/dsdt | grep int-xen)\"\n" " if [ x\"${IS_X86HVM}\" != x ]; then\n" " echo \"Guest type is full-virt x86hvm\"\n" " IS_HVM=1\n" " fi\n" "}\n" "check_para()\n" "{\n" " if $(grep -q control_d /proc/xen/capabilities); then\n" " echo \"Host is dom0\"\n" " IS_PARA=1\n" " else\n" " echo \"Guest is para-virt domU\"\n" " IS_PARA=1\n" " fi\n" "}\n" "if [ -f /proc/acpi/dsdt ]; then \n" " check_hvm\n" "fi\n" "\n" "if [ ${IS_HVM} -eq 0 ]; then\n" " if [ -f /proc/xen/capabilities ] ; then\n" " check_para\n" " fi\n" " fi\n" "if [ ${IS_HVM} -eq 0 -a ${IS_PARA} -eq 0 ]; then\n" " echo \"Baremetal platform\"\n" "fi" msgstr "" #. Tag: title #: Tips_and_Tricks.xml:482 #, no-c-format msgid "Examining hosts" msgstr "" #. Tag: para #: Tips_and_Tricks.xml:483 #, no-c-format msgid "" "For examining hosts, use the virsh capabilites command." msgstr "" #. Tag: title #: Tips_and_Tricks.xml:490 #, no-c-format msgid "Generating a new unique MAC address" msgstr "" #. Tag: para #: Tips_and_Tricks.xml:491 #, no-c-format msgid "" "In some case you will need to generate a new and unique MAC address for a guest. " "There is no command line tool available to generate a new MAC address at the" " time of writing. The script provided below can generate a new MAC address " "for your guests. Save the script to your guest as " "macgen.py. Now from that directory you can run the " "script using ./macgen.py . and it will generate a new MAC" " address. A sample output would look like the following:" msgstr "" #. Tag: screen #: Tips_and_Tricks.xml:495 #, no-c-format msgid "" "$ ./macgen.py \n" "00:16:3e:20:b0:11\n" " \n" "#!/usr/bin/python\n" "# macgen.py script to generate a MAC address for virtualized guests on Xen\n" "#\n" "import random\n" "#\n" "def randomMAC():\n" " mac = [ 0x00, 0x16, 0x3e,\n" " random.randint(0x00, 0x7f),\n" " random.randint(0x00, 0xff),\n" " random.randint(0x00, 0xff) ]\n" " return ':'.join(map(lambda x: \"%02x\" % x, mac))\n" "#\n" "print randomMAC()" msgstr "" #. Tag: title #: Tips_and_Tricks.xml:497 #, no-c-format msgid "Another method to generate a new MAC for your guest" msgstr "" #. Tag: para #: Tips_and_Tricks.xml:498 #, no-c-format msgid "" "You can also use the built-in modules of python-virtinst " "to generate a new MAC address and UUID for use in a guest" " configuration file:" msgstr "" #. Tag: screen #: Tips_and_Tricks.xml:503 #, no-c-format msgid "" "# echo 'import virtinst.util ; print\\\n" " virtinst.util.uuidToString(virtinst.util.randomUUID())' | python\n" "# echo 'import virtinst.util ; print virtinst.util.randomMAC()' | python" msgstr "" #. Tag: para #: Tips_and_Tricks.xml:504 #, no-c-format msgid "" "The script above can also be implemented as a script file as seen below." msgstr "" #. Tag: screen #: Tips_and_Tricks.xml:508 #, no-c-format msgid "" "#!/usr/bin/env python\n" "# -*- mode: python; -*-\n" "print \"\"\n" "print \"New UUID:\"\n" "import virtinst.util ; print virtinst.util.uuidToString(virtinst.util.randomUUID())\n" "print \"New MAC:\"\n" "import virtinst.util ; print virtinst.util.randomMAC()\n" "print \"\"" msgstr "" #. Tag: title #: Tips_and_Tricks.xml:512 #, no-c-format msgid "Limit network bandwidth for a Xen guest" msgstr "" #. Tag: para #: Tips_and_Tricks.xml:513 #, no-c-format msgid "" "In some environments it may be required to limit the network bandwidth " "available to certain guests. This can be used to implement basic Quality of " "Service on a host running multiple virtual machines. By default, the guest " "can use any bandwidth setting available which your physical network card " "supports. The physical network card must be mapped to one of virtual " "machine's virtual network interfaces. In Xen the " "“rate” parameter part of the VIF " "entries can throttle virtualized guests." msgstr "" #. Tag: para #: Tips_and_Tricks.xml:516 #, no-c-format msgid "This list covers the variables" msgstr "" #. Tag: command #: Tips_and_Tricks.xml:521 #, no-c-format msgid "rate" msgstr "" #. Tag: para #: Tips_and_Tricks.xml:523 #, no-c-format msgid "" "The rate= option can be added to the " "VIF= entry in a virtual machine " "configuration file to limit a virtual machine's network bandwidth or " "specify a specific time interval for a time window." msgstr "" #. Tag: term #: Tips_and_Tricks.xml:529 #, no-c-format msgid "time window" msgstr "" #. Tag: para #: Tips_and_Tricks.xml:531 #, no-c-format msgid "" "The time window is optional to the rate= " "option:" msgstr "" #. Tag: para #: Tips_and_Tricks.xml:534 #, no-c-format msgid "The default time window is 50ms." msgstr "" #. Tag: para #: Tips_and_Tricks.xml:537 #, no-c-format msgid "" "A smaller time window will provide less burst transmission, however, the " "replenishment rate and latency will increase." msgstr "" #. Tag: para #: Tips_and_Tricks.xml:540 #, no-c-format msgid "" "The default 50ms time window is a good balance between latency and " "throughput and in most cases will not require changing." msgstr "" #. Tag: para #: Tips_and_Tricks.xml:546 #, no-c-format msgid "Examples of rate parameter values and uses." msgstr "" #. Tag: computeroutput #: Tips_and_Tricks.xml:551 #, no-c-format msgid "rate=10Mb/s" msgstr "" #. Tag: para #: Tips_and_Tricks.xml:553 #, no-c-format msgid "Limit the outgoing network traffic from the guest to 10MB/s." msgstr "" #. Tag: computeroutput #: Tips_and_Tricks.xml:559 #, no-c-format msgid "rate=250KB/s" msgstr "" #. Tag: para #: Tips_and_Tricks.xml:561 #, no-c-format msgid "Limit the outgoing network traffic from the guest to 250KB/s." msgstr "" #. Tag: computeroutput #: Tips_and_Tricks.xml:567 #, no-c-format msgid "rate=10MB/s@50ms" msgstr "" #. Tag: para #: Tips_and_Tricks.xml:569 #, no-c-format msgid "" "Limit bandwidth to 10MB/s and provide the guest with a 50KB chunk every " "50ms." msgstr "" #. Tag: para #: Tips_and_Tricks.xml:575 #, no-c-format msgid "" "In the virtual machine configuration a sample VIF entry" " would look like the following:" msgstr "" #. Tag: screen #: Tips_and_Tricks.xml:579 #, no-c-format msgid "vif = [ 'rate=10MB/s , mac=00:16:3e:7a:55:1c, bridge=xenbr1']" msgstr "" #. Tag: para #: Tips_and_Tricks.xml:580 #, no-c-format msgid "" "This rate entry would limit the virtual " "machine's interface to 10MB/s for outgoing traffic" msgstr "" #. Tag: title #: Tips_and_Tricks.xml:594 #, no-c-format msgid "Configuring Xen processor affinities" msgstr "" #. Tag: para #: Tips_and_Tricks.xml:595 #, no-c-format msgid "" "Xen can allocate virtual CPUs to associate with one or more host CPUs. This " "allocates real processing resources to virtualized guests. This approach " "allows Red Hat Enterprise Linux optimize processor resources when employing " "dual-core, hyper-threading, or other CPU concurrency technologies. The Xen " "credit scheduler automatically balances virtual CPUs between physical ones, " "to maximize system use. Red Hat Enterprise Linux allows the credit scheduler" " to move CPUs around as necessary, as long as the virtual CPU is pinned to a" " physical CPU." msgstr "" #. Tag: para #: Tips_and_Tricks.xml:598 #, no-c-format msgid "" "If you are running I/O intensive tasks, it is recommended to dedicate either" " a hyperthread or an entire processor core to run domain0." msgstr "" #. Tag: para #: Tips_and_Tricks.xml:601 #, no-c-format msgid "" "Note that this is unnecessary for KVM as KVM uses the default Linux kernel " "scheduler." msgstr "" #. Tag: para #: Tips_and_Tricks.xml:604 #, no-c-format msgid "" "CPU affinities can be set with virsh or virt-" "manager:" msgstr "" #. Tag: para #: Tips_and_Tricks.xml:607 #, no-c-format msgid "" "To set CPU affinities using virsh refer to for more information." msgstr "" #. Tag: para #: Tips_and_Tricks.xml:610 #, no-c-format msgid "" "To configure and view CPU information with virt-manager " "refer to for more information." msgstr "" #. Tag: title #: Tips_and_Tricks.xml:616 #, no-c-format msgid "Modifying the Xen hypervisor" msgstr "" #. Tag: para #: Tips_and_Tricks.xml:617 #, no-c-format msgid "" "Managing host systems often involves changing the boot configuration file " "/boot/grub/grub.conf. Managing several or more hosts " "configuration files quickly becomes difficult. System administrators often " "prefer to use the 'cut and paste' method for editing multiple " "grub.conf files. If you do this, ensure you include all " "five lines in the Virtualization entry (or this will create system errors). " "Hypervisor specific values are all found on the " "'xen' line. This example represents a " "correct grub.conf virtualization entry:" msgstr "" #. Tag: screen #: Tips_and_Tricks.xml:621 #, no-c-format msgid "" "# boot=/dev/sda/\n" "default=0\n" "timeout=15\n" "#splashimage=(hd0, 0)/grub/splash.xpm.gz\n" "\n" "hiddenmenu\n" "serial --unit=0 --speed=115200 --word=8 --parity=no --stop=1\n" "terminal --timeout=10 serial console\n" "title Red Hat Enterprise Linux Server (2.6.17-1.2519.4.21. el5xen)\n" "root (hd0, 0)\n" "kernel /xen.gz-2.6.17-1.2519.4.21.el5 com1=115200,8n1\n" "module /vmlinuz-2.6.17-1.2519.4.21el5xen ro root=/dev/VolGroup00/LogVol00\n" "module /initrd-2.6.17-1.2519.4.21.el5xen.img" msgstr "" #. Tag: para #: Tips_and_Tricks.xml:622 #, no-c-format msgid "" "For example, to change the memory entry on your hypervisor (dom0) to 256MB " "at boot time, edit the 'xen' line and append it with this entry: " "'dom0_mem=256M'. This example a modified " "grub.conf with the hypervisor's memory entry " "modified." msgstr "" #. Tag: screen #: Tips_and_Tricks.xml:626 #, no-c-format msgid "" "# boot=/dev/sda\n" "default=0\n" "timeout=15\n" "#splashimage=(hd0,0)/grubs/splash.xpm.gz\n" "hiddenmenu\n" "serial --unit=0 --speed =115200 --word=8 --parity=no --stop=1\n" "terminal --timeout=10 serial console\n" "title Red Hat Enterprise Linux Server (2.6.17-1.2519.4.21. el5xen)\n" "root (hd0,0)\n" "kernel /xen.gz-2.6.17-1.2519.4.21.el5 com1=115200,8n1 dom0_mem=256MB\n" "module /vmlinuz-2.6.17-1.2519.4.21.el5xen ro\n" "root=/dev/VolGroup00/LogVol00\n" "module /initrd-2.6.17-1.2519.4.21.el5xen.img" msgstr "" #. Tag: title #: Tips_and_Tricks.xml:630 #, no-c-format msgid "Very Secure ftpd" msgstr "" #. Tag: para #: Tips_and_Tricks.xml:631 #, no-c-format msgid "" "vsftpd can provide access to " "installation trees for para-virtualized guests (for example, the Red Hat " "Enterprise Linux 5 repositories) or other data. If you have not installed " "vsftpd during the server " "installation you can grab the RPM package from your " "Server directory of your installation media and install" " it using the rpm -ivh vsftpd*.rpm (note that the RPM " "package must be in your current directory)." msgstr "" #. Tag: para #: Tips_and_Tricks.xml:636 #, no-c-format msgid "" "To configure vsftpd, edit " "/etc/passwd using vipw and change " "the ftp user's home directory to the directory where you are going to " "keep the installation trees for your para-virtualized guests. An example " "entry for the FTP user would look like the following:" msgstr "" #. Tag: screen #: Tips_and_Tricks.xml:640 #, no-c-format msgid "ftp:x:14:50:FTP User:/xen/pub:/sbin/nologin" msgstr "" #. Tag: para #: Tips_and_Tricks.xml:643 #, no-c-format msgid "" "to have vsftpd start automatically" " during system boot use the chkconfig utility to enable the automatic start " "up of vsftpd." msgstr "" #. Tag: para #: Tips_and_Tricks.xml:648 #, no-c-format msgid "" "verify that vsftpd is not enabled " "using the chkconfig --list vsftpd:" msgstr "" #. Tag: screen #: Tips_and_Tricks.xml:652 #, no-c-format msgid "" "$ chkconfig --list vsftpd\n" "vsftpd 0:off 1:off 2:off 3:off 4:off 5:off 6:off" msgstr "" #. Tag: para #: Tips_and_Tricks.xml:655 #, no-c-format msgid "" "run the chkconfig --levels 345 vsftpd on to start vsftpd " "automatically for run levels 3, 4 and 5." msgstr "" #. Tag: para #: Tips_and_Tricks.xml:660 #, no-c-format msgid "" "use the chkconfig --list vsftpd command to verify vsftdp " "has been enabled to start during system boot:" msgstr "" #. Tag: screen #: Tips_and_Tricks.xml:664 #, no-c-format msgid "" "$ chkconfig --list vsftpd\n" "vsftpd 0:off 1:off 2:off 3:on 4:on 5:on 6:off" msgstr "" #. Tag: para #: Tips_and_Tricks.xml:667 #, no-c-format msgid "" "use the service vsftpd start vsftpd to start the vsftpd " "service:" msgstr "" #. Tag: screen #: Tips_and_Tricks.xml:671 #, no-c-format msgid "" "$service vsftpd start vsftpd\n" "Starting vsftpd for vsftpd: [ OK ]" msgstr "" #. Tag: title #: Tips_and_Tricks.xml:677 #, no-c-format msgid "Configuring LUN Persistence" msgstr "" #. Tag: para #: Tips_and_Tricks.xml:678 #, no-c-format msgid "" "This section covers how to implement LUN persistence in guests and on the host " "machine with and without multipath." msgstr "" #. Tag: title #: Tips_and_Tricks.xml:682 #, no-c-format msgid "Implementing LUN persistence without multipath" msgstr "" #. Tag: para #: Tips_and_Tricks.xml:683 #, no-c-format msgid "" "If your system is not using multipath, you can use udev " "to implement LUN persistence. Before implementing LUN persistence in your " "system, ensure that you acquire the proper UUIDs. Once you acquire these, " "you can configure LUN persistence by editing the scsi_id " "file that resides in the /etc directory. Once you have " "this file open in a text editor, you must comment out this line:" msgstr "" #. Tag: screen #: Tips_and_Tricks.xml:688 #, no-c-format msgid "# options=-b" msgstr "" #. Tag: para #: Tips_and_Tricks.xml:689 #, no-c-format msgid "Then replace it with this parameter:" msgstr "" #. Tag: screen #: Tips_and_Tricks.xml:693 #, no-c-format msgid "# options=-g" msgstr "" #. Tag: para #: Tips_and_Tricks.xml:694 #, no-c-format msgid "" "This tells udev to monitor all system SCSI devices for returning UUIDs. To " "determine the system UUIDs, use the scsi_id command:" msgstr "" #. Tag: screen #: Tips_and_Tricks.xml:698 #, no-c-format msgid "" "# scsi_id -g -s /block/sdc\n" "*3600a0b80001327510000015427b625e*" msgstr "" #. Tag: para #: Tips_and_Tricks.xml:699 #, no-c-format msgid "" "The long string of characters in the output is the UUID. The UUID does not " "change when you add a new device to your system. Acquire the UUID for each " "the device in order to create rules for the devices. To create new device " "rules, edit the 20-names.rules file in the " "/etc/udev/rules.d directory. The device naming rules " "follow this format:" msgstr "" #. Tag: screen #: Tips_and_Tricks.xml:703 #, no-c-format msgid "" "# KERNEL=\"sd*\", BUS=\"scsi\", PROGRAM=\"sbin/scsi_id\", " "RESULT=\"UUID\", " "NAME=\"devicename\"" msgstr "" #. Tag: para #: Tips_and_Tricks.xml:704 #, no-c-format msgid "" "Replace your existing UUID and " "devicename with the above UUID retrieved entry. The " "rule should resemble the following:" msgstr "" #. Tag: screen #: Tips_and_Tricks.xml:708 #, no-c-format msgid "" "KERNEL=\"sd*\", BUS=\"scsi\", " "PROGRAM=\"sbin/scsi_id\", " "RESULT=\"3600a0b80001327510000015427b625e\", " "NAME=\"mydevicename\"" msgstr "" #. Tag: para #: Tips_and_Tricks.xml:709 #, no-c-format msgid "" "This enables all devices that match the /dev/sd* pattern " "to inspect the given UUID. When it finds a matching device, it creates a " "device node called /dev/devicename. For this " "example, the device node is /dev/mydevice . Finally, " "append the /etc/rc.local file with this line:" msgstr "" #. Tag: screen #: Tips_and_Tricks.xml:713 #, no-c-format msgid "/sbin/start_udev" msgstr "" #. Tag: title #: Tips_and_Tricks.xml:715 #, no-c-format msgid "Implementing LUN persistence with multipath" msgstr "" #. Tag: para #: Tips_and_Tricks.xml:716 #, no-c-format msgid "" "To implement LUN persistence in a multipath environment, you must define the" " alias names for the multipath devices. For this example, you must define " "four device aliases by editing the multipath.conf file " "that resides in the /etc/ directory:" msgstr "" #. Tag: screen #: Tips_and_Tricks.xml:721 #, no-c-format msgid "" "multipath { \n" " wwid 3600a0b80001327510000015427b625e\n" " alias oramp1\n" "}\n" "multipath { \n" " wwid 3600a0b80001327510000015427b6\n" " alias oramp2\n" "}\n" "multipath { \n" " wwid 3600a0b80001327510000015427b625e\n" " alias oramp3\n" "}\n" "multipath { \n" " wwid 3600a0b80001327510000015427b625e\n" " alias oramp4\n" "}" msgstr "" #. Tag: para #: Tips_and_Tricks.xml:722 #, no-c-format msgid "" "This defines 4 LUNs: /dev/mpath/oramp1, " "/dev/mpath/oramp2, /dev/mpath/oramp3, " "and dev/mpath/oramp4. The devices will reside in the " "/dev/mpath directory. These LUN names are persistent " "over reboots as it creates the alias names on the wwid of the LUNs." msgstr "" #. Tag: title #: Tips_and_Tricks.xml:728 #, no-c-format msgid "Disable SMART disk monitoring for guests" msgstr "" #. Tag: para #: Tips_and_Tricks.xml:729 #, no-c-format msgid "" "SMART disk monitoring can be disabled as we are running on virtual disks and" " the physical storage is managed by the host." msgstr "" #. Tag: screen #: Tips_and_Tricks.xml:731 #, no-c-format msgid "" "/sbin/service smartd stop\n" "/sbin/chkconfig --del smartd" msgstr "" #. Tag: title #: Tips_and_Tricks.xml:736 #, no-c-format msgid "Cleaning up old Xen configuration files" msgstr "" #. Tag: para #: Tips_and_Tricks.xml:737 #, no-c-format msgid "" "Over time you will see a number of files accumulate in " "/var/lib/xen, the usually named " "vmlinuz.****** and initrd.******. " "These files are the initrd and vmlinuz files from virtual machines which " "either failed to boot or failed for some other reason. These files are " "temporary files extracted from virtual machine's boot disk during the " "start up sequence. These files should be automatically removed after the " "virtual machine is shut down cleanly. Then you can safely delete old and " "stale copies from this directory." msgstr "" #. Tag: title #: Tips_and_Tricks.xml:743 #, no-c-format msgid "Configuring a VNC Server" msgstr "" #. Tag: para #: Tips_and_Tricks.xml:744 #, no-c-format msgid "" "To configure a VNC server use the Remote Desktop " "application in System > " "Preferences. Alternatively, you can run the vino-preferences command." msgstr "" #. Tag: para #: Tips_and_Tricks.xml:747 #, no-c-format msgid "The following steps set up a dedicated VNC server session:" msgstr "" #. Tag: para #: Tips_and_Tricks.xml:752 #, no-c-format msgid "" "Edit the ~/.vnc/xstartup file to start a GNOME session " "whenever vncserver is started. The first time you" " run the vncserver script it will ask you for a " "password you want to use for your VNC session." msgstr "" #. Tag: para #: Tips_and_Tricks.xml:757 #, no-c-format msgid "A sample xstartup file:" msgstr "" #. Tag: screen #: Tips_and_Tricks.xml:761 #, no-c-format msgid "" "#!/bin/sh\n" "# Uncomment the following two lines for normal desktop:\n" "# unset SESSION_MANAGER\n" "# exec /etc/X11/xinit/xinitrc\n" "[ -x /etc/vnc/xstartup ] && exec /etc/vnc/xstartup\n" "[ -r $HOME/.Xresources ] && xrdb $HOME/.Xresources\n" "#xsetroot -solid grey\n" "#vncconfig -iconic &\n" "#xterm -geometry 80x24+10+10 -ls -title \"$VNCDESKTOP Desktop\" &\n" "#twm &\n" "if test -z \"$DBUS_SESSION_BUS_ADDRESS\" ; then\n" " eval `dbus-launch --sh-syntax –exit-with-session`\n" " echo \"D-BUS per-session daemon address is: \\\n" " $DBUS_SESSION_BUS_ADDRESS\"\n" "fi\n" "exec gnome-session" msgstr "" #. Tag: title #: Tips_and_Tricks.xml:767 #, no-c-format msgid "Cloning guest configuration files" msgstr "" #. Tag: para #: Tips_and_Tricks.xml:768 #, no-c-format msgid "" "You can copy an existing configuration file to create an all new guest. You " "must modify the name parameter of the guests' configuration file. The " "new, unique name then appears in the hypervisor and is viewable by the " "management utilities. You must generate an all new UUID as well by using the" " uuidgen command. Then for the vif " "entries you must define a unique MAC address for each guest (if you are " "copying a guest configuration from an existing guest, you can create a " "script to handle it). For the xen bridge information, if you move an " "existing guest configuration file to a new host, you must update the " "xenbr entry to match your local networking configuration." " For the Device entries, you must modify the entries in the " "'disk=' section to point to the correct guest " "image." msgstr "" #. Tag: para #: Tips_and_Tricks.xml:771 #, no-c-format msgid "" "You must also modify these system configuration settings on your guest. You " "must modify the HOSTNAME entry of the " "/etc/sysconfig/network file to match the new guest's " "hostname." msgstr "" #. Tag: para #: Tips_and_Tricks.xml:774 #, no-c-format msgid "" "You must modify the HWADDR address of the " "/etc/sysconfig/network-scripts/ifcfg-eth0 file to match the " "output from ifconfig eth0 file and if you use static IP " "addresses, you must modify the IPADDR entry." msgstr "" #. Tag: title #: Tips_and_Tricks.xml:780 #, no-c-format msgid "Duplicating an existing guest and its configuration file" msgstr "" #. Tag: para #: Tips_and_Tricks.xml:781 #, no-c-format msgid "" "This section outlines copying an existing configuration file to create a new" " guest. There are key parameters in your guest's configuration file you " "must be aware of, and modify, to successfully duplicate a guest." msgstr "" #. Tag: computeroutput #: Tips_and_Tricks.xml:786 #, no-c-format msgid "name" msgstr "" #. Tag: para #: Tips_and_Tricks.xml:788 #, no-c-format msgid "" "The name of your guest as it is known to the hypervisor and displayed in the" " management utilities. This entry should be unique on your system." msgstr "" #. Tag: computeroutput #: Tips_and_Tricks.xml:794 #, no-c-format msgid "uuid" msgstr "" #. Tag: para #: Tips_and_Tricks.xml:796 #, no-c-format msgid "" "A unique handle for the guest, a new UUID can be regenerated using the " "uuidgen command. A sample UUID output:" msgstr "" #. Tag: screen #: Tips_and_Tricks.xml:800 #, no-c-format msgid "" "$ uuidgen \n" "a984a14f-4191-4d14-868e-329906b211e5" msgstr "" #. Tag: computeroutput #: Tips_and_Tricks.xml:804 #, no-c-format msgid "vif" msgstr "" #. Tag: para #: Tips_and_Tricks.xml:808 #, no-c-format msgid "" "The MAC " "address must define a unique MAC address for each guest. This is" " automatically done if the standard tools are used. If you are copying a " "guest configuration from an existing guest you can use the script ." msgstr "" #. Tag: para #: Tips_and_Tricks.xml:813 #, no-c-format msgid "" "If you are moving or duplicating an existing guest configuration file to a " "new host you have to make sure you adjust the " "xenbr entry to correspond with your local " "networking configuration (you can obtain the bridge information using the " "command brctl show command)." msgstr "" #. Tag: para #: Tips_and_Tricks.xml:818 #, no-c-format msgid "" "Device entries, make sure you adjust the entries in the " "disk= section to point to the correct guest image." msgstr "" #. Tag: para #: Tips_and_Tricks.xml:826 #, no-c-format msgid "Now, adjust the system configuration settings on your guest:" msgstr "" #. Tag: filename #: Tips_and_Tricks.xml:831 #, no-c-format msgid "/etc/sysconfig/network" msgstr "" #. Tag: para #: Tips_and_Tricks.xml:833 #, no-c-format msgid "" "Modify the HOSTNAME entry to the " "guest's new hostname." msgstr "" #. Tag: filename #: Tips_and_Tricks.xml:839 #, no-c-format msgid "/etc/sysconfig/network-scripts/ifcfg-eth0" msgstr "" #. Tag: para #: Tips_and_Tricks.xml:843 #, no-c-format msgid "" "Modify the HWADDR address to the output " "from ifconfig eth0" msgstr "" #. Tag: para #: Tips_and_Tricks.xml:848 #, no-c-format msgid "" "Modify the IPADDR entry if a static IP " "address is used." msgstr ""