# AUTHOR , YEAR. # msgid "" msgstr "" "Project-Id-Version: Fedora Virtualization Guide\n" "POT-Creation-Date: 2011-03-02T01:07:52\n" "PO-Revision-Date: 2011-08-21 12:10+0000\n" "Last-Translator: Automatically generated\n" "Language-Team: Czech (http://www.transifex.net/projects/p/fedora/team/cs/)\n" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=UTF-8\n" "Content-Transfer-Encoding: 8bit\n" "Language: cs\n" "Plural-Forms: nplurals=3; plural=(n==1) ? 0 : (n>=2 && n<=4) ? 1 : 2\n" #. Tag: title #, no-c-format msgid "Troubleshooting" msgstr "" #. Tag: para #, no-c-format msgid "" "This chapter covers common problems and solutions with Fedora " "virtualization." msgstr "" #. Tag: para #, no-c-format msgid "" "This chapter is to give you, the reader, a background to identify where " "problems with virtualization technologies are. Troubleshooting takes " "practice and experience which are difficult to learn from a book. It is " "recommended that you experiment and test virtualization on Fedora to develop" " your troubleshooting skills." msgstr "" #. Tag: para #, no-c-format msgid "" "If you cannot find the answer in this document there may be an answer online" " from the virtualization community. Refer to for a list of " "Linux virtualization websites." msgstr "" #. Tag: title #, no-c-format msgid "Debugging and troubleshooting tools" msgstr "" #. Tag: para #, no-c-format msgid "" "This section summarizes the System Administrator applications, the " "networking utilities, and debugging tools. You can employ these standard " "System administration tools and logs to assist with troubleshooting:" msgstr "" #. Tag: para #, no-c-format msgid "kvm_stat" msgstr "" #. Tag: para #, no-c-format msgid "kvmtrace" msgstr "" #. Tag: para #, no-c-format msgid "vmstat" msgstr "" #. Tag: para #, no-c-format msgid "iostat" msgstr "" #. Tag: para #, no-c-format msgid "lsof" msgstr "" #. Tag: para #, no-c-format msgid "systemtap" msgstr "" #. Tag: para #, no-c-format msgid "crash" msgstr "" #. Tag: para #, no-c-format msgid "sysrq" msgstr "" #. Tag: para #, no-c-format msgid "sysrq t" msgstr "" #. Tag: para #, no-c-format msgid "sysrq w" msgstr "" #. Tag: para #, no-c-format msgid "" "These networking tools can assist with troubleshooting virtualization " "networking problems:" msgstr "" #. Tag: para #, no-c-format msgid "ifconfig" msgstr "" #. Tag: para #, no-c-format msgid "tcpdump" msgstr "" #. Tag: para #, no-c-format msgid "" "The tcpdump command 'sniffs' network packets. " "tcpdump is useful for finding network abnormalities and " "problems with network authentication. There is a graphical version of " "tcpdump named wireshark." msgstr "" #. Tag: para #, no-c-format msgid "brctl" msgstr "" #. Tag: para #, no-c-format msgid "" "brctl is a networking tool that inspects and configures " "the Ethernet bridge configuration in the Virtualization linux kernel. You " "must have root access before performing these example commands:" msgstr "" #. Tag: screen #, no-c-format msgid "" "# brctl show \n" "bridge-name bridge-id STP enabled interfaces \n" "-----------------------------------------------------------------------------\n" "virtbr0 8000.feffffff yes eth0\n" "\n" "# brctl showmacs virtbr0 \n" "port-no mac-addr local? aging timer\n" "1 fe:ff:ff:ff:ff: yes 0.00\n" "2 fe:ff:ff:fe:ff: yes 0.00\n" "# brctl showstp virtbr0\n" "virtbr0 \n" "bridge-id 8000.fefffffffff\n" "designated-root 8000.fefffffffff\n" "root-port 0 path-cost 0\n" "max-age 20.00 bridge-max-age 20.00\n" "hello-time 2.00 bridge-hello-time 2.00\n" "forward-delay 0.00 bridge-forward-delay 0.00\n" "aging-time 300.01\n" "hello-timer 1.43 tcn-timer 0.00\n" "topology-change-timer 0.00 gc-timer 0.02\n" msgstr "" #. Tag: para #, no-c-format msgid "" "Listed below are some other useful commands for troubleshooting " "virtualization." msgstr "" #. Tag: para #, no-c-format msgid "" "strace is a command which traces system calls and" " events received and used by another process." msgstr "" #. Tag: para #, no-c-format msgid "" "vncviewer: connect to a VNC server running on " "your server or a virtual machine. Install " "vncviwer using the yum install " "vnc command." msgstr "" #. Tag: para #, no-c-format msgid "" "vncserver: start a remote desktop on your server." " Gives you the ability to run graphical user interfaces such as virt-manager" " via a remote session. Install vncserver using " "the yum install vnc-server command." msgstr "" #. Tag: title #, no-c-format msgid "Log files" msgstr "" #. Tag: para #, no-c-format msgid "" "KVM uses various log files. All the log files are standard ASCII files, and " "accessible with a text editor." msgstr "" #. Tag: para #, no-c-format msgid "" "The default directory for all file-based images is the " "/var/lib/libvirt/images directory." msgstr "" #. Tag: para #, no-c-format msgid "" "qemu-kvm.[PID].log is the log file created by the " "qemu-kvm process for each fully virtualized guest. When " "using this log file, you must retrieve the given qemu-kvm" " process PID, by using the ps command to examine process " "arguments to isolate the qemu-kvm process on the virtual " "machine. Note that you must replace the [PID] symbol with the actual PID " "qemu-kvm process." msgstr "" #. Tag: para #, no-c-format msgid "" "If you encounter any errors with the Virtual Machine Manager, you can review" " the generated data in the virt-manager.log file that " "resides in the /.virt-manager directory. Note that every" " time you start the Virtual Machine Manager, it overwrites the existing log " "file contents. Make sure to backup the virt-manager.log " " file, before you restart the Virtual Machine manager after a system error." msgstr "" #. Tag: title #, no-c-format msgid "Troubleshooting with serial consoles" msgstr "" #. Tag: para #, no-c-format msgid "" "Linux kernels can output information to serial ports. This is useful for " "debugging kernel panics and hardware issues with video devices or headless " "servers. The subsections in this section cover setting up serial console " "output for machines running Fedora virtualization kernels and their " "virtualized guests." msgstr "" #. Tag: para #, no-c-format msgid "" "This section covers how to enable serial console output for fully " "virtualized guests." msgstr "" #. Tag: para #, no-c-format msgid "" "Fully virtualized guest serial console output can be viewed with the " "virsh console command." msgstr "" #. Tag: para #, no-c-format msgid "" "Be aware fully virtualized guest serial consoles have some limitations. " "Present limitations include:" msgstr "" #. Tag: para #, no-c-format msgid "output data may be dropped or scrambled." msgstr "" #. Tag: para #, no-c-format msgid "" "The serial port is called ttyS0 on Linux or " "COM1 on Windows." msgstr "" #. Tag: para #, no-c-format msgid "" "You must configure the virtualized operating system to output information to" " the virtual serial port." msgstr "" #. Tag: para #, no-c-format msgid "" "To output kernel information from a fully virtualized Linux guest into the " "domain modify the /boot/grub/grub.conf file by " "inserting the line console=tty0 console=ttys0,115200." msgstr "" #. Tag: screen #, no-c-format msgid "" "title Red Hat Enterprise Linux Server (2.6.32-36.x86-64)\n" "\troot (hd0,0)\n" "\tkernel /vmlinuz-2.6.32-36.x86-64 ro root=/dev/volgroup00/logvol00\n" "\tconsole=tty0 console=ttys0,115200\n" "\tinitrd /initrd-2.6.32-36.x86-64.img\n" msgstr "" #. Tag: para #, no-c-format msgid "Reboot the guest." msgstr "" #. Tag: para #, no-c-format msgid "On the host, access the serial console with the following command:" msgstr "" #. Tag: screen #, no-c-format msgid "# virsh console\n" msgstr "" #. Tag: para #, no-c-format msgid "" "You can also use virt-manager to display the virtual text" " console. In the guest console window, select Serial " "Console from the View menu." msgstr "" #. Tag: title #, no-c-format msgid "Virtualization log files" msgstr "" #. Tag: para #, no-c-format msgid "/var/log/libvirt/qemu/GuestName.log" msgstr "" #. Tag: title #, no-c-format msgid "Loop device errors" msgstr "" #. Tag: para #, no-c-format msgid "" "If file-based guest images are used you may have to increase the number of " "configured loop devices. The default configuration allows up to eight active" " loop devices. If more than eight file-based guests or loop devices are " "needed the number of loop devices configured can be adjusted in " "/etc/modprobe.conf. Edit " "/etc/modprobe.conf and add the following line to it:" msgstr "" #. Tag: screen #, no-c-format msgid " options loop max_loop=64\n" msgstr "" #. Tag: para #, no-c-format msgid "" "This example uses 64 but you can specify another number to set the maximum " "loop value. You may also have to implement loop device backed guests on your" " system. To use a loop device backed guests for a full virtualized system, " "use the phy: device or file: file " "commands." msgstr "" #. Tag: title #, no-c-format msgid "Enabling Intel VT and AMD-V virtualization hardware extensions in BIOS" msgstr "" #. Tag: para #, no-c-format msgid "" "This section describes how to identify hardware virtualization extensions " "and enable them in your BIOS if they are disabled." msgstr "" #. Tag: para #, no-c-format msgid "" "The Intel VT extensions can be disabled in the BIOS. Certain laptop vendors " "have disabled the Intel VT extensions by default in their CPUs." msgstr "" #. Tag: para #, no-c-format msgid "" "The virtualization extensions can not be disabled in the BIOS for AMD-V." msgstr "" #. Tag: para #, no-c-format msgid "" "The virtualization extensions are sometimes disabled in BIOS, usually by " "laptop manufacturers. Refer to " "for instructions on enabling disabled virtualization extensions." msgstr "" #. Tag: para #, no-c-format msgid "" "Verify the virtualization extensions are enabled in BIOS. The BIOS settings " "for Intel VT or AMD-V are " "usually in the Chipset or " "Processor menus. The menu names may vary from " "this guide, the virtualization extension settings may be found in " "Security Settings or other non standard menu names." msgstr "" #. Tag: title #, no-c-format msgid "Enabling virtualization extensions in BIOS" msgstr "" #. Tag: para #, no-c-format msgid "" "Reboot the computer and open the system's BIOS menu. This can usually be " "done by pressing the delete key, the " "F1 key or Alt and F4 keys" " depending on the system." msgstr "" #. Tag: para #, no-c-format msgid "" "Select Restore Defaults or Restore Optimized " "Defaults, and then select Save & Exit." msgstr "" #. Tag: para #, no-c-format msgid "Power off the machine and disconnect the power supply." msgstr "" #. Tag: title #, no-c-format msgid "Enabling the virtualization extensions in BIOS" msgstr "" #. Tag: title #, no-c-format msgid "Note: BIOS steps" msgstr "" #. Tag: para #, no-c-format msgid "" "Many of the steps below may vary depending on your motherboard, processor " "type, chipset and OEM. Refer to your system's accompanying documentation for" " the correct information on configuring your system." msgstr "" #. Tag: para #, no-c-format msgid "Power on the machine and open the BIOS (as per Step 1)." msgstr "" #. Tag: para #, no-c-format msgid "" "Open the Processor submenu The processor settings menu " "may be hidden in the Chipset, Advanced CPU " "Configuration or Northbridge." msgstr "" #. Tag: para #, no-c-format msgid "" "Enable Intel Virtualization Technology (also known as " "Intel VT) or AMD-V depending on the brand of the " "processor. The virtualization extensions may be labeled " "Virtualization Extensions, " "Vanderpool or various other names depending on the OEM " "and system BIOS." msgstr "" #. Tag: para #, no-c-format msgid "" "Enable Intel VTd or AMD IOMMU, if the options are available. Intel VTd and " "AMD IOMMU are used for PCI " "passthrough." msgstr "" #. Tag: para #, no-c-format msgid "Select Save & Exit." msgstr "" #. Tag: para #, no-c-format msgid "" "Run cat /proc/cpuinfo | grep vmx svm. If the command " "outputs, the virtualization extensions are now enabled. If there is no " "output your system may not have the virtualization extensions or the correct" " BIOS setting enabled." msgstr "" #. Tag: title #, no-c-format msgid "KVM networking performance" msgstr "" #. Tag: para #, no-c-format msgid "" "By default, KVM virtual machines are assigned a virtual Realtek 8139 " "(rtl8139) NIC (network interface controller)." msgstr "" #. Tag: para #, no-c-format msgid "" "The rtl8139 virtualized NIC works fine in most environments. However, this " "device can suffer from performance degradation problems on some networks, " "for example, a 10 Gigabit Ethernet network." msgstr "" #. Tag: para #, no-c-format msgid "To improve performance switch to the para-virtualized network driver." msgstr "" #. Tag: title #, no-c-format msgid "Note" msgstr "" #. Tag: para #, no-c-format msgid "" "Note that the virtualized Intel PRO/1000 (e1000) " "driver is also supported as an emulated driver choice. To use the " "e1000 driver, replace " "virtio in the procedure below with " "e1000. For the best performance it is " "recommended to use the virtio driver." msgstr "" #. Tag: title #, no-c-format msgid "Switching to the virtio driver" msgstr "" #. Tag: para #, no-c-format msgid "Shutdown the guest operating system." msgstr "" #. Tag: para #, no-c-format msgid "" "Edit the guest's configuration file with the virsh " "command (where GUEST is the guest's name):" msgstr "" #. Tag: screen #, no-c-format msgid "# virsh edit GUEST\n" msgstr "" #. Tag: para #, no-c-format msgid "" "The virsh edit command uses the " "$EDITOR shell variable to determine which editor to use." msgstr "" #. Tag: para #, no-c-format msgid "" "Find the network interface section of the configuration. This section " "resembles the snippet below:" msgstr "" #. Tag: screen #, no-c-format msgid "" "<interface type='network'>\n" " [output truncated]\n" " <model type='rtl8139' />\n" "</interface>\n" msgstr "" #. Tag: para #, no-c-format msgid "" "Change the type attribute of the model element from " "'rtl8139' to 'virtio'. This " "will change the driver from the rtl8139 driver to the e1000 driver." msgstr "" #. Tag: screen #, no-c-format msgid "" "<interface type='network'>\n" " [output truncated]\n" " <model type='virtio' />\n" "</interface>\n" msgstr "" #. Tag: para #, no-c-format msgid "Save the changes and exit the text editor" msgstr "" #. Tag: para #, no-c-format msgid "Restart the guest operating system." msgstr "" #. Tag: title #, no-c-format msgid "Creating new guests using other network drivers" msgstr "" #. Tag: para #, no-c-format msgid "" "Alternatively, new virtualized guests can be created with a different " "network driver. This may be required if you are having difficulty installing" " guests over a network connection. This method requires you to have at least" " one virtualized guest already created (possibly installed from CD or DVD) " "to use as a template." msgstr "" #. Tag: para #, no-c-format msgid "" "Create an XML template from an existing virtualized guest (in this example, " "named Guest1):" msgstr "" #. Tag: screen #, no-c-format msgid "" "# virsh dumpxml Guest1 > /tmp/guest-template.xml\n" msgstr "" #. Tag: para #, no-c-format msgid "" "Copy and edit the XML file and update the unique fields: virtual machine " "name, UUID, disk image, MAC address, and any other unique parameters. Note " "that you can delete the UUID and MAC address lines and virsh will generate a" " UUID and MAC address." msgstr "" #. Tag: screen #, no-c-format msgid "" "# cp /tmp/guest-template.xml /tmp/new-guest.xml\n" "# vi /tmp/new-guest.xml\n" msgstr "" #. Tag: para #, no-c-format msgid "Add the model line in the network interface section:" msgstr "" #. Tag: screen #, no-c-format msgid "" " <interface type='network'>\n" " [output truncated]\n" " <model type='virtio' />\n" "</interface>\n" msgstr "" #. Tag: para #, no-c-format msgid "Create the new virtual machine:" msgstr "" #. Tag: screen #, no-c-format msgid "" "# virsh define /tmp/new-guest.xml\n" "# virsh start new-guest\n" msgstr "" #. Tag: para #, no-c-format msgid "" "The network performance is better virtio driver. (BZ#517181)" msgstr ""