KVM crash on kvm-88 + kernel 2.6.30.6

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi

I had a KVM crash today with WinXP Pro SP3 32bit on kvm-88 + kernel 2.6.30.6
(modules from kernel).

------------[ cut here ]------------
WARNING: at arch/x86/kvm/x86.c:204 kvm_queue_exception_e+0x6b/0x80 [kvm]()
Hardware name: Latitude D520
Modules linked in: ipv6 i915 drm i2c_algo_bit rfcomm sco bridge stp llc bnep
l2cap btusb bluetooth fan usbhid hid fuse snd_seq_dummy tun snd_seq_oss
snd_seq_midi_event snd_seq snd_seq_device kvm_intel kvm snd_pcm_oss joydev
snd_hda_codec_idt snd_mixer_oss ohci1394 ieee1394 snd_hda_intel arc4
snd_hda_codec snd_hwdep ecb snd_pcm yenta_socket rsrc_nonstatic dell_laptop
snd_timer snd soundcore snd_page_alloc uhci_hcd psmouse video thermal output ac
iTCO_wdt iTCO_vendor_support wmi processor button iwl3945 ehci_hcd battery
usbcore dcdbas i2c_i801 i2c_core intel_agp sg iwlcore rfkill mac80211 led_class
agpgart serio_raw evdev cfg80211 slhc b44 ssb pcmcia pcmcia_core mii rtc_cmos
rtc_core rtc_lib ext3 jbd mbcache aes_i586 aes_generic xts gf128mul dm_crypt
dm_mod sd_mod sr_mod cdrom ata_piix ata_generic pata_acpi libata scsi_mod
Pid: 4238, comm: qemu-kvm Not tainted 2.6.30-ARCH #1
Call Trace:
 [<c013b26a>] ? warn_slowpath_common+0x7a/0xc0
 [<f8a3451b>] ? kvm_queue_exception_e+0x6b/0x80 [kvm]
 [<c013b2d0>] ? warn_slowpath_null+0x20/0x40
 [<f8a3451b>] ? kvm_queue_exception_e+0x6b/0x80 [kvm]
 [<f8a35927>] ? kvm_task_switch+0x277/0xc60 [kvm]
 [<f8a3d842>] ? mmu_sync_children+0x182/0x340 [kvm]
 [<f8a42015>] ? x86_emulate_insn+0x1895/0x3cb0 [kvm]
 [<f8a3ff96>] ? x86_decode_insn+0x686/0xd50 [kvm]
 [<f8a654be>] ? vmx_fpu_deactivate+0x4e/0x70 [kvm_intel]
 [<f8a66b61>] ? handle_task_switch+0x31/0xc0 [kvm_intel]
 [<f8a67161>] ? kvm_handle_exit+0xf1/0x200 [kvm_intel]
 [<c012a5a4>] ? kunmap_atomic+0x84/0xb0
 [<c012a55c>] ? kunmap_atomic+0x3c/0xb0
 [<f8a34dcd>] ? kvm_arch_vcpu_ioctl_run+0x34d/0xaf0 [kvm]
 [<f8a2ab5e>] ? kvm_vcpu_ioctl+0x45e/0x7f0 [kvm]
 [<c0166dba>] ? futex_wake+0xfa/0x110
 [<f8a2a700>] ? kvm_vcpu_ioctl+0x0/0x7f0 [kvm]
 [<c01dfcb2>] ? vfs_ioctl+0x22/0xa0
 [<c01dfdb9>] ? do_vfs_ioctl+0x89/0x5a0
 [<c0141bca>] ? irq_exit+0x3a/0x90
 [<c01688fa>] ? sys_futex+0xca/0x160
 [<c01e035e>] ? sys_ioctl+0x8e/0xb0
 [<c0103cb3>] ? sysenter_do_call+0x12/0x28
---[ end trace 82bf054de8a6387e ]---


Misc info:

--

The Blue Screen Of Death gave the following error:

*** STOP: 0x0000008E (0xC000001D, 0xF7A48D3E, 0xF7C5ECC0, 0x00000000)
*** processr.sys - Address F7A48D3E base at F7A47000, DateStamp 48025181

--

Startup command:
qemu-kvm -usbdevice tablet -net nic,macaddr=52:55:00:00:00:01,model=rtl8139 -net
tap,ifname=tap0 -vnc :1 -smp 2 -m 1024 -cdrom
/home/kenni/images/NETKVM-20081229.iso -hda /data/virtualization/winxp.img -boot
c -localtime -daemonize -monitor unix:/var/run/kvm/01_winxp.socket,server,nowait

--

$ cat /proc/cpuinfo
processor       : 0
vendor_id       : GenuineIntel
cpu family      : 6
model           : 15
model name      : Intel(R) Core(TM)2 CPU         T7200  @ 2.00GHz
stepping        : 6
cpu MHz         : 1995.143
cache size      : 4096 KB
physical id     : 0
siblings        : 2
core id         : 0
cpu cores       : 2
apicid          : 0
initial apicid  : 0
fdiv_bug        : no
hlt_bug         : no
f00f_bug        : no
coma_bug        : no
fpu             : yes
fpu_exception   : yes
cpuid level     : 10
wp              : yes
flags           : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov
pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe nx lm constant_tsc
arch_perfmon pebs bts pni dtes64 monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr pdcm
lahf_lm tpr_shadow
bogomips        : 3991.54
clflush size    : 64
power management:
<snip>

--

$ uname -a
Linux D520 2.6.30-ARCH #1 SMP PREEMPT Wed Sep 9 12:37:32 UTC 2009 i686 Intel(R)
Core(TM)2 CPU T7200 @ 2.00GHz GenuineIntel GNU/Linux

--

I don't suppose that this is enough information for you to identify the
issue? As I haven't had this crash before, I don't know if I'll see it
again...can I do something to collect better debugging information in the
future? Perhaps enable kernel memory dump in Windows or something else?

Best Regards
Kenni Lund
--
To unsubscribe from this list: send the line "unsubscribe kvm" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[Index of Archives]     [KVM ARM]     [KVM ia64]     [KVM ppc]     [Virtualization Tools]     [Spice Development]     [Libvirt]     [Libvirt Users]     [Linux USB Devel]     [Linux Audio Users]     [Yosemite Questions]     [Linux Kernel]     [Linux SCSI]     [XFree86]
  Powered by Linux