Bugs item #1834719, was opened at 2007-11-19 19:58 Message generated for change (Comment added) made by jessorensen You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=893831&aid=1834719&group_id=180599 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: qemu Group: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: William Poetra Yoga Hadisoeseno (williampoetra) Assigned to: Nobody/Anonymous (nobody) Summary: bad_page in kvm_qemu when running Windows XP SP2 Initial Comment: Host OS: Linux 2.6.22.10 (vanilla) Host Bitness: 32 Guest OS: Windows XP SP2 Guest Bitness: 32 GCC: 4.1.2 CPU: T5600 RAM: 1 GB (allocated 256 MB for kvm_qemu) KVM Version: 0.52 Description: I ran kvm_qemu without modprobe-ing kvm-intel, and it just died. I didn't check the kernel logs (didn't suspect anything), and loaded the kvm-intel module. After that, I re-ran kvm, and connected to it through rdp. Initially everything was fine, I logged in and got to the desktop, but after a few seconds my mouse clicks weren't detected by the guest OS, and then a few seconds later my machine freezed, requiring a reboot. The logs below are taken from /var/log/kernel, after rebooting. The command is: kvm_qemu \ -hda c.img \ -no-reboot \ -nographic \ -localtime \ -m 256 \ -alt-grab \ -smb /home/william \ -redir tcp:3389::3389 & Nov 20 02:01:09 darkstar kernel: kvm: guest NX capability removed Nov 20 02:01:16 darkstar kernel: kvm: emulating exchange as write Nov 20 02:03:02 darkstar kernel: Bad page state in process 'kvm_qemu' Nov 20 02:03:03 darkstar kernel: page:c138dfc0 flags:0x40000014 mapping:00000000 mapcount:1 count:0 Nov 20 02:03:03 darkstar kernel: Trying to fix it up, but a reboot is needed Nov 20 02:03:03 darkstar kernel: Backtrace: Nov 20 02:03:03 darkstar kernel: [<c0151712>] bad_page+0x62/0xa0 Nov 20 02:03:03 darkstar kernel: [<c0151c71>] free_hot_cold_page+0x151/0x160 Nov 20 02:03:03 darkstar kernel: [<f8e06a4a>] rmap_remove+0x5a/0x180 [kvm] Nov 20 02:03:03 darkstar kernel: [<f8e06d7d>] kvm_mmu_zap_page+0x20d/0x250 [kvm] Nov 20 02:03:03 darkstar kernel: [<f8e082cd>] kvm_mmu_pte_write+0x20d/0x3e0 [kvm] Nov 20 02:03:03 darkstar kernel: [<f8e01bf1>] kvm_write_guest_page+0x71/0xa0 [kvm] Nov 20 02:03:03 darkstar kernel: [<f8e03910>] emulator_write_emulated_onepage+0xb0/0x140 [kvm] Nov 20 02:03:03 darkstar kernel: [<f8e0a741>] x86_emulate_insn+0x571/0x33c0 [kvm] Nov 20 02:03:03 darkstar kernel: [<f8e01cdd>] kvm_read_guest_page+0x5d/0x80 [kvm] Nov 20 02:03:03 darkstar kernel: [<f8e01d4d>] kvm_read_guest+0x4d/0x60 [kvm] Nov 20 02:03:03 darkstar kernel: [<f8e03b3f>] emulator_read_std+0x3f/0x90 [kvm] Nov 20 02:03:03 darkstar kernel: [<f8e097eb>] x86_decode_insn+0x9b/0xa80 [kvm] Nov 20 02:03:03 darkstar kernel: [<f8e03d8c>] emulate_instruction+0x16c/0x2a0 [kvm] Nov 20 02:03:03 darkstar kernel: [<f8e078e4>] kvm_mmu_page_fault+0x64/0xa0 [kvm] Nov 20 02:03:03 darkstar kernel: [<f8d2e579>] kvm_handle_exit+0x79/0xc0 [kvm_intel] Nov 20 02:03:04 darkstar kernel: [<f8d2c294>] vmcs_readl+0x14/0x20 [kvm_intel] Nov 20 02:03:04 darkstar kernel: [<f8d2e6af>] vmx_vcpu_run+0xef/0x110 [kvm_intel] Nov 20 02:03:04 darkstar kernel: [<f8e05cec>] kvm_arch_vcpu_ioctl_run+0xec/0x420 [kvm] Nov 20 02:03:04 darkstar kernel: [<f8e028f0>] kvm_vcpu_ioctl+0x0/0x410 [kvm] Nov 20 02:03:04 darkstar kernel: [<f8e02ca3>] kvm_vcpu_ioctl+0x3b3/0x410 [kvm] Nov 20 02:03:04 darkstar kernel: [<c023cfab>] dev_queue_xmit+0x9b/0x350 Nov 20 02:03:04 darkstar kernel: [<c025f221>] ip_output+0x1a1/0x340 Nov 20 02:03:04 darkstar kernel: [<c011d891>] __activate_task+0x21/0x40 Nov 20 02:03:04 darkstar kernel: [<c011f8e1>] try_to_wake_up+0x41/0x3c0 Nov 20 02:03:05 darkstar kernel: [<c017a0b2>] core_sys_select+0x242/0x2e0 Nov 20 02:03:05 darkstar kernel: [<c011d619>] __wake_up_common+0x39/0x70 Nov 20 02:03:05 darkstar kernel: [<c011dc78>] __wake_up+0x38/0x50 Nov 20 02:03:05 darkstar kernel: [<c014129b>] wake_futex+0x3b/0x50 Nov 20 02:03:05 darkstar kernel: [<c014261d>] futex_wake+0xad/0xd0 Nov 20 02:03:05 darkstar kernel: [<c012eae0>] __dequeue_signal+0x10/0x170 Nov 20 02:03:05 darkstar kernel: [<c012e82b>] recalc_sigpending+0xb/0x20 Nov 20 02:03:05 darkstar kernel: [<c0130507>] dequeue_signal+0x47/0x170 Nov 20 02:03:05 darkstar kernel: [<f8e02405>] kvm_vm_ioctl+0x35/0x290 [kvm] Nov 20 02:03:05 darkstar kernel: [<c01cca71>] rb_insert_color+0x91/0xc0 Nov 20 02:03:05 darkstar kernel: [<c013b0cb>] enqueue_hrtimer+0x6b/0x110 Nov 20 02:03:06 darkstar kernel: [<c013b92d>] hrtimer_start+0xbd/0x130 Nov 20 02:03:06 darkstar kernel: [<f8e028f0>] kvm_vcpu_ioctl+0x0/0x410 [kvm] Nov 20 02:03:06 darkstar kernel: [<c0178beb>] do_ioctl+0x2b/0xc0 Nov 20 02:03:06 darkstar kernel: [<c0137e72>] sys_timer_settime+0x272/0x290 Nov 20 02:03:06 darkstar kernel: [<c0178cdc>] vfs_ioctl+0x5c/0x290 Nov 20 02:03:06 darkstar kernel: [<c01cf540>] copy_to_user+0x30/0x60 Nov 20 02:03:06 darkstar kernel: [<c0178f82>] sys_ioctl+0x72/0x90 Nov 20 02:03:06 darkstar kernel: [<c01040fe>] sysenter_past_esp+0x5f/0x85 Nov 20 02:03:07 darkstar kernel: ======================= Nov 20 02:03:07 darkstar kernel: Bad page state in process 'kvm_qemu' Nov 20 02:03:07 darkstar kernel: page:c138dfc0 flags:0x40000004 mapping:00000000 mapcount:0 count:1 Nov 20 02:03:07 darkstar kernel: Trying to fix it up, but a reboot is needed Nov 20 02:03:07 darkstar kernel: Backtrace: Nov 20 02:03:08 darkstar kernel: [<c0151712>] bad_page+0x62/0xa0 ---------------------------------------------------------------------- >Comment By: Jes Sorensen (jessorensen) Date: 2010-06-11 10:26 Message: Hi, Looking through old bugs. You reported this against an old version of KVM - could you let us know if this is still a problem, and if not, lets close the bug. Thanks, Jes ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=893831&aid=1834719&group_id=180599 -- 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
