kernel bug in kvm_intel

[Andrew Theurer <habanero@linux.vnet.ibm.com>]

This is on latest master branch on kvm.git and qemu-kvm.git, running 12 
Windows Server2008 VMs, and using oprofile.  I ran again without 
oprofile and did not get the BUG.  I am wondering if anyone else is 
seeing this.

Thanks,

-Andrew

> Oct  9 11:55:13 virtvictory-eth0 kernel: BUG: unable to handle kernel paging request at ffffffff9fe9a2b4
> Oct  9 11:55:13 virtvictory-eth0 kernel: IP: [<ffffffffa02e1af1>] vmx_vcpu_run+0x26d/0x64f [kvm_intel]
> Oct  9 11:55:13 virtvictory-eth0 kernel: PGD 1003067 PUD 1007063 PMD 0 
> Oct  9 11:55:13 virtvictory-eth0 kernel: Oops: 0000 [#5] SMP 
> Oct  9 11:55:13 virtvictory-eth0 kernel: last sysfs file: /sys/devices/virtual/net/br4/bridge/topology_change_detected
> Oct  9 11:55:13 virtvictory-eth0 kernel: CPU 6 
> Oct  9 11:55:13 virtvictory-eth0 kernel: Modules linked in: oprofile tun hidp l2cap crc16 bluetooth rfkill lockd sunrpc bridge stp af_packet ipv6 binfmt_misc dm_multipath scsi_dh video output sbs sbshc pci_slot fan container battery ac parport_pc lp parport kvm_intel kvm joydev sr_mod cdrom sg cdc_ether usbnet mii usbhid hid serio_raw rtc_cmos rtc_core rtc_lib button thermal thermal_sys hwmon pata_acpi bnx2 i2c_i801 ide_pci_generic iTCO_wdt i2c_core ata_generic iTCO_vendor_support ioatdma dca pcspkr dm_snapshot dm_zero dm_mirror dm_region_hash dm_log dm_mod ide_gd_mod ide_core usb_storage ata_piix libata shpchp pci_hotplug qla2xxx scsi_transport_fc scsi_tgt sd_mod crc_t10dif scsi_mod ext3 jbd mbcache uhci_hcd ohci_hcd ehci_hcd usbcore [last unloaded: oprofile]
> Oct  9 11:55:13 virtvictory-eth0 kernel: Pid: 6495, comm: qemu-system-x86 Tainted: G      D    2.6.32-rc3-autokern1 #1 IBM System x -[7947AC1]-
> Oct  9 11:55:13 virtvictory-eth0 kernel: RIP: 0010:[<ffffffffa02e1af1>]  [<ffffffffa02e1af1>] vmx_vcpu_run+0x26d/0x64f [kvm_intel]
> Oct  9 11:55:13 virtvictory-eth0 kernel: RSP: 0018:ffff8806369ffc80  EFLAGS: 00010002     
> Oct  9 11:55:13 virtvictory-eth0 kernel: RAX: 000000000004001f RBX: 0000000000000200 RCX: 0000000000000001
> Oct  9 11:55:13 virtvictory-eth0 kernel: RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000080000000
> Oct  9 11:55:13 virtvictory-eth0 kernel: RBP: 0000000000000000 R08: fffffa80025180a8 R09: fffff800016ca4f0
> Oct  9 11:55:13 virtvictory-eth0 kernel: R10: 7797003630747070 R11: fffffa60039039b8 R12: 00000000a0000003
> Oct  9 11:55:13 virtvictory-eth0 kernel: R13: 0000000000000000 R14: 0000000000000000 R15: 0000000000000000
> Oct  9 11:55:13 virtvictory-eth0 kernel: FS:  0000000040ae6940(0000) GS:ffff88099fe80000(0000) knlGS:00000000ffe66000
> Oct  9 11:55:13 virtvictory-eth0 kernel: CS:  0010 DS: 0018 ES: 0018 CR0: 0000000080050033
> Oct  9 11:55:13 virtvictory-eth0 kernel: CR2: ffffffff9fe9a2b4 CR3: 00000006375ec000 CR4: 00000000000026f0
> Oct  9 11:55:13 virtvictory-eth0 kernel: DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
> Oct  9 11:55:13 virtvictory-eth0 kernel: DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
> Oct  9 11:55:13 virtvictory-eth0 kernel: Process qemu-system-x86 (pid: 6495, threadinfo ffff8806369fe000, task ffff880632056480)
> Oct  9 11:55:13 virtvictory-eth0 kernel: Stack:
> Oct  9 11:55:13 virtvictory-eth0 kernel:  ffff8806320916c0 ffff8806369ffd88 0000000000006c14 ffff8806369ffca8
> Oct  9 11:55:13 virtvictory-eth0 kernel: <0> ffff8806320916c0 ffff8806369ffce8 ffffffffa0293bfa ffff8806369ffee8
> Oct  9 11:55:13 virtvictory-eth0 kernel: <0> 0000000000000001 0000000000000300 ffff8806320916c0 000000000000002c
> Oct  9 11:55:13 virtvictory-eth0 kernel: Call Trace:
> Oct  9 11:55:13 virtvictory-eth0 kernel:  [<ffffffffa0293bfa>] ? emulate_instruction+0x28a/0x2bc [kvm]
> Oct  9 11:55:13 virtvictory-eth0 kernel:  [<ffffffffa02e129a>] ? handle_apic_access+0x20/0x4b [kvm_intel]
> Oct  9 11:55:13 virtvictory-eth0 kernel:  [<ffffffffa02e1fb4>] ? vmx_handle_exit+0xe1/0x48b [kvm_intel]
> Oct  9 11:55:13 virtvictory-eth0 kernel:  [<ffffffffa02de575>] ? save_msrs+0x39/0x50 [kvm_intel]
> Oct  9 11:55:13 virtvictory-eth0 kernel:  [<ffffffffa02aa328>] ? apic_update_ppr+0x23/0x51 [kvm]
> Oct  9 11:55:13 virtvictory-eth0 kernel:  [<ffffffff81199f6e>] ? __up_read+0x8f/0x97
> Oct  9 11:55:13 virtvictory-eth0 kernel:  [<ffffffffa02976a6>] ? kvm_arch_vcpu_ioctl_run+0x6b6/0xa92 [kvm]
> Oct  9 11:55:13 virtvictory-eth0 kernel:  [<ffffffffa028da38>] ? kvm_vcpu_ioctl+0xf6/0x5c0 [kvm]
> Oct  9 11:55:13 virtvictory-eth0 kernel:  [<ffffffff8102067f>] ? lapic_next_event+0x18/0x1c
> Oct  9 11:55:13 virtvictory-eth0 kernel:  [<ffffffff8106ec97>] ? clockevents_program_event+0x73/0x7c
> Oct  9 11:55:13 virtvictory-eth0 kernel:  [<ffffffff8106fdea>] ? tick_dev_program_event+0x2a/0x9c
> Oct  9 11:55:13 virtvictory-eth0 kernel:  [<ffffffff810fb324>] ? vfs_ioctl+0x2a/0x77
> Oct  9 11:55:13 virtvictory-eth0 kernel:  [<ffffffff810fb82e>] ? do_vfs_ioctl+0x445/0x496
> Oct  9 11:55:13 virtvictory-eth0 kernel:  [<ffffffff810736b9>] ? sys_futex+0x111/0x12f
> Oct  9 11:55:13 virtvictory-eth0 kernel:  [<ffffffff810fb8d6>] ? sys_ioctl+0x57/0x7a
> Oct  9 11:55:13 virtvictory-eth0 kernel:  [<ffffffff8100bc02>] ? system_call_fastpath+0x16/0x1b