kernel page request failure

kernel page request failure

[David Brown]

I was running a guest os using kvm and I got this kernel page request
failure using kvm 33 and 2.6.22.1 host.

[12038.889793] Unable to handle kernel paging request at 0000000000100100 RIP:
[12038.889799]  [<ffffffff88bacd25>] :kvm:kvm_mmu_pte_write+0x95/0x2f0
[12038.889811] PGD 52d58067 PUD 533d1067 PMD 0
[12038.889814] Oops: 0000 [1] SMP
[12038.889816] CPU 0
[12038.889817] Modules linked in: usb_storage tun crc32 kvm_intel kvm
bridge ipv6 snd_pcm_oss snd_mixer_oss snd_emu10k1 snd_rawmidi
snd_ac97_codec ac97_bus snd_pcm snd_seq_device snd_timer
snd_page_alloc snd_util_mem snd_hwdep snd soundcore ext3 jbd libusual
usbkbd usbmouse usbhid hid ff_memless nvidiafb fb fb_ddc backlight
ohci1394 i2c_algo_bit ieee1394 cfbcopyarea vgastate generic bitrev
cfbimgblt cfbfillrect amd74xx firewire_ohci firewire_core nvidia(P)
ide_core serio_raw rtc tg3 crc_itu_t ehci_hcd ohci_hcd i2c_nforce2
8250_pnp 8250 serial_core pcspkr usbcore i2c_core psmouse shpchp
pci_hotplug sg sr_mod cdrom evdev tsdev ext4dev mbcache jbd2
ata_generic pata_amd sata_nv libata sd_mod scsi_mod dm_mod
[12038.889851] Pid: 4685, comm: qemu-system-x86 Tainted: P       2.6.22.1 #5
[12038.889853] RIP: 0010:[<ffffffff88bacd25>]  [<ffffffff88bacd25>]
:kvm:kvm_mmu_pte_write+0x95/0x2f0
[12038.889860] RSP: 0018:ffff81007202d928  EFLAGS: 00010206
[12038.889862] RAX: 00000000000004c8 RBX: ffff810072ff8000 RCX: ffff81007202db10
[12038.889864] RDX: 0000000000100100 RSI: 0000000000100100 RDI: 000000000000181d
[12038.889866] RBP: ffff81004b1d5000 R08: 0000000000000004 R09: 0000000000000004
[12038.889868] R10: 0000000000000001 R11: ffffffff88bbc380 R12: ffff810065ba38c0
[12038.889870] R13: 0000000000000004 R14: ffff810072ffaf20 R15: 000000000000181d
[12038.889872] FS:  0000000040800950(0063) GS:ffffffff8131f000(0000)
knlGS:0000000000000000
[12038.889874] CS:  0010 DS: 002b ES: 002b CR0: 000000008005003b
[12038.889876] CR2: 0000000000100100 CR3: 000000007cc6a000 CR4: 00000000000026e0
[12038.889878] Process qemu-system-x86 (pid: 4685, threadinfo
ffff81007202c000, task ffff8100532854a0)
[12038.889880] Stack:  0000000000000004 ffff81007202db10
ffffffff88bb9620 ffffffff88bad6e1
[12038.889884]  0000000400000002 ffff81007202db10 00000000000004c8
0000000000100100
[12038.889887]  00000000000004c8 ffff81007a68b000 ffff81007a68b060
ffff810072ffaf20
[12038.889890] Call Trace:
[12038.889897]  [<ffffffff88bad6e1>] :kvm:paging64_gva_to_gpa+0x51/0x70
[12038.889905]  [<ffffffff88ba7a66>]
:kvm:emulator_write_emulated_onepage+0x136/0x1a0
[12038.889912]  [<ffffffff88bafe43>] :kvm:x86_emulate_memop+0x1953/0x3e00
[12038.889917]  [<ffffffff88bac693>] :kvm:gpa_to_hpa+0x23/0x40
[12038.889922]  [<ffffffff88bacfe9>] :kvm:safe_gpa_to_hpa+0x9/0x30
[12038.889937]  [<ffffffff88ba9557>] :kvm:emulate_instruction+0x137/0x290
[12038.889945]  [<ffffffff8120a207>] mutex_lock+0x17/0x20
[12038.889948]  [<ffffffff8103962e>] recalc_sigpending+0xe/0x30
[12038.889954]  [<ffffffff88baa49a>] :kvm:kvm_vcpu_ioctl+0xdea/0xe90
[12038.889959]  [<ffffffff810272bc>] task_rq_lock+0x4c/0x90
[12038.889962]  [<ffffffff81026e32>] __activate_task+0x32/0x50
[12038.889965]  [<ffffffff810299ed>] try_to_wake_up+0x5d/0x4b0
[12038.889970]  [<ffffffff8104aade>] futex_wait+0x17e/0x3c0
[12038.889974]  [<ffffffff810ee803>] avc_has_perm_noaudit+0x93/0x380
[12038.889981]  [<ffffffff810ef6fa>] avc_has_perm+0x5a/0x80
[12038.889986]  [<ffffffff810f076b>] inode_has_perm+0x5b/0xa0
[12038.889993]  [<ffffffff8109db95>] do_ioctl+0x35/0xe0
[12038.889996]  [<ffffffff8109dcb4>] vfs_ioctl+0x74/0x2d0
[12038.890000]  [<ffffffff8109dfa5>] sys_ioctl+0x95/0xb0
[12038.890003]  [<ffffffff8100a0fe>] system_call+0x7e/0x83
[12038.890008]
[12038.890009]
[12038.890009] Code: 48 8b 32 4c 8d 62 f0 48 89 74 24 38 4d 3b 7c 24
20 75 df 41
[12038.890016] RIP  [<ffffffff88bacd25>] :kvm:kvm_mmu_pte_write+0x95/0x2f0
[12038.890022]  RSP <ffff81007202d928>
[12038.890023] CR2: 0000000000100100
[12038.890028] note: qemu-system-x86[4685] exited with preempt_count 1
[12038.890031] BUG: scheduling while atomic: qemu-system-x86/0x10000001/4685
[12038.890032]
[12038.890033] Call Trace:
[12038.890036]  [<ffffffff81209101>] thread_return+0x211/0x6c0
[12038.890041]  [<ffffffff8111c206>] vsnprintf+0x2d6/0x6b0
[12038.890046]  [<ffffffff8102a2fc>] __cond_resched+0x1c/0x50
[12038.890049]  [<ffffffff81209632>] cond_resched+0x32/0x40
[12038.890052]  [<ffffffff81047549>] down_read+0x9/0x20
[12038.890054]  [<ffffffff8104b024>] futex_wake+0x24/0xf0
[12038.890059]  [<ffffffff8104b812>] do_futex+0x722/0xc00
[12038.890063]  [<ffffffff8102fac9>] __call_console_drivers+0x69/0x80
[12038.890066]  [<ffffffff8102ff6e>] release_console_sem+0x20e/0x230
[12038.890070]  [<ffffffff8103050e>] printk+0x4e/0x60
[12038.890073]  [<ffffffff8104bd69>] sys_futex+0x79/0x130
[12038.890078]  [<ffffffff810316c6>] exit_mm+0x16/0xf0
[12038.890081]  [<ffffffff81032f5e>] do_exit+0x15e/0x970
[12038.890085]  [<ffffffff8120b4a8>] _spin_unlock_irqrestore+0x8/0x10
[12038.890089]  [<ffffffff8101daad>] do_page_fault+0x5ad/0x8e0
[12038.890093]  [<ffffffff810169b9>] smp_call_function_single+0xa9/0x100
[12038.890098]  [<ffffffff88ba70a0>] :kvm:ack_flush+0x0/0x10
[12038.890103]  [<ffffffff88bbc380>] :kvm_intel:vmx_get_segment_base+0x0/0x20
[12038.890108]  [<ffffffff88ba71a3>] :kvm:gfn_to_page+0x23/0x50
[12038.890113]  [<ffffffff88bac693>] :kvm:gpa_to_hpa+0x23/0x40
[12038.890118]  [<ffffffff88bacfe9>] :kvm:safe_gpa_to_hpa+0x9/0x30
[12038.890123]  [<ffffffff88bad585>] :kvm:paging64_walk_addr+0x245/0x350
[12038.890128]  [<ffffffff8120b71d>] error_exit+0x0/0x84
[12038.890133]  [<ffffffff88bbc380>] :kvm_intel:vmx_get_segment_base+0x0/0x20
[12038.890140]  [<ffffffff88bacd25>] :kvm:kvm_mmu_pte_write+0x95/0x2f0
[12038.890145]  [<ffffffff88bacced>] :kvm:kvm_mmu_pte_write+0x5d/0x2f0
[12038.890151]  [<ffffffff88bad6e1>] :kvm:paging64_gva_to_gpa+0x51/0x70
[12038.890158]  [<ffffffff88ba7a66>]
:kvm:emulator_write_emulated_onepage+0x136/0x1a0
[12038.890165]  [<ffffffff88bafe43>] :kvm:x86_emulate_memop+0x1953/0x3e00
[12038.890170]  [<ffffffff88bac693>] :kvm:gpa_to_hpa+0x23/0x40
[12038.890175]  [<ffffffff88bacfe9>] :kvm:safe_gpa_to_hpa+0x9/0x30
[12038.890190]  [<ffffffff88ba9557>] :kvm:emulate_instruction+0x137/0x290
[12038.890195]  [<ffffffff8120a207>] mutex_lock+0x17/0x20
[12038.890197]  [<ffffffff8103962e>] recalc_sigpending+0xe/0x30
[12038.890203]  [<ffffffff88baa49a>] :kvm:kvm_vcpu_ioctl+0xdea/0xe90
[12038.890206]  [<ffffffff810272bc>] task_rq_lock+0x4c/0x90
[12038.890209]  [<ffffffff81026e32>] __activate_task+0x32/0x50
[12038.890212]  [<ffffffff810299ed>] try_to_wake_up+0x5d/0x4b0
[12038.890216]  [<ffffffff8104aade>] futex_wait+0x17e/0x3c0
[12038.890218]  [<ffffffff810ee803>] avc_has_perm_noaudit+0x93/0x380
[12038.890226]  [<ffffffff810ef6fa>] avc_has_perm+0x5a/0x80
[12038.890232]  [<ffffffff810f076b>] inode_has_perm+0x5b/0xa0
[12038.890238]  [<ffffffff8109db95>] do_ioctl+0x35/0xe0
[12038.890241]  [<ffffffff8109dcb4>] vfs_ioctl+0x74/0x2d0
[12038.890245]  [<ffffffff8109dfa5>] sys_ioctl+0x95/0xb0
[12038.890248]  [<ffffffff8100a0fe>] system_call+0x7e/0x83
[12038.890252]

I am running a 64bit OS with a 32bit guest the guest happened to be
rebuilding my system (yeah I'm one of those crazies that run's a
compile from source distro) and it dumped this.

Some info on the system:
x86-64 one socket dual core pentium4 64bit Host
x86-64 2 processor 32bit Guest

cat /proc/cpuinfo
...
processor       : 1
vendor_id       : GenuineIntel
cpu family      : 6
model           : 15
model name      : Intel(R) Core(TM)2 CPU          6700  @ 2.66GHz
stepping        : 6
cpu MHz         : 2660.024
cache size      : 4096 KB
physical id     : 0
siblings        : 2
core id         : 1
cpu cores       : 2
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 syscall
nx lm constant_tsc pni monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr
lahf_lm
bogomips        : 5320.30
clflush size    : 64
cache_alignment : 64
address sizes   : 36 bits physical, 48 bits virtual
power management:

Any help would be appreciated.

Thanks,
- David Brown

-------------------------------------------------------------------------
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/

Re: kernel page request failure

[Avi Kivity]

David Brown wrote:
> I was running a guest os using kvm and I got this kernel page request
> failure using kvm 33 and 2.6.22.1 host.
>
>   

Is this 2.6.22.1's modules (i.e. --with-patched-kernel) or kvm-33's modules?

What guest are you running?

> [12038.889793] Unable to handle kernel paging request at 0000000000100100 RIP:
> [12038.889799]  [<ffffffff88bacd25>] :kvm:kvm_mmu_pte_write+0x95/0x2f0
> [12038.889811] PGD 52d58067 PUD 533d1067 PMD 0
> [12038.889814] Oops: 0000 [1] SMP
> [12038.889816] CPU 0
> [12038.889817] Modules linked in: usb_storage tun crc32 kvm_intel kvm
> bridge ipv6 snd_pcm_oss snd_mixer_oss snd_emu10k1 snd_rawmidi
> snd_ac97_codec ac97_bus snd_pcm snd_seq_device snd_timer
> snd_page_alloc snd_util_mem snd_hwdep snd soundcore ext3 jbd libusual
> usbkbd usbmouse usbhid hid ff_memless nvidiafb fb fb_ddc backlight
> ohci1394 i2c_algo_bit ieee1394 cfbcopyarea vgastate generic bitrev
> cfbimgblt cfbfillrect amd74xx firewire_ohci firewire_core nvidia(P)
> ide_core serio_raw rtc tg3 crc_itu_t ehci_hcd ohci_hcd i2c_nforce2
> 8250_pnp 8250 serial_core pcspkr usbcore i2c_core psmouse shpchp
> pci_hotplug sg sr_mod cdrom evdev tsdev ext4dev mbcache jbd2
> ata_generic pata_amd sata_nv libata sd_mod scsi_mod dm_mod
> [12038.889851] Pid: 4685, comm: qemu-system-x86 Tainted: P       2.6.22.1 #5
> [12038.889853] RIP: 0010:[<ffffffff88bacd25>]  [<ffffffff88bacd25>]
> :kvm:kvm_mmu_pte_write+0x95/0x2f0
> [12038.889860] RSP: 0018:ffff81007202d928  EFLAGS: 00010206
> [12038.889862] RAX: 00000000000004c8 RBX: ffff810072ff8000 RCX: ffff81007202db10
> [12038.889864] RDX: 0000000000100100 RSI: 0000000000100100 RDI: 000000000000181d
> [12038.889866] RBP: ffff81004b1d5000 R08: 0000000000000004 R09: 0000000000000004
> [12038.889868] R10: 0000000000000001 R11: ffffffff88bbc380 R12: ffff810065ba38c0
> [12038.889870] R13: 0000000000000004 R14: ffff810072ffaf20 R15: 000000000000181d
> [12038.889872] FS:  0000000040800950(0063) GS:ffffffff8131f000(0000)
> knlGS:0000000000000000
> [12038.889874] CS:  0010 DS: 002b ES: 002b CR0: 000000008005003b
> [12038.889876] CR2: 0000000000100100 CR3: 000000007cc6a000 CR4: 00000000000026e0
> [12038.889878] Process qemu-system-x86 (pid: 4685, threadinfo
> ffff81007202c000, task ffff8100532854a0)
> [12038.889880] Stack:  0000000000000004 ffff81007202db10
> ffffffff88bb9620 ffffffff88bad6e1
> [12038.889884]  0000000400000002 ffff81007202db10 00000000000004c8
> 0000000000100100
> [12038.889887]  00000000000004c8 ffff81007a68b000 ffff81007a68b060
> ffff810072ffaf20
> [12038.889890] Call Trace:
> [12038.889897]  [<ffffffff88bad6e1>] :kvm:paging64_gva_to_gpa+0x51/0x70
> [12038.889905]  [<ffffffff88ba7a66>]
> :kvm:emulator_write_emulated_onepage+0x136/0x1a0
> [12038.889912]  [<ffffffff88bafe43>] :kvm:x86_emulate_memop+0x1953/0x3e00
> [12038.889917]  [<ffffffff88bac693>] :kvm:gpa_to_hpa+0x23/0x40
> [12038.889922]  [<ffffffff88bacfe9>] :kvm:safe_gpa_to_hpa+0x9/0x30
> [12038.889937]  [<ffffffff88ba9557>] :kvm:emulate_instruction+0x137/0x290
> [12038.889945]  [<ffffffff8120a207>] mutex_lock+0x17/0x20
> [12038.889948]  [<ffffffff8103962e>] recalc_sigpending+0xe/0x30
> [12038.889954]  [<ffffffff88baa49a>] :kvm:kvm_vcpu_ioctl+0xdea/0xe90
> [12038.889959]  [<ffffffff810272bc>] task_rq_lock+0x4c/0x90
> [12038.889962]  [<ffffffff81026e32>] __activate_task+0x32/0x50
> [12038.889965]  [<ffffffff810299ed>] try_to_wake_up+0x5d/0x4b0
> [12038.889970]  [<ffffffff8104aade>] futex_wait+0x17e/0x3c0
> [12038.889974]  [<ffffffff810ee803>] avc_has_perm_noaudit+0x93/0x380
> [12038.889981]  [<ffffffff810ef6fa>] avc_has_perm+0x5a/0x80
> [12038.889986]  [<ffffffff810f076b>] inode_has_perm+0x5b/0xa0
> [12038.889993]  [<ffffffff8109db95>] do_ioctl+0x35/0xe0
> [12038.889996]  [<ffffffff8109dcb4>] vfs_ioctl+0x74/0x2d0
> [12038.890000]  [<ffffffff8109dfa5>] sys_ioctl+0x95/0xb0
> [12038.890003]  [<ffffffff8100a0fe>] system_call+0x7e/0x83
> [12038.890008]
> [12038.890009]
> [12038.890009] Code: 48 8b 32 4c 8d 62 f0 48 89 74 24 38 4d 3b 7c 24
> 20 75 df 41
> [12038.890016] RIP  [<ffffffff88bacd25>] :kvm:kvm_mmu_pte_write+0x95/0x2f0
> [12038.890022]  RSP <ffff81007202d928>
> [12038.890023] CR2: 0000000000100100
> [12038.890028] note: qemu-system-x86[4685] exited with preempt_count 1
> [12038.890031] BUG: scheduling while atomic: qemu-system-x86/0x10000001/4685
> [12038.890032]
> [12038.890033] Call Trace:
> [12038.890036]  [<ffffffff81209101>] thread_return+0x211/0x6c0
> [12038.890041]  [<ffffffff8111c206>] vsnprintf+0x2d6/0x6b0
> [12038.890046]  [<ffffffff8102a2fc>] __cond_resched+0x1c/0x50
> [12038.890049]  [<ffffffff81209632>] cond_resched+0x32/0x40
> [12038.890052]  [<ffffffff81047549>] down_read+0x9/0x20
> [12038.890054]  [<ffffffff8104b024>] futex_wake+0x24/0xf0
> [12038.890059]  [<ffffffff8104b812>] do_futex+0x722/0xc00
> [12038.890063]  [<ffffffff8102fac9>] __call_console_drivers+0x69/0x80
> [12038.890066]  [<ffffffff8102ff6e>] release_console_sem+0x20e/0x230
> [12038.890070]  [<ffffffff8103050e>] printk+0x4e/0x60
> [12038.890073]  [<ffffffff8104bd69>] sys_futex+0x79/0x130
> [12038.890078]  [<ffffffff810316c6>] exit_mm+0x16/0xf0
> [12038.890081]  [<ffffffff81032f5e>] do_exit+0x15e/0x970
> [12038.890085]  [<ffffffff8120b4a8>] _spin_unlock_irqrestore+0x8/0x10
> [12038.890089]  [<ffffffff8101daad>] do_page_fault+0x5ad/0x8e0
> [12038.890093]  [<ffffffff810169b9>] smp_call_function_single+0xa9/0x100
> [12038.890098]  [<ffffffff88ba70a0>] :kvm:ack_flush+0x0/0x10
> [12038.890103]  [<ffffffff88bbc380>] :kvm_intel:vmx_get_segment_base+0x0/0x20
> [12038.890108]  [<ffffffff88ba71a3>] :kvm:gfn_to_page+0x23/0x50
> [12038.890113]  [<ffffffff88bac693>] :kvm:gpa_to_hpa+0x23/0x40
> [12038.890118]  [<ffffffff88bacfe9>] :kvm:safe_gpa_to_hpa+0x9/0x30
> [12038.890123]  [<ffffffff88bad585>] :kvm:paging64_walk_addr+0x245/0x350
> [12038.890128]  [<ffffffff8120b71d>] error_exit+0x0/0x84
> [12038.890133]  [<ffffffff88bbc380>] :kvm_intel:vmx_get_segment_base+0x0/0x20
> [12038.890140]  [<ffffffff88bacd25>] :kvm:kvm_mmu_pte_write+0x95/0x2f0
> [12038.890145]  [<ffffffff88bacced>] :kvm:kvm_mmu_pte_write+0x5d/0x2f0
> [12038.890151]  [<ffffffff88bad6e1>] :kvm:paging64_gva_to_gpa+0x51/0x70
> [12038.890158]  [<ffffffff88ba7a66>]
> :kvm:emulator_write_emulated_onepage+0x136/0x1a0
> [12038.890165]  [<ffffffff88bafe43>] :kvm:x86_emulate_memop+0x1953/0x3e00
> [12038.890170]  [<ffffffff88bac693>] :kvm:gpa_to_hpa+0x23/0x40
> [12038.890175]  [<ffffffff88bacfe9>] :kvm:safe_gpa_to_hpa+0x9/0x30
> [12038.890190]  [<ffffffff88ba9557>] :kvm:emulate_instruction+0x137/0x290
> [12038.890195]  [<ffffffff8120a207>] mutex_lock+0x17/0x20
> [12038.890197]  [<ffffffff8103962e>] recalc_sigpending+0xe/0x30
> [12038.890203]  [<ffffffff88baa49a>] :kvm:kvm_vcpu_ioctl+0xdea/0xe90
> [12038.890206]  [<ffffffff810272bc>] task_rq_lock+0x4c/0x90
> [12038.890209]  [<ffffffff81026e32>] __activate_task+0x32/0x50
> [12038.890212]  [<ffffffff810299ed>] try_to_wake_up+0x5d/0x4b0
> [12038.890216]  [<ffffffff8104aade>] futex_wait+0x17e/0x3c0
> [12038.890218]  [<ffffffff810ee803>] avc_has_perm_noaudit+0x93/0x380
> [12038.890226]  [<ffffffff810ef6fa>] avc_has_perm+0x5a/0x80
> [12038.890232]  [<ffffffff810f076b>] inode_has_perm+0x5b/0xa0
> [12038.890238]  [<ffffffff8109db95>] do_ioctl+0x35/0xe0
> [12038.890241]  [<ffffffff8109dcb4>] vfs_ioctl+0x74/0x2d0
> [12038.890245]  [<ffffffff8109dfa5>] sys_ioctl+0x95/0xb0
> [12038.890248]  [<ffffffff8100a0fe>] system_call+0x7e/0x83
> [12038.890252]
>
> I am running a 64bit OS with a 32bit guest the guest happened to be
> rebuilding my system (yeah I'm one of those crazies that run's a
> compile from source distro) and it dumped this.
>
> Some info on the system:
> x86-64 one socket dual core pentium4 64bit Host
> x86-64 2 processor 32bit Guest
>
> cat /proc/cpuinfo
> ...
> processor       : 1
> vendor_id       : GenuineIntel
> cpu family      : 6
> model           : 15
> model name      : Intel(R) Core(TM)2 CPU          6700  @ 2.66GHz
> stepping        : 6
> cpu MHz         : 2660.024
> cache size      : 4096 KB
> physical id     : 0
> siblings        : 2
> core id         : 1
> cpu cores       : 2
> 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 syscall
> nx lm constant_tsc pni monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr
> lahf_lm
> bogomips        : 5320.30
> clflush size    : 64
> cache_alignment : 64
> address sizes   : 36 bits physical, 48 bits virtual
> power management:
>
> Any help would be appreciated.
>
> Thanks,
> - David Brown
>
> -------------------------------------------------------------------------
> 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/
> _______________________________________________
> kvm-devel mailing list
> kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
> https://lists.sourceforge.net/lists/listinfo/kvm-devel
>   


-- 
Do not meddle in the internals of kernels, for they are subtle and quick to panic.


-------------------------------------------------------------------------
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/

Re: kernel page request failure

[David Brown]

On 8/5/07, Avi Kivity <avi-atKUWr5tajBWk0Htik3J/w@public.gmane.org> wrote:
> David Brown wrote:
> > I was running a guest os using kvm and I got this kernel page request
> > failure using kvm 33 and 2.6.22.1 host.
> >
> >
>
> Is this 2.6.22.1's modules (i.e. --with-patched-kernel) or kvm-33's modules?

This is built with kvm-33 modules.

> What guest are you running?

Also the same crazy sourced based distro (Source Mage).

I don't remember what it was trying to rebuild I think it might have
been gcc. The guest has 1G ram and 1G swap. Also I found that the
guest (if there isn't any swap available) will die if all the memory
fills up. kvm had issues when that happened and it didn't release any
of the memory back to the host when the guest died and the process was
killed. I'm not sure if this had something to do with it or not gcc
does tend to generate some huge DFA's when it compiles and could have
filled up 2G with of memory and swap...  I wasn't paying attention
enough to notice if that was the case...

Thanks,
- David Brown

-------------------------------------------------------------------------
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/

Re: kernel page request failure

[Avi Kivity]

David Brown wrote:
> On 8/5/07, Avi Kivity <avi-atKUWr5tajBWk0Htik3J/w@public.gmane.org> wrote:
>   
>> David Brown wrote:
>>     
>>> I was running a guest os using kvm and I got this kernel page request
>>> failure using kvm 33 and 2.6.22.1 host.
>>>
>>>
>>>       
>> Is this 2.6.22.1's modules (i.e. --with-patched-kernel) or kvm-33's modules?
>>     
>
> This is built with kvm-33 modules.
>
>   
>> What guest are you running?
>>     
>
> Also the same crazy sourced based distro (Source Mage).
>
> I don't remember what it was trying to rebuild I think it might have
> been gcc. The guest has 1G ram and 1G swap. Also I found that the
> guest (if there isn't any swap available) will die if all the memory
> fills up. kvm had issues when that happened and it didn't release any
> of the memory back to the host when the guest died and the process was
> killed. I'm not sure if this had something to do with it or not gcc
> does tend to generate some huge DFA's when it compiles and could have
> filled up 2G with of memory and swap...  I wasn't paying attention
> enough to notice if that was the case...
>
>   

Is this the same issue or a different issue?  Did the oops happen when 
the host was loaded?

Please try to characterize one issue at a time, completely.



-------------------------------------------------------------------------
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/

Re: kernel page request failure

[David Brown]

> Is this the same issue or a different issue?

No but I was performing the same task in the guest OS so it might be related.

> Did the oops happen when the host was loaded?

No besides gnome running the host wasn't doing anything.

> Please try to characterize one issue at a time, completely.

Sorry, sometimes I get frustrated when things break and I tend to
start rambling...

Thanks,
- David Brown

-------------------------------------------------------------------------
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/

Re: kernel page request failure

[Avi Kivity]

David Brown wrote:
>> Is this the same issue or a different issue?
>>     
>
> No but I was performing the same task in the guest OS so it might be related.
>
>   
>> Did the oops happen when the host was loaded?
>>     
>
> No besides gnome running the host wasn't doing anything.
>
>   
>> Please try to characterize one issue at a time, completely.
>>     
>
> Sorry, sometimes I get frustrated when things break and I tend to
> start rambling...
>
>   

Well, I tend to get confused when I get fragmented reports and mix up 
different bugs.  Can you summarize what you are seeing with all relevant 
info so I can reproduce it?


-------------------------------------------------------------------------
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/

Re: kernel page request failure

[David Brown]

> Well, I tend to get confused when I get fragmented reports and mix up
> different bugs.  Can you summarize what you are seeing with all relevant
> info so I can reproduce it?

Well the problem is I can't reliably reproduce the bug. The things I
was doing that broke before aren't causing it to oopse again. I'll try
more things, I wouldn't worry about this one until I can pin down
what's causing it to fail.

The only time I've been able to reproduce it is when I am rebuilding
the entire guest (from source). However I attempt to rebuild the
individual components that failed and they don't reproduce the oopse.
So trying different things that are computationally intensive (like
compiles) for long periods of time seem to be the pattern. I'll have
to get back to you with more though.

Thanks, but this one might have to be put on the back burner.

- David Brown

-------------------------------------------------------------------------
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/