# 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 09:43+0000\n" "Last-Translator: FULL NAME \n" "Language-Team: Catalan \n" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=UTF-8\n" "Content-Transfer-Encoding: 8bit\n" "Language: ca\n" "Plural-Forms: nplurals=2; plural=(n != 1)\n" #. Tag: title #: PV-Troubleshooting.xml:6 #, no-c-format msgid "Troubleshooting the Xen para-virtualized drivers" msgstr "" #. Tag: para #: PV-Troubleshooting.xml:7 #, no-c-format msgid "" "This chapter deals with issues you may encounter with Xen hosts and fully " "virtualized Red Hat Enterprise Linux guests using the para-virtualized " "drivers." msgstr "" #. Tag: title #: PV-Troubleshooting.xml:11 #, no-c-format msgid "Red Hat Enterprise Linux 5 Virtualization log file and directories" msgstr "" #. Tag: title #: PV-Troubleshooting.xml:13 #, no-c-format msgid "Red Hat Enterprise Linux 5 Virtualization related log file" msgstr "" #. Tag: para #: PV-Troubleshooting.xml:14 #, no-c-format msgid "" "In Red Hat Enterprise Linux 5, the log file written by the " "xend daemon and the qemu-dm process " "are all kept in the following directories:" msgstr "" #. Tag: filename #: PV-Troubleshooting.xml:20 #, no-c-format msgid "/var/log/xen/" msgstr "" #. Tag: para #: PV-Troubleshooting.xml:22 #, no-c-format msgid "" "directory holding all log file generated by the xend " "daemon and qemu-dm process." msgstr "" #. Tag: filename #: PV-Troubleshooting.xml:28 #, no-c-format msgid "xend.log" msgstr "" #. Tag: para #: PV-Troubleshooting.xml:32 #, no-c-format msgid "" "This logfile is used by xend to log any events generate by either normal " "system events or operator initiated events." msgstr "" #. Tag: para #: PV-Troubleshooting.xml:37 #, no-c-format msgid "" "virtual machine operations such as create, shutdown, destroy etc are all " "logged in this logfile." msgstr "" #. Tag: para #: PV-Troubleshooting.xml:42 #, no-c-format msgid "" "Usually this logfile will be the first place to look at in the event of a " "problem. In many cases you will be able to identify the root cause by " "scanning the logfile and review the entries logged just prior to the actual " "error message." msgstr "" #. Tag: filename #: PV-Troubleshooting.xml:50 #, no-c-format msgid "xend-debug.log" msgstr "" #. Tag: para #: PV-Troubleshooting.xml:54 #, no-c-format msgid "" "Records error events from xend and its subsystems (from the framebuffer and " "Python scripts)" msgstr "" #. Tag: filename #: PV-Troubleshooting.xml:62 #, no-c-format msgid "xen-hotplug.log" msgstr "" #. Tag: para #: PV-Troubleshooting.xml:66 #, no-c-format msgid "Logs events from hotplug events." msgstr "" #. Tag: para #: PV-Troubleshooting.xml:71 #, no-c-format msgid "" "Event notifications from devices not coming online or network bridges not " "online are logged in this file." msgstr "" #. Tag: filename #: PV-Troubleshooting.xml:79 #, no-c-format msgid "qemu-dm.PID.log" msgstr "" #. Tag: para #: PV-Troubleshooting.xml:83 #, no-c-format msgid "" "This file is created by the qemu-dm process which is " "started for each fully virtualized guest." msgstr "" #. Tag: para #: PV-Troubleshooting.xml:88 #, no-c-format msgid "" "The PID is replaced with the " "PID of the process of the related qemu-dm " "process" msgstr "" #. Tag: para #: PV-Troubleshooting.xml:93 #, no-c-format msgid "" "You can retrieve the PID for a given " "qemu-dm process using the ps command " "and in looking at the process arguments you can identify the virtual machine" " the qemu-dm process belongs to." msgstr "" #. Tag: para #: PV-Troubleshooting.xml:101 #, no-c-format msgid "" "If you are troubleshooting a problem with the virt-" "manager application you can also review the logfile generated " "by it. The logfile for virt-manager will be in a " "directory called .virt-manager in the user's " "home directory whom ran virt-" "manager. This directory will usually be ~/.virt-" "manager/virt-manager." msgstr "" #. Tag: para #: PV-Troubleshooting.xml:105 #, no-c-format msgid "" "The logfile is overwritten every time you start virt-" "manager. If you are troubleshooting a problem with " "virt-manager make sure you save the logfile " "before you restart virt-manager after an error " "has occurred." msgstr "" #. Tag: title #: PV-Troubleshooting.xml:110 #, no-c-format msgid "Red Hat Enterprise Linux 5 Virtualization related directories" msgstr "" #. Tag: para #: PV-Troubleshooting.xml:111 #, no-c-format msgid "" "There are a few other directories and files which may be of interest when " "troubleshooting a Red Hat Enterprise Linux 5 Virtualization environment:" msgstr "" #. Tag: filename #: PV-Troubleshooting.xml:117 #, no-c-format msgid "/var/lib/libvirt/images/" msgstr "" #. Tag: para #: PV-Troubleshooting.xml:119 #, no-c-format msgid "the standard directory for file-based guest images." msgstr "" #. Tag: filename #: PV-Troubleshooting.xml:125 #, no-c-format msgid "/var/lib/xen/xend-db/" msgstr "" #. Tag: para #: PV-Troubleshooting.xml:127 #, no-c-format msgid "" "directory that hold the xend database which is generated every time the " "daemon is restarted." msgstr "" #. Tag: filename #: PV-Troubleshooting.xml:133 #, no-c-format msgid "/etc/xen/" msgstr "" #. Tag: para #: PV-Troubleshooting.xml:135 #, no-c-format msgid "Stores a number of configuration files for the Xen hypervisor." msgstr "" #. Tag: para #: PV-Troubleshooting.xml:140 #, no-c-format msgid "" "/etc/xen/xend-config.sxp is the main configuration for " "the xend daemon. The xend-config.sxp file enables or " "disables migration and other features not configured by " "libvirt. Use the libvirt tools for all" " other features." msgstr "" #. Tag: filename #: PV-Troubleshooting.xml:148 #, no-c-format msgid "/var/xen/dump/" msgstr "" #. Tag: para #: PV-Troubleshooting.xml:150 #, no-c-format msgid "" "Holds dumps generate by virtual machines or when using the xm dump-" "core command." msgstr "" #. Tag: filename #: PV-Troubleshooting.xml:156 #, no-c-format msgid "/proc/xen/" msgstr "" #. Tag: para #: PV-Troubleshooting.xml:158 #, no-c-format msgid "" "Stores xen-kernel information in the following files:" msgstr "" #. Tag: filename #: PV-Troubleshooting.xml:164 #, no-c-format msgid "/proc/xen/capabilities" msgstr "" #. Tag: filename #: PV-Troubleshooting.xml:169 #, no-c-format msgid "/proc/xen/privcmd" msgstr "" #. Tag: filename #: PV-Troubleshooting.xml:174 #, no-c-format msgid "/proc/xen/balloon" msgstr "" #. Tag: filename #: PV-Troubleshooting.xml:179 #, no-c-format msgid "/proc/xen/xenbus" msgstr "" #. Tag: filename #: PV-Troubleshooting.xml:184 #, no-c-format msgid "/proc/xen/xsd_port" msgstr "" #. Tag: filename #: PV-Troubleshooting.xml:189 #, no-c-format msgid "/proc/xen/xsd_kva" msgstr "" #. Tag: title #: PV-Troubleshooting.xml:199 #, no-c-format msgid "" "Para-virtualized guest fail to load on a Red Hat Enterprise Linux 3 guest " "operating system" msgstr "" #. Tag: para #: PV-Troubleshooting.xml:200 #, no-c-format msgid "" "Red Hat Enterprise Linux 3 is uses processor architecture specific kernel " "RPMs and because of this the para-virtualized drivers may fail to load if " "the para-virtualized driver RPM does not match the installed kernel " "architecture." msgstr "" #. Tag: para #: PV-Troubleshooting.xml:203 #, no-c-format msgid "" "When the para-virtualized driver modules are inserted, a long list of unresolved modules will be displayed. A shortened excerpt of the error can be seen below. # insmod xen-platform-pci.o \n" "Warning: kernel-module version mismatch\n" "xen-platform-pci.o was compiled for kernel version 2.4.21-52.EL\n" "while this kernel is version 2.4.21-50.EL\n" "xen-platform-pci.o: unresolved symbol __ioremap_R9eac042a\n" "xen-platform-pci.o: unresolved symbol flush_signals_R50973be2\n" "xen-platform-pci.o: unresolved symbol pci_read_config_byte_R0e425a9e\n" "xen-platform-pci.o: unresolved symbol __get_free_pages_R9016dd82\n" "[...]\n" " The solution is to use the correct RPM package for your hardware architecture for the para-virtualized drivers." msgstr "" #. Tag: title #: PV-Troubleshooting.xml:211 #, no-c-format msgid "" "A warning message is displayed while installing the para-virtualized drivers" " on Red Hat Enterprise Linux 3" msgstr "" #. Tag: para #: PV-Troubleshooting.xml:212 #, no-c-format msgid "" "Installing the para-virtualized drivers on a Red Hat Enterprise Linux 3 " "kernel prior to 2.4.21-52 may result in a warning message being displayed " "stating the modules have been compiled with a newer version than the running" " kernel." msgstr "" #. Tag: para #: PV-Troubleshooting.xml:215 #, no-c-format msgid "This message, as seen below, can be safely ignored." msgstr "" #. Tag: screen #: PV-Troubleshooting.xml:219 #, no-c-format msgid "" "Warning: kernel-module version mismatch\n" "xen-platform-pci.o was compiled for kernel version 2.4.21-52.EL\n" "while this kernel is version 2.4.21-50.EL\n" "Warning: loading xen-platform-pci.o will taint the kernel: forced load\n" "See http://www.tux.org/lkml/#export-tainted for information about tainted modules\n" "Module xen-platform-pci loaded, with warnings" msgstr "" #. Tag: para #: PV-Troubleshooting.xml:220 #, no-c-format msgid "" "The important part of the message above is the last line which should state " "the module has been loaded with warnings." msgstr "" #. Tag: title #: PV-Troubleshooting.xml:257 #, no-c-format msgid "Manually loading the para-virtualized drivers" msgstr "" #. Tag: para #: PV-Troubleshooting.xml:258 #, no-c-format msgid "" "If for some reason the para-virtualized drivers failed to load automatically" " during the boot process you can attempt to load them manually." msgstr "" #. Tag: para #: PV-Troubleshooting.xml:261 #, no-c-format msgid "" "This will allow you to reconfigure network or storage entities or identify " "why they failed to load in the first place. The steps below should load the " "para-virtualized driver modules." msgstr "" #. Tag: para #: PV-Troubleshooting.xml:264 #, no-c-format msgid "First, locate the para-virtualized driver modules on your system." msgstr "" #. Tag: screen #: PV-Troubleshooting.xml:268 #, no-c-format msgid "" "# cd /lib/modules/`uname -r`/\n" "# find . -name 'xen-*.ko' -print" msgstr "" #. Tag: para #: PV-Troubleshooting.xml:269 #, no-c-format msgid "" "Take note of the location and load the modules manually. Substitute " "{LocationofPV-drivers} with the correct location you noted from the output " "of the commands above." msgstr "" #. Tag: screen #: PV-Troubleshooting.xml:273 #, no-c-format msgid "" "# insmod \\\n" "/lib/modules/'uname -r'/{LocationofPV-drivers}/xen-platform-pci.ko\n" "# insmod /lib/modules/'uname -r'/{LocationofPV-drivers}/xen-balloon.ko\n" "# insmod /lib/modules/'uname -r'/{LocationofPV-drivers}/xen-vnif.ko\n" "# insmod /lib/modules/'uname -r'/{LocationofPV-drivers}/xen-vbd.ko" msgstr "" #. Tag: title #: PV-Troubleshooting.xml:277 #, no-c-format msgid "Verifying the para-virtualized drivers have successfully loaded" msgstr "" #. Tag: para #: PV-Troubleshooting.xml:278 #, no-c-format msgid "" "One of the first tasks you will want to do is to verify that the drivers " "have actually been loaded into your system." msgstr "" #. Tag: para #: PV-Troubleshooting.xml:281 #, no-c-format msgid "" "After the para-virtualized drivers have been installed and the guest has been rebooted you can verify that the drivers have loaded. First you should confirm the drivers have logged their loading into /var/log/messages # grep -E \"vif|vbd|xen\" /var/log/messages\n" " xen_mem: Initialising balloon driver\n" " vif vif-0: 2 parsing device/vif/0/mac\n" " vbd vbd-768: 19 xlvbd_add at /local/domain/0/backend/vbd/21/76\n" " vbd vbd-768: 19 xlvbd_add at /local/domain/0/backend/vbd/21/76\n" " xen-vbd: registered block device major 202\n" " You can also use the lsmod command to list the loaded para-virtualized drivers. It should output a list containing the xen_vnif, xen_vbd, xen_platform_pci and xen_balloon modules." msgstr "" #. Tag: screen #: PV-Troubleshooting.xml:285 #, no-c-format msgid "" "# lsmod|grep xen\n" "xen_vbd 19168 1 \n" "xen_vnif 28416 0 \n" "xen_balloon 15256 1 xen_vnif\n" "xen_platform_pci 98520 3 xen_vbd,xen_vnif,xen_balloon,[permanent]" msgstr "" #. Tag: title #: PV-Troubleshooting.xml:290 #, no-c-format msgid "The system has limited throughput with para-virtualized drivers" msgstr "" #. Tag: para #: PV-Troubleshooting.xml:291 #, no-c-format msgid "" "If network throughput is still limited even after installing the para-" "virtualized drivers and you have confirmed they are loaded correctly (refer " "to ). To fix" " this problem, remove the 'type=ioemu' part of " "'vif=' line in your guest's configuration " "file." msgstr ""