From: Pedro Alves <pedro-x9W5mcYdYeS4rn6H26CGUg@public.gmane.org>
To: KVM <kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org>
Subject: kvm-48: kernel BUG at mmu.c:307! - invalid opcode: 0000 [#1]
Date: Fri, 26 Oct 2007 15:09:06 +0100 [thread overview]
Message-ID: <20071026140906.GA7545@zmail.pt> (raw)
Hello.
I've been using kvm for a while, and it's been working great so far. Today
I got a kernel error pasted below.
Some system infos:
Host: Slackware
$ uname -a
Linux nicola 2.6.23.1-smp #2 SMP Mon Oct 15 17:49:01 CDT 2007 i686 Intel(R) Core(TM)2 Duo CPU T7300 @ 2.00GHz GenuineIntel GNU/Linux
kvm-48
launch instructions: sudo /opt/kvm-46/bin/qemu-system-x86_64 -hda /shared/vm/xp_pro_sp2.qcow2 -cdrom /dev/cdrom -usb -m 1250 -L /opt/kvm-46/share/qemu/ -redir tcp:1433::1433 -redir tcp:3389::3389 -redir tcp:8022::22
Cliene:
Windows xp pro xp2
I had booted the VM and was doing nothing - AVG antivirus was running.
Here is the paste:
------------[ cut here ]------------
kernel BUG at /home/pedro/can2/kvm-48/kernel/mmu.c:307!
invalid opcode: 0000 [#1]
SMP
Modules linked in: i915 drm sch_ingress cls_u32 sch_sfq sch_cbq fuse tun kvm_intel kvm snd_seq_dummy snd_seq_oss snd_seq_midi_event snd_seq snd_seq_device snd_pcm_oss snd_mixer_oss ipv6 cifs capability commoncap lp parport_pc parport pcmcia e1000 intel_agp agpgart rtc_cmos sdhci rtc_core yenta_socket rtc_lib rsrc_nonstatic mmc_core tifm_7xx1 serio_raw pcmcia_core tifm_core thermal video output ac button battery processor snd_hda_intel psmouse mac80211 snd_pcm cfg80211 snd_timer snd soundcore snd_page_alloc evdev pcspkr sg
CPU: 1
EIP: 0060:[<f9319c32>] Not tainted VLI
EFLAGS: 00010246 (2.6.23.1-smp #2)
EIP is at mmu_memory_cache_alloc+0x32/0x40 [kvm]
eax: 00000000 ebx: f95658ec ecx: d7a621b0 edx: 00000014
esi: f7daf838 edi: d7a62000 ebp: 00000000 esp: f6de5b28
ds: 007b es: 007b fs: 00d8 gs: 0000 ss: 0068
Process qemu-system-x86 (pid: 3688, ti=f6de4000 task=f27aaaa0 task.ti=f6de4000)
Stack: d7a62000 f95658ec d7a62000 f931a271 00000002 00000000 2d8ff043 f931a683
392fb000 00000000 000392fb 00000000 00000000 00000000 00000002 00000000
392fb000 00000000 f7daf838 d7a62000 392fb000 00000000 2d8ff000 00000000
Call Trace:
[<f931a271>] rmap_add+0xe1/0x100 [kvm]
[<f931a683>] paging32_set_pte_common+0x163/0x310 [kvm]
[<f931a895>] paging32_set_pte+0x65/0x80 [kvm]
[<f931afce>] kvm_mmu_pte_write+0x37e/0x3e0 [kvm]
[<f9315831>] kvm_write_guest_page+0x71/0xa0 [kvm]
[<c02ebc1c>] xfs_fs_geometry+0x21c/0x2d0
[<f931595b>] emulator_write_emulated_onepage+0x9b/0x120 [kvm]
[<f931d205>] x86_emulate_insn+0x525/0x3630 [kvm]
[<f9315c5f>] emulator_read_std+0x3f/0x90 [kvm]
[<c02ebc1c>] xfs_fs_geometry+0x21c/0x2d0
[<f931c9bb>] x86_decode_insn+0x7ab/0xad0 [kvm]
[<c02ebc1c>] xfs_fs_geometry+0x21c/0x2d0
[<f9315ebc>] emulate_instruction+0x16c/0x2a0 [kvm]
[<f911dc0a>] handle_exception+0x25a/0x2c0 [kvm_intel]
[<f911babd>] vmx_set_cr3+0xd/0x20 [kvm_intel]
[<c02ebc1c>] xfs_fs_geometry+0x21c/0x2d0
[<f911d889>] kvm_handle_exit+0x79/0xc0 [kvm_intel]
[<f9316743>] kvm_vcpu_ioctl_run+0x123/0x440 [kvm]
[<f9316dd0>] kvm_vcpu_ioctl+0x0/0xba0 [kvm]
[<f9317914>] kvm_vcpu_ioctl+0xb44/0xba0 [kvm]
[<c06d6e75>] sock_common_recvmsg+0x45/0x70
[<c06d5383>] sock_recvmsg+0x123/0x140
[<c06daa00>] skb_dequeue+0x40/0x60
[<c0746d2e>] unix_stream_recvmsg+0x24e/0x580
[<c0122985>] resched_task+0x55/0x60
[<c018334b>] core_sys_select+0x23b/0x2d0
[<c0122921>] update_curr+0x141/0x150
[<c0133a10>] __dequeue_signal+0x10/0x170
[<c013375b>] recalc_sigpending+0xb/0x20
[<c0135458>] dequeue_signal+0x48/0x140
[<c0141e56>] getnstimeofday+0x36/0xd0
[<c014005f>] enqueue_hrtimer+0x5f/0x80
[<c01405aa>] hrtimer_start+0xba/0x120
[<f9316dd0>] kvm_vcpu_ioctl+0x0/0xba0 [kvm]
[<c0181ebb>] do_ioctl+0x2b/0x90
[<c0181f7c>] vfs_ioctl+0x5c/0x290
[<c0182222>] sys_ioctl+0x72/0x90
[<c010428a>] syscall_call+0x7/0xb
=======================
Code: 8b 00 85 c0 74 25 48 8b 5c 81 04 89 01 89 d1 31 c0 c1 e9 02 89 df f3 ab f6 c2 02 74 02 66 ab f6 c2 01 74 01 aa 5a 89 d8 5b 5f c3 <0f> 0b eb fe 8d 76 00 8d bc 27 00 00 00 00 05 b0 01 00 00 ba 14
EIP: [<f9319c32>] mmu_memory_cache_alloc+0x32/0x40 [kvm] SS:ESP 0068:f6de5b28
--
Pedro Alves
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
next reply other threads:[~2007-10-26 14:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-26 14:09 Pedro Alves [this message]
[not found] ` <20071026140906.GA7545-8+64PGVKDrE@public.gmane.org>
2007-10-26 14:57 ` kvm-48: kernel BUG at mmu.c:307! - invalid opcode: 0000 [#1] Aurelien Jarno
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20071026140906.GA7545@zmail.pt \
--to=pedro-x9w5mcydyes4rn6h26cgug@public.gmane.org \
--cc=kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox