Bug 715407

Summary: After upgrade from Fedora 14 to 15, virtual machines not running and kernel oops: sleeping function called from invalid context at arch/x86/mm/fault.c:1087
Product: [Fedora] Fedora Reporter: Paolo Campegiani <paolo.campegiani>
Component: kernelAssignee: Kernel Maintainer List <kernel-maint>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: high Docs Contact:
Priority: unspecified    
Version: 15CC: aquini, gansalmon, itamar, jonathan, kernel-maint, madhu.chinakonda
Target Milestone: ---   
Target Release: ---   
Hardware: i386   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-08-15 21:40:11 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Paolo Campegiani 2011-06-22 19:13:14 UTC 
Description of problem:

After an upgrade from Fedora 14 to Fedora 15, the system is unable to launch any virtual machine. The system supports SVM hardware virtualization

Version-Release number of selected component (if applicable):


How reproducible:

Everytime

Steps to Reproduce:

Start a virtual machine from virt-manager. Actually, something happens, i.e. the BIOS is working, but the virtual machine stucks with the "Press F12 to boot" message on screen. The first oop is at starting time, the last at stucking time
 
Actual results:

Jun 22 21:00:34 spacedock NetworkManager[1020]: <warn> /sys/devices/virtual/net/vnet0: couldn't determine device driver; ignoring...
Jun 22 21:00:34 spacedock kernel: [ 7291.689364] device vnet0 entered promiscuous mode
Jun 22 21:00:34 spacedock kernel: [ 7291.690054] virbr0: topology change detected, propagating
Jun 22 21:00:34 spacedock kernel: [ 7291.690059] virbr0: port 1(vnet0) entering forwarding state
Jun 22 21:00:34 spacedock kernel: [ 7291.690061] virbr0: port 1(vnet0) entering forwarding state
Jun 22 21:00:34 spacedock NetworkManager[1020]: <warn> /sys/devices/virtual/net/vnet1: couldn't determine device driver; ignoring...
Jun 22 21:00:34 spacedock kernel: [ 7291.697860] device vnet1 entered promiscuous mode
Jun 22 21:00:34 spacedock kernel: [ 7291.698143] virbr0: topology change detected, propagating
Jun 22 21:00:34 spacedock kernel: [ 7291.698148] virbr0: port 2(vnet1) entering forwarding state
Jun 22 21:00:34 spacedock kernel: [ 7291.698150] virbr0: port 2(vnet1) entering forwarding state
Jun 22 21:00:35 spacedock kernel: [ 7292.113035] BUG: sleeping function called from invalid context at arch/x86/mm/fault.c:1087
Jun 22 21:00:35 spacedock kernel: [ 7292.113040] in_atomic(): 0, irqs_disabled(): 1, pid: 4938, name: qemu-kvm
Jun 22 21:00:35 spacedock kernel: [ 7292.113044] Pid: 4938, comm: qemu-kvm Not tainted 2.6.38.8-32.fc15.i686.PAE #1
Jun 22 21:00:35 spacedock kernel: [ 7292.113046] Call Trace:
Jun 22 21:00:35 spacedock kernel: [ 7292.113054]  [<c07e17f3>] ? printk+0x2d/0x2f
Jun 22 21:00:35 spacedock kernel: [ 7292.113059]  [<c0435bee>] __might_sleep+0xdd/0xe4
Jun 22 21:00:35 spacedock kernel: [ 7292.113062]  [<c07ec0e2>] do_page_fault+0x179/0x30c
Jun 22 21:00:35 spacedock kernel: [ 7292.113066]  [<c044d599>] ? update_process_times+0x58/0x5d
Jun 22 21:00:35 spacedock kernel: [ 7292.113070]  [<c040b44b>] ? do_softirq+0x8c/0x92
Jun 22 21:00:35 spacedock kernel: [ 7292.113072]  [<c07ebf69>] ? do_page_fault+0x0/0x30c
Jun 22 21:00:35 spacedock kernel: [ 7292.113075]  [<c07e9cef>] error_code+0x67/0x6c
Jun 22 21:00:35 spacedock kernel: [ 7292.113078]  [<c07e9641>] ? restore_nocheck+0xb/0x10
Jun 22 21:00:35 spacedock kernel: [ 7292.113112]  [<f9081c58>] ? arch_local_irq_enable+0x7/0xb [kvm]
Jun 22 21:00:35 spacedock kernel: [ 7292.113136]  [<f908e30f>] kvm_arch_vcpu_ioctl_run+0xa33/0xd20 [kvm]
Jun 22 21:00:35 spacedock kernel: [ 7292.113138]  [<c07e86c9>] ? mutex_lock+0x22/0x3c
Jun 22 21:00:35 spacedock kernel: [ 7292.113159]  [<f907f5ec>] ? kvm_vm_ioctl_unregister_coalesced_mmio+0xc2/0xce [kvm]
Jun 22 21:00:35 spacedock kernel: [ 7292.113166]  [<f90e0b2b>] ? svm_vcpu_load+0x62/0x7b [kvm_amd]
Jun 22 21:00:35 spacedock kernel: [ 7292.113188]  [<f9089b5a>] ? kvm_arch_vcpu_load+0x83/0x11e [kvm]
Jun 22 21:00:35 spacedock kernel: [ 7292.113208]  [<f907d86b>] kvm_vcpu_ioctl+0x105/0x4b1 [kvm]
Jun 22 21:00:35 spacedock kernel: [ 7292.113212]  [<c040e9e1>] ? sched_clock+0x8/0xb
Jun 22 21:00:35 spacedock kernel: [ 7292.113214]  [<c045d8e8>] ? sched_clock_local+0x10/0x18b
Jun 22 21:00:35 spacedock kernel: [ 7292.113234]  [<f907d766>] ? kvm_vcpu_ioctl+0x0/0x4b1 [kvm]
Jun 22 21:00:35 spacedock kernel: [ 7292.113237]  [<c04f9f11>] do_vfs_ioctl+0x451/0x482
Jun 22 21:00:35 spacedock kernel: [ 7292.113240]  [<c045dbfb>] ? sched_clock_cpu+0x134/0x144
Jun 22 21:00:35 spacedock kernel: [ 7292.113243]  [<c043e5fe>] ? scheduler_tick+0x19d/0x1ee
Jun 22 21:00:35 spacedock kernel: [ 7292.113245]  [<c044d599>] ? update_process_times+0x58/0x5d
Jun 22 21:00:35 spacedock kernel: [ 7292.113248]  [<c04f9f8a>] sys_ioctl+0x48/0x6a
Jun 22 21:00:35 spacedock kernel: [ 7292.113250]  [<c040969f>] sysenter_do_call+0x12/0x28
Jun 22 21:00:36 spacedock avahi-daemon[1009]: Registering new address record for fe80::fc54:ff:fe56:5445 on vnet0.*.
Jun 22 21:00:36 spacedock avahi-daemon[1009]: Registering new address record for fe80::fc54:ff:feb3:f2c8 on vnet1.*.
Jun 22 21:00:37 spacedock ntpd[1027]: Listen normally on 9 vnet1 fe80::fc54:ff:feb3:f2c8 UDP 123
Jun 22 21:00:37 spacedock ntpd[1027]: Listen normally on 10 vnet0 fe80::fc54:ff:fe56:5445 UDP 123
Jun 22 21:00:37 spacedock ntpd[1027]: peers refreshed
Jun 22 21:00:39 spacedock kernel: [ 7296.061556] BUG: sleeping function called from invalid context at arch/x86/mm/fault.c:1087
Jun 22 21:00:39 spacedock kernel: [ 7296.061561] in_atomic(): 0, irqs_disabled(): 1, pid: 4938, name: qemu-kvm
Jun 22 21:00:39 spacedock kernel: [ 7296.061565] Pid: 4938, comm: qemu-kvm Not tainted 2.6.38.8-32.fc15.i686.PAE #1
Jun 22 21:00:39 spacedock kernel: [ 7296.061567] Call Trace:
Jun 22 21:00:39 spacedock kernel: [ 7296.061575]  [<c07e17f3>] ? printk+0x2d/0x2f
Jun 22 21:00:39 spacedock kernel: [ 7296.061580]  [<c0435bee>] __might_sleep+0xdd/0xe4
Jun 22 21:00:39 spacedock kernel: [ 7296.061583]  [<c07ec0e2>] do_page_fault+0x179/0x30c
Jun 22 21:00:39 spacedock kernel: [ 7296.061587]  [<c044d599>] ? update_process_times+0x58/0x5d
Jun 22 21:00:39 spacedock kernel: [ 7296.061591]  [<c040b44b>] ? do_softirq+0x8c/0x92
Jun 22 21:00:39 spacedock kernel: [ 7296.061593]  [<c07ebf69>] ? do_page_fault+0x0/0x30c
Jun 22 21:00:39 spacedock kernel: [ 7296.061597]  [<c07e9cef>] error_code+0x67/0x6c
Jun 22 21:00:39 spacedock kernel: [ 7296.061599]  [<c07e9641>] ? restore_nocheck+0xb/0x10
Jun 22 21:00:39 spacedock kernel: [ 7296.061603]  [<c05db06a>] ? __copy_from_user_ll+0xd1/0xd9
Jun 22 21:00:39 spacedock kernel: [ 7296.061606]  [<c05db0ae>] _copy_from_user+0x3c/0x50
Jun 22 21:00:39 spacedock kernel: [ 7296.061637]  [<f907ba6e>] copy_from_user+0xd/0xf [kvm]
Jun 22 21:00:39 spacedock kernel: [ 7296.061656]  [<f907ba99>] kvm_read_guest_page+0x29/0x37 [kvm]
Jun 22 21:00:39 spacedock kernel: [ 7296.061675]  [<f907bae6>] kvm_read_guest+0x3f/0x6e [kvm]
Jun 22 21:00:39 spacedock kernel: [ 7296.061697]  [<f90856f3>] kvm_read_guest_virt_helper+0x66/0x8e [kvm]
Jun 22 21:00:39 spacedock kernel: [ 7296.061719]  [<f9085769>] kvm_fetch_guest_virt+0x4e/0x56 [kvm]
Jun 22 21:00:39 spacedock kernel: [ 7296.061743]  [<f9097f57>] do_insn_fetch+0x8c/0xc8 [kvm]
Jun 22 21:00:39 spacedock kernel: [ 7296.061767]  [<f90990da>] x86_decode_insn+0xc0/0xc16 [kvm]
Jun 22 21:00:39 spacedock kernel: [ 7296.061789]  [<f908b407>] ? kvm_get_segment+0x12/0x15 [kvm]
Jun 22 21:00:39 spacedock kernel: [ 7296.061812]  [<f908b63f>] ? kvm_get_cs_db_l_bits+0x1e/0x31 [kvm]
Jun 22 21:00:39 spacedock kernel: [ 7296.061835]  [<f908b9d3>] x86_emulate_instruction+0x65/0x2d6 [kvm]
Jun 22 21:00:39 spacedock kernel: [ 7296.061843]  [<f90e0bed>] emulate_instruction+0x23/0x25 [kvm_amd]
Jun 22 21:00:39 spacedock kernel: [ 7296.061849]  [<f90e3b44>] io_interception+0x35/0x76 [kvm_amd]
Jun 22 21:00:39 spacedock kernel: [ 7296.061856]  [<f90e5600>] handle_exit+0x2b2/0x363 [kvm_amd]
Jun 22 21:00:39 spacedock kernel: [ 7296.061878]  [<f90962d5>] ? kvm_mmu_load+0x370/0x384 [kvm]
Jun 22 21:00:39 spacedock kernel: [ 7296.061900]  [<f9088ecc>] ? kvm_get_cr8+0x19/0x23 [kvm]
Jun 22 21:00:39 spacedock kernel: [ 7296.061922]  [<f908e37b>] kvm_arch_vcpu_ioctl_run+0xa9f/0xd20 [kvm]
Jun 22 21:00:39 spacedock kernel: [ 7296.061925]  [<c07e86c9>] ? mutex_lock+0x22/0x3c
Jun 22 21:00:39 spacedock kernel: [ 7296.061946]  [<f907f5ec>] ? kvm_vm_ioctl_unregister_coalesced_mmio+0xc2/0xce [kvm]
Jun 22 21:00:39 spacedock kernel: [ 7296.061952]  [<f90e0b2b>] ? svm_vcpu_load+0x62/0x7b [kvm_amd]
Jun 22 21:00:39 spacedock kernel: [ 7296.061974]  [<f9089b5a>] ? kvm_arch_vcpu_load+0x83/0x11e [kvm]
Jun 22 21:00:39 spacedock kernel: [ 7296.061994]  [<f907d86b>] kvm_vcpu_ioctl+0x105/0x4b1 [kvm]
Jun 22 21:00:39 spacedock kernel: [ 7296.061996]  [<c0408829>] ? __switch_to+0x99/0x10a
Jun 22 21:00:39 spacedock kernel: [ 7296.061999]  [<c04344de>] ? finish_task_switch+0x3e/0x98
Jun 22 21:00:39 spacedock kernel: [ 7296.062018]  [<f907d766>] ? kvm_vcpu_ioctl+0x0/0x4b1 [kvm]
Jun 22 21:00:39 spacedock kernel: [ 7296.062022]  [<c04f9f11>] do_vfs_ioctl+0x451/0x482
Jun 22 21:00:39 spacedock kernel: [ 7296.062025]  [<c044751b>] ? irq_exit+0x4c/0x70
Jun 22 21:00:39 spacedock kernel: [ 7296.062029]  [<c04f5402>] ? path_put+0x1a/0x1d
Jun 22 21:00:39 spacedock kernel: [ 7296.062031]  [<c04f9f8a>] sys_ioctl+0x48/0x6a
Jun 22 21:00:39 spacedock kernel: [ 7296.062033]  [<c040969f>] sysenter_do_call+0x12/0x28



Expected results:

I'd like to run my virtual machines.
Comment 1 Dave Jones 2011-08-15 21:40:11 UTC 

*** This bug has been marked as a duplicate of bug 717102 ***