Description of problem: After installing new f13 x86_64 kernel, the virsh command would always hang. Examining the log finds many instances of junk like this: Sep 27 09:59:32 xen kernel: INFO: task qemu-kvm:1759 blocked for more than 120 seconds. Sep 27 09:59:32 xen kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. Sep 27 09:59:32 xen kernel: qemu-kvm D 0000000000000003 0 1759 1 0x00000000 Sep 27 09:59:32 xen kernel: ffff88022bacdc48 0000000000000082 ffff88012b8e1770 ffff88022aba8000 Sep 27 09:59:32 xen kernel: ffff88022bacdfd8 ffff88022aba8000 00000000000153c0 ffff88022bacdfd8 Sep 27 09:59:32 xen kernel: 00000000000153c0 00000000000153c0 00000000000153c0 00000000000153c0 Sep 27 09:59:32 xen kernel: Call Trace: Sep 27 09:59:32 xen kernel: [<ffffffff8144bd04>] __mutex_lock_common+0x152/0x1b9 Sep 27 09:59:32 xen kernel: [<ffffffff8144bd84>] __mutex_lock_slowpath+0x19/0x1b Sep 27 09:59:32 xen kernel: [<ffffffff8144bea4>] mutex_lock+0x36/0x50 Sep 27 09:59:32 xen kernel: [<ffffffffa01dd83a>] ? might_fault+0x21/0x23 [kvm] Sep 27 09:59:32 xen kernel: [<ffffffffa01d30b7>] vcpu_load+0x18/0x3a [kvm] Sep 27 09:59:32 xen kernel: [<ffffffffa01deebd>] kvm_arch_vcpu_ioctl+0x877/0x96d [kvm] Sep 27 09:59:32 xen kernel: [<ffffffffa01d09c5>] kvm_vcpu_ioctl+0x508/0x56e [kvm] Sep 27 09:59:32 xen kernel: [<ffffffff8105ca3e>] ? send_signal+0x76/0x81 Sep 27 09:59:32 xen kernel: [<ffffffff8111aabf>] vfs_ioctl+0x32/0xa6 Sep 27 09:59:32 xen kernel: [<ffffffff8111b032>] do_vfs_ioctl+0x483/0x4c9 Sep 27 09:59:32 xen kernel: [<ffffffff81076771>] ? sys_futex+0x12c/0x147 Sep 27 09:59:32 xen kernel: [<ffffffff8111b0ce>] sys_ioctl+0x56/0x79 Sep 27 09:59:32 xen kernel: [<ffffffff81009c72>] system_call_fastpath+0x16/0x1b Reverting back to the previous kernel-2.6.33.6-147.fc13.x86_64 makes the system work fine. Version-Release number of selected component (if applicable): kernel-2.6.34.7-56.fc13.x86_64 How reproducible: Seems 100% Steps to Reproduce: 1.install new 2.6.34 kernel, watch libvirt puke 2. 3. Actual results: libvirt busted Expected results: working virtual host Additional info: The same 2.6.34 kernel installed on a second Intel xeon host system works fine.
This message is a reminder that Fedora 13 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 13. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '13'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 13's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 13 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora please change the 'version' of this bug to the applicable version. If you are unable to change the version, please add a comment here and someone will do it for you. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
Fedora 13 changed to end-of-life (EOL) status on 2011-06-25. Fedora 13 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. Thank you for reporting this bug and we are sorry it could not be fixed.