Description of problem: #virsh start <client> Message from syslogd@APANATSCHI at Apr 22 13:09:45 ... kernel:[ 9828.038006] BUG: soft lockup - CPU#0 stuck for 23s! [qemu-system-x86:10598] Message from syslogd@APANATSCHI at Apr 22 13:09:45 ... kernel:[ 9828.038006] CPU: 0 PID: 10598 Comm: qemu-system-x86 Not tainted 3.13.10-200.fc20.i686+PAE #1 Message from syslogd@APANATSCHI at Apr 22 13:09:45 ... kernel:[ 9828.038006] Hardware name: FUJITSU SIEMENS AMILO Pi 2515/F43 , BIOS 1.05C 10/01/2007 Message from syslogd@APANATSCHI at Apr 22 13:09:45 ... kernel:[ 9828.038006] task: d6c4df80 ti: d0a3e000 task.ti: d0a3e000 Message from syslogd@APANATSCHI at Apr 22 13:09:45 ... kernel:[ 9828.038006] Stack: Message from syslogd@APANATSCHI at Apr 22 13:09:45 ... kernel:[ 9828.038006] Call Trace: Message from syslogd@APANATSCHI at Apr 22 13:09:45 ... kernel:[ 9828.038006] Code: 66 66 66 90 8b 10 83 e2 01 8b 48 04 64 03 0d c4 00 d8 c0 8d 1c 95 00 00 00 00 01 d9 8b 31 83 c6 01 89 31 0f ae f0 66 90 8b 40 04 <64> 03 05 c4 00 d8 c0 01 d8 8b 48 08 83 c1 01 89 48 08 5b 89 d0 Message from syslogd@APANATSCHI at Apr 22 13:09:45 ... kernel:BUG: soft lockup - CPU#0 stuck for 23s! [qem ... grep -A3 -i failed boot.log [FAILED] Failed to start Load Kernel Modules. See 'systemctl status systemd-modules-load.service' for details. [ OK ] Started Import network configuration from initramfs. [ OK ] Mounted RPC Pipe File System. # systemctl status systemd-modules-load.service systemd-modules-load.service - Load Kernel Modules Loaded: loaded (/usr/lib/systemd/system/systemd-modules-load.service; static) Active: failed (Result: exit-code) since Tue 2014-04-22 10:26:09 CEST; 2h 48min ago Docs: man:systemd-modules-load.service(8) man:modules-load.d(5) Main PID: 447 (code=exited, status=1/FAILURE) Apr 22 10:26:06 APANATSCHI systemd[1]: Starting Load Kernel Modules... Apr 22 10:26:09 APANATSCHI systemd[1]: systemd-modules-load.service: main process exited, code=exited, stat...ILURE Apr 22 10:26:09 APANATSCHI systemd[1]: Failed to start Load Kernel Modules. Apr 22 10:26:09 APANATSCHI systemd[1]: Unit systemd-modules-load.service entered failed state. Hint: Some lines were ellipsized, use -l to show in full. # Additional info: reporter: libreport-2.2.1 BUG: soft lockup - CPU#0 stuck for 22s! [qemu-system-x86:10598] Modules linked in: ipt_MASQUERADE xt_CHECKSUM ccm tun bnep bluetooth ip6t_rpfilter ip6t_REJECT xt_conntrack ebtable_nat ebtable_broute bridge stp llc ebtable_filter ebtables ip6table_nat nf_conntrack_ipv6 nf_defrag_ipv6 nf_nat_ipv6 ip6table_mangle ip6table_security ip6table_raw ip6table_filter ip6_tables iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_conntrack iptable_mangle iptable_security iptable_raw coretemp kvm_intel kvm iTCO_wdt iTCO_vendor_support joydev microcode arc4 i2c_i801 serio_raw iwl3945 iwlegacy mac80211 cfg80211 rfkill lpc_ich mfd_core snd_hda_codec_realtek snd_hda_codec_si3054 snd_hda_intel snd_hda_codec snd_hwdep snd_seq snd_seq_device snd_pcm snd_page_alloc snd_timer snd soundcore acpi_cpufreq nfsd auth_rpcgss nfs_acl lockd sunrpc ata_generic pata_acpi i915 r8169 i2c_algo_bit drm_kms_helper mii drm i2c_core video CPU: 0 PID: 10598 Comm: qemu-system-x86 Not tainted 3.13.10-200.fc20.i686+PAE #1 Hardware name: FUJITSU SIEMENS AMILO Pi 2515/F43 , BIOS 1.05C 10/01/2007 task: d6c4df80 ti: d0a3e000 task.ti: d0a3e000 EIP: 0060:[<f9c3e9b1>] EFLAGS: 00000202 CPU: 0 EIP is at vmcs_writel+0x11/0x30 [kvm_intel] EAX: 800000ef EBX: d0a10000 ECX: 00004016 EDX: 00004016 ESI: 800000ef EDI: d0a10000 EBP: d0a3fdfc ESP: d0a3fdfc DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: 0068 CR0: 80050033 CR2: 09322ed8 CR3: 23abf000 CR4: 000027f0 Stack: d0a3fe10 f9c4496b d0a10000 00000001 00000000 d0a3feb0 f9cf193e 00000007 00000000 00217bcb 8521bb6e 00000014 d6c4df80 d6c4df80 5a26b6cf 000008ea 8521bb6e 00000014 5a29f801 000008ea 0000000e 00a507d1 f4ab6024 7ffbfeff Call Trace: [<f9c4496b>] vmx_inject_irq+0x6b/0xd0 [kvm_intel] [<f9cf193e>] kvm_arch_vcpu_ioctl_run+0xaae/0x10c0 [kvm] [<c07c99cb>] ? sata_scr_write+0x3b/0x50 [<f9cddd04>] ? vcpu_load+0x44/0x70 [kvm] [<f9cde16e>] kvm_vcpu_ioctl+0x40e/0x4b0 [kvm] [<c04b7b34>] ? do_futex+0xf4/0xa90 [<f9cddd60>] ? vcpu_put+0x30/0x30 [kvm] [<c05784e2>] do_vfs_ioctl+0x2e2/0x4c0 [<c0642f2f>] ? file_has_perm+0x7f/0x90 [<c064391c>] ? selinux_file_ioctl+0x4c/0xf0 [<c0578720>] SyS_ioctl+0x60/0x80 [<c09d118d>] sysenter_do_call+0x12/0x28 Code: 81 58 01 00 00 0f ba a9 44 01 00 00 0a 5d c3 8d 74 26 00 8d bc 27 00 00 00 00 55 89 e5 66 66 66 66 90 89 c1 89 d0 89 ca 0f 79 d0 <0f> 96 c2 84 d2 75 02 5d c3 89 c2 89 c8 e8 28 aa 00 00 5d c3 8d
Created attachment 888445 [details] File: dmesg
*********** MASS BUG UPDATE ************** We apologize for the inconvenience. There is a large number of bugs to go through and several of them have gone stale. Due to this, we are doing a mass bug update across all of the Fedora 20 kernel bugs. Fedora 20 has now been rebased to 3.14.4-200.fc20. Please test this kernel update (or newer) and let us know if you issue has been resolved or if it is still present with the newer kernel. If you experience different issues, please open a new bug report for those.
I believe this is fixed by one of the newer 3.14.y updates.