# AUTHOR , YEAR. # msgid "" msgstr "" "Project-Id-Version: Fedora Virtualization Guide\n" "POT-Creation-Date: 2011-03-02T01:07:51\n" "PO-Revision-Date: 2011-08-21 06:59+0000\n" "Last-Translator: Automatically generated\n" "Language-Team: Russian (Russia) (http://www.transifex.net/projects/p/fedora/team/ru_RU/)\n" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=UTF-8\n" "Content-Transfer-Encoding: 8bit\n" "Language: ru_RU\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" #. Tag: title #, no-c-format msgid "Miscellaneous administration tasks" msgstr "" #. Tag: para #, no-c-format msgid "" "This chapter contain useful hints and tips to improve virtualization " "performance, scale and stability." msgstr "" #. Tag: title #, no-c-format msgid "Automatically starting guests" msgstr "" #. Tag: para #, no-c-format msgid "" "This section covers how to make virtualized guests start automatically " "during the host system's boot phase." msgstr "" #. Tag: para #, no-c-format msgid "" "This example uses virsh to set a guest, " "TestServer, to automatically start when the host " "boots." msgstr "" #. Tag: screen #, no-c-format msgid "" "# virsh autostart TestServer\n" "Domain TestServer marked as autostarted\n" msgstr "" #. Tag: para #, no-c-format msgid "The guest now automatically starts with the host." msgstr "" #. Tag: para #, no-c-format msgid "" "To stop a guest automatically booting use the " "--disable parameter" msgstr "" #. Tag: screen #, no-c-format msgid "" "# virsh autostart --disable TestServer\n" "Domain TestServer unmarked as autostarted\n" msgstr "" #. Tag: para #, no-c-format msgid "The guest no longer automatically starts with the host." msgstr "" #. Tag: title #, no-c-format msgid "Using qemu-img" msgstr "" #. Tag: para #, no-c-format msgid "" "The qemu-img command line tool is used for formatting " "various file systems used by 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 #, no-c-format msgid "Formatting and creating new images or devices" msgstr "" #. Tag: para #, no-c-format msgid "" "Create the new disk image filename of size " "size and format format." msgstr "" #. Tag: screen #, no-c-format msgid "" "# qemu-img create [-6] [-e] [-b base_image] [-f " "format] filename " "[size]\n" msgstr "" #. Tag: para #, 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 #, no-c-format msgid "Convert an existing image to another format" msgstr "" #. Tag: para #, no-c-format msgid "" "The convert option is used for converting a " "recognized format to another image format." msgstr "" #. Tag: para #, no-c-format msgid "Command format:" msgstr "" #. Tag: screen #, no-c-format msgid "" "# qemu-img convert [-c] [-e] [-f format] filename [-O output_format] output_filename\n" "\t\t" msgstr "" #. Tag: para #, no-c-format msgid "" "Convert the disk image filename to disk image " "output_filename using format " "output_format. The disk image can be optionally " "encrypted with the -e option or compressed with the " "-c option." msgstr "" #. Tag: para #, no-c-format msgid "" "Only the qcow format 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 #, no-c-format msgid "" "The encryption uses the AES format with very secure 128-bit keys. Use a long" " password (over 16 characters) to get maximum protection." msgstr "" #. Tag: para #, 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 #, no-c-format msgid "getting image information" msgstr "" #. Tag: para #, 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 #, no-c-format msgid "# qemu-img info [-f format] filename\n" msgstr "" #. Tag: para #, 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 #, no-c-format msgid "Supported formats" msgstr "" #. Tag: para #, no-c-format msgid "" "The format of an image is usually guessed automatically. The following " "formats are supported:" msgstr "" #. Tag: term #, no-c-format msgid "raw" msgstr "" #. Tag: para #, 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: term #, no-c-format msgid "qcow2" msgstr "" #. Tag: para #, 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: term #, no-c-format msgid "qcow" msgstr "" #. Tag: para #, no-c-format msgid "" "Old QEMU image format. Only included for compatibility with older versions." msgstr "" #. Tag: term #, no-c-format msgid "cow" msgstr "" #. Tag: para #, 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: term #, no-c-format msgid "vmdk" msgstr "" #. Tag: para #, no-c-format msgid "VMware 3 and 4 compatible image format." msgstr "" #. Tag: term #, no-c-format msgid "cloop" msgstr "" #. Tag: para #, 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 #, no-c-format msgid "Overcommitting with KVM" msgstr "" #. Tag: para #, 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 #, no-c-format msgid "Overcommitting memory" msgstr "" #. Tag: para #, 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. KVM can allocate " "more memory for virtualized guests than the host has physically available." msgstr "" #. Tag: para #, no-c-format msgid "" "With KVM, virtual machines are Linux processes. Guests on the KVM hypervisor" " do not have dedicated blocks of physical RAM assigned to them, instead " "guests function as Linux processes. The Linux kernel allocates each process " "memory when the process requests more memory. KVM guests are allocated " "memory when requested by the guest operating system. The guest only requires" " slightly more physical memory than the virtualized operating system reports" " as used. The Linux kernel swaps infrequently used memory out of physical " "memory and into virtual memory. Swapping decreases the amount of memory " "required by virtualized guests." msgstr "" #. Tag: para #, no-c-format msgid "" "When physical memory is 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 due to the throughput and " "response times of hard drives and solid state drives." msgstr "" #. Tag: para #, no-c-format msgid "" "As KVM virtual machines are Linux processes, underused or idle memory of " "virtualized guests is moved by default to swap. The total memory used by " "guests can be overcommitted, which is to use more than the physically " "available host memory. Overcommitting requires sufficient swap space for all" " guests and all host processes." msgstr "" #. Tag: para #, no-c-format msgid "" "Without sufficient swap space for all processes in virtual memory the " "pdflush process, the cleanup process, starts. The " "pdflush process 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.This can cause issues if virtualized " "guests use their total RAM." msgstr "" #. Tag: title #, no-c-format msgid "Warning" msgstr "" #. Tag: para #, 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: title #, no-c-format msgid "With KSM" msgstr "" #. Tag: para #, no-c-format msgid "" "If KSM is used ensure the swap size is sufficient for the overcommitted RAM." " KSM reduces the RAM usage of identical or similar guests. Overcommitting " "guests with KSM without sufficient swap may be possible but is not " "recommended. For more information on KSM and overcommitting, refer to ." msgstr "" #. Tag: title #, no-c-format msgid "Configuring swap for overcommitting memory" msgstr "" #. Tag: para #, 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 the physical RAM of the host." msgstr "" #. Tag: para #, no-c-format msgid "" "Red Hat Knowledgebase has" " an article on safely and efficiently determining the size of the swap " "partition." msgstr "" #. Tag: para #, no-c-format msgid "" "The swap partition must be large enough to provide virtual memory for all " "guests and the host system." msgstr "" #. Tag: title #, no-c-format msgid "Important" msgstr "" #. Tag: para #, no-c-format msgid "" "The example below is provided as a guide for configuring swap only. The " "settings listed may not be appropriate for your environment." msgstr "" #. Tag: title #, no-c-format msgid "Memory overcommit example" msgstr "" #. Tag: para #, no-c-format msgid "" "ExampleServer1 has 32GB of RAM. The system is being configured to run 56 " "guests with 1GB of virtualized memory. The host system rarely uses more than" " 4GB of memory for system processes, drivers and storage caching." msgstr "" #. Tag: para #, no-c-format msgid "" "32GB minus 4GB for the host leaves 28GB of physical RAM for virtualized " "guests. Each guest uses 1GB of RAM, a total of 56GB of virtual RAM is " "required for the guests." msgstr "" #. Tag: para #, no-c-format msgid "" "The Red Hat Knowledgebase recommends 8GB of swap for a system with 32GB of " "RAM. To safely overcommit memory there must be sufficient virtual memory for" " all guests and the host. The host has 28GB of RAM for guests (which need " "56GB of RAM). Therefore, the system needs at least 28GB of swap for the " "guests." msgstr "" #. Tag: para #, no-c-format msgid "" "ExampleServer1 requires at least 36GB (8GB for the host and 28GB for the " "guests) of swap to safely overcommit for all 56 guests." msgstr "" #. Tag: para #, no-c-format msgid "" "It is possible to overcommit memory over ten times the amount of physical " "RAM in the system. This only works with certain types of guest, for example," " desktop virtualization with minimal intensive usage or running several " "identical guests with KSM. Configuring swap and memory overcommit is not a " "formula, each environment and setup is different. Your environment must be " "tested and customized to ensure stability and performance." msgstr "" #. Tag: para #, no-c-format msgid "" "For more information on KSM and overcommitting, refer to ." msgstr "" #. Tag: title #, no-c-format msgid "Overcommitting virtualized CPUs" msgstr "" #. Tag: para #, 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 #, 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 " "five VCPUs. Overcommitting single VCPU virtualized guests is not an issue." msgstr "" #. Tag: para #, 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 #, 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 #, no-c-format msgid "Always test first" msgstr "" #. Tag: para #, 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 #, no-c-format msgid "Verifying virtualization extensions" msgstr "" #. Tag: para #, 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: para #, no-c-format msgid "" "Run the following command to verify the CPU virtualization extensions are " "available:" msgstr "" #. Tag: screen #, no-c-format msgid "$ grep -E 'svm|vmx' /proc/cpuinfo\n" msgstr "" #. Tag: para #, no-c-format msgid "Analyze the output." msgstr "" #. Tag: para #, no-c-format msgid "" "The following output contains a vmx entry " "indicating an Intel processor with the Intel VT extensions:" msgstr "" #. Tag: screen #, no-c-format msgid "" "flags : fpu tsc msr pae mce cx8 apic mtrr mca cmov pat pse36 clflush \n" "\tdts acpi mmx fxsr sse sse2 ss ht tm syscall lm constant_tsc pni monitor ds_cpl\n" "\tvmx est tm2 cx16 xtpr lahf_lm\n" msgstr "" #. Tag: para #, no-c-format msgid "" "The following output contains an svm entry " "indicating an AMD processor with the AMD-V extensions:" msgstr "" #. Tag: screen #, no-c-format msgid "" "flags : fpu tsc msr pae mce cx8 apic mtrr mca cmov pat pse36 clflush\n" "\tmmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt lm 3dnowext 3dnow pni cx16\n" "\tlahf_lm cmp_legacy svm cr8legacy ts fid vid ttp tm stc\n" msgstr "" #. Tag: para #, no-c-format msgid "" "If any output is received, the processor has the hardware virtualization " "extensions. However in some circumstances manufacturers disable the " "virtualization extensions in BIOS." msgstr "" #. Tag: para #, no-c-format msgid "" "The \"flags:\" output content may appear " "multiple times, once for each hyperthread, core or CPU on the system." msgstr "" #. Tag: para #, 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 #, no-c-format msgid "For users of the KVM hypervisor" msgstr "" #. Tag: para #, no-c-format msgid "" "If the kvm package is installed. I As an additional check, verify that the " "kvm modules are loaded in the kernel:" msgstr "" #. Tag: screen #, no-c-format msgid "# lsmod | grep kvm\n" msgstr "" #. Tag: para #, no-c-format msgid "" "If the output includes kvm_intel or " "kvm_amd then the " "kvm hardware virtualization modules are " "loaded and your system meets requirements. sudo" msgstr "" #. Tag: title #, no-c-format msgid "Additional output" msgstr "" #. Tag: para #, no-c-format msgid "" "If the libvirt package is installed, the " "virsh command can output a full list of virtualization " "system capabilities. Run virsh capabilies as root to " "receive the complete list." msgstr "" #. Tag: title #, no-c-format msgid "Generating a new unique MAC address" msgstr "" #. Tag: para #, 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 #, no-c-format msgid "" "$ ./macgen.py \n" "00:16:3e:20:b0:11\n" "\t\n" "#!/usr/bin/python\n" "# macgen.py script to generate a MAC address for virtualized guests\n" "#\n" "import random\n" "#\n" "def randomMAC():\n" "\tmac = [ 0x00, 0x16, 0x3e,\n" "\t\trandom.randint(0x00, 0x7f),\n" "\t\trandom.randint(0x00, 0xff),\n" "\t\trandom.randint(0x00, 0xff) ]\n" "\treturn ':'.join(map(lambda x: \"%02x\" % x, mac))\n" "#\n" "print randomMAC()\n" msgstr "" #. Tag: title #, no-c-format msgid "Another method to generate a new MAC for your guest" msgstr "" #. Tag: para #, 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 #, 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\n" msgstr "" #. Tag: para #, no-c-format msgid "" "The script above can also be implemented as a script file as seen below." msgstr "" #. Tag: screen #, 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 \"\"\n" msgstr "" #. Tag: title #, no-c-format msgid "Improving guest response time" msgstr "" #. Tag: para #, no-c-format msgid "" "Virtualized guests can sometimes be slow to respond with certain workloads " "and usage patterns. Examples of situations which may cause slow or " "unresponsive guests:" msgstr "" #. Tag: para #, no-c-format msgid "Severely overcommitted memory." msgstr "" #. Tag: para #, no-c-format msgid "Overcommitted memory with high processor usage" msgstr "" #. Tag: para #, no-c-format msgid "" "Other (not qemu-kvm processes) busy or stalled processes " "on the host." msgstr "" #. Tag: para #, no-c-format msgid "" "These types of workload may cause guests to appear slow or unresponsive. " "Usually, the guests memory is eventually fully loaded from swap into the " "hosts main memory. Once the guest is loaded in main memory, the guest will " "preform normally. Note, the process of loading a guest from swap to main " "memory may take several seconds per gigabyte of RAM assigned to the guest " "depending on the type of storage used for swap and the performance of the " "components." msgstr "" #. Tag: para #, no-c-format msgid "" "KVM virtualized guests function as Linux processes. Linux processes are not " "permanently kept in main memory (physical RAM). The kernel scheduler swaps " "process memory into virtual memory (swap). Swap, with conventional hard disk" " drives, is thousands of times slower than main memory in modern computers. " "If a guest is inactive for long periods of time, the guest may be placed " "into swap by the kernel." msgstr "" #. Tag: para #, no-c-format msgid "" "KVM virtualized guests processes may be moved to swap regardless of whether " "memory is overcommitted or overall memory usage." msgstr "" #. Tag: para #, no-c-format msgid "" "In extreme circumstances, for example, using unsafe overcommit levels or " "overcommit with swap turned off, guest processes can be killed by the " "pdflush kernel function. pdflush " "automatically kills processes to keep the system from crashing and to free " "up memory. Be aware of the function of the" msgstr "" #. Tag: para #, no-c-format msgid "" "For more information on overcommitting with KVM, refer to ." msgstr "" #. Tag: title #, no-c-format msgid "Warning: turning off swap" msgstr "" #. Tag: para #, no-c-format msgid "" "Virtual memory is useful to Linux and improves performance and memory " "utilization. Turning it off will remove these benefits." msgstr "" #. Tag: para #, no-c-format msgid "" "If swap is turned off, do not overcommit guests. Overcommitting guests " "without swap may cause guests or the host system to crash." msgstr "" #. Tag: title #, no-c-format msgid "Turning off swap" msgstr "" #. Tag: para #, no-c-format msgid "" "Swap usage can be completely turned off to prevent guests from being " "unresponsive while they are moved back to main memory. This may improve " "performance but will expose the system to certain risks." msgstr "" #. Tag: para #, no-c-format msgid "" "The swapoff command can disable all swap partitions and " "swap files on a system." msgstr "" #. Tag: screen #, no-c-format msgid "# swapoff -a" msgstr "" #. Tag: para #, no-c-format msgid "" "To make this change permanent, remove swap lines from" " the /etc/fstab file and restart the host system." msgstr "" #. Tag: title #, no-c-format msgid "Using SSDs for swap" msgstr "" #. Tag: para #, no-c-format msgid "" "Using Solid State Drives (SSDs) for swap storage may improve the performance" " of virtualized guests." msgstr "" #. Tag: para #, no-c-format msgid "" "Using RAID arrays, faster disks or separate drives dedicated to swap may " "also improve performance." msgstr "" #. Tag: title #, no-c-format msgid "Very Secure ftpd" msgstr "" #. Tag: para #, no-c-format msgid "" "vsftpd can provide access to " "installation trees for para-virtualized guests (for example, the Fedora " "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 #, 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 guests. An example entry for the FTP user " "would look like the following:" msgstr "" #. Tag: screen #, no-c-format msgid "ftp:x:14:50:FTP User:/installtree/:/sbin/nologin\n" msgstr "" #. Tag: para #, no-c-format msgid "" "Verify that vsftpd is not enabled " "using the chkconfig --list vsftpd:" msgstr "" #. Tag: screen #, no-c-format msgid "" "$ chkconfig --list vsftpd\n" "vsftpd 0:off 1:off 2:off 3:off 4:off 5:off 6:off\n" msgstr "" #. Tag: para #, 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 #, no-c-format msgid "" "Use the chkconfig --list vsftpd command to verify the " "vsftpd daemon is enabled to start during system boot:" msgstr "" #. Tag: screen #, no-c-format msgid "" "$ chkconfig --list vsftpd\n" "vsftpd 0:off 1:off 2:off 3:on 4:on 5:on 6:off\n" msgstr "" #. Tag: para #, no-c-format msgid "" "use the service vsftpd start vsftpd to start the vsftpd " "service:" msgstr "" #. Tag: screen #, no-c-format msgid "" "$service vsftpd start vsftpd\n" "Starting vsftpd for vsftpd: [ OK ]\n" msgstr "" #. Tag: title #, no-c-format msgid "Disable SMART disk monitoring for guests" msgstr "" #. Tag: para #, no-c-format msgid "" "SMART disk monitoring can be safely disabled as virtual disks and the " "physical storage devices are managed by the host." msgstr "" #. Tag: screen #, no-c-format msgid "" "# service smartd stop\n" "# chkconfig --del smartd\n" msgstr "" #. Tag: title #, no-c-format msgid "Configuring a VNC Server" msgstr "" #. Tag: para #, 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 #, no-c-format msgid "The following steps set up a dedicated VNC server session:" msgstr "" #. Tag: para #, 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 #, no-c-format msgid "A sample xstartup file:" msgstr "" #. Tag: screen #, 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" "\teval `dbus-launch --sh-syntax –exit-with-session`\n" "\techo \"D-BUS per-session daemon address is: \\\n" "\t$DBUS_SESSION_BUS_ADDRESS\"\n" "fi\n" "exec gnome-session\n" msgstr "" #. Tag: title #, no-c-format msgid "Gracefully shutting down guests" msgstr "" #. Tag: para #, no-c-format msgid "" "Installing virtualized Red Hat Enterprise Linux 6 guests with the " " installation option will not install " "the acpid package." msgstr "" #. Tag: para #, no-c-format msgid "" "Without the acpid package, the Red Hat Enterprise Linux 6" " guest does not shut down when the virsh shutdown command" " is executed. The virsh shutdown command is designed to " "gracefully shut down virtualized guests." msgstr "" #. Tag: para #, no-c-format msgid "" "Using virsh shutdown is easier amd safer for system " "administration. Without graceful shut down with the virsh " "shutdown command a system administrator must log into a " "virtualized guest manually or send the " "Ctrl-Alt-Del key " "combination to each guest." msgstr "" #. Tag: title #, no-c-format msgid "Other virtualized operating systems" msgstr "" #. Tag: para #, no-c-format msgid "" "Other virtualized operating systems may be affected by this issue. The " "virsh shutdown command requires that the guest operating " "system is configured to handle ACPI shut down requests. Many operating " "systems require additional configuration on the guest operating system to " "accept ACPI shut down requests." msgstr "" #. Tag: title #, no-c-format msgid "Workaround for Red Hat Enteprise Linux 6" msgstr "" #. Tag: title #, no-c-format msgid "Install the acpid package" msgstr "" #. Tag: para #, no-c-format msgid "" "The acpid service listen and processes ACPI requests." msgstr "" #. Tag: para #, no-c-format msgid "" "Log into the guest and install the acpid package on the " "guest:" msgstr "" #. Tag: screen #, no-c-format msgid "# yum install acpid" msgstr "" #. Tag: title #, no-c-format msgid "Enable the acpid service" msgstr "" #. Tag: para #, no-c-format msgid "" "Set the acpid service to start " "during the guest boot sequence and start the service:" msgstr "" #. Tag: screen #, no-c-format msgid "" "# chkconfig acpid on\n" "# service acpid start" msgstr "" #. Tag: para #, no-c-format msgid "" "The guest is now configured to shut down when the virsh " "shutdown command is used." msgstr ""