public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Hans de Bruin <bruinjm@xs4all.nl>
To: kvm@vger.kernel.org
Subject: Re: just a dump
Date: Wed, 13 May 2009 00:20:26 +0200	[thread overview]
Message-ID: <4A09F62A.8010203@xs4all.nl> (raw)
In-Reply-To: <4A09E620.3040300@xs4all.nl>

Hans de Bruin wrote:
> Staring to vms simultaneously end in crash
> 
> linux 30-rc5
> kvm-qemu kvm-85-378-g143eb2b
> proc AMD dualcore
> 
> vm's like:
> 
> #!/bin/sh
> n=10
> cdrom=/iso/server2008x64.iso
> drive=file=/kvm/disks/vm$n
> mem=1024
> cpu=qemu64
> vga=std
> mac=52:54:00:12:34:$n
> bridge=br1
> 
> qemu-system-x86_64 -cdrom $cdrom -drive $drive -m $mem -cpu $cpu -vga 
> $vga -net nic,macaddr=$mac -net tap,script=/etc/qemu/$bridge
> 
> 
another dmesg:

device tap0 entered promiscuous mode
br1: topology change detected, propagating
br1: port 1(tap0) entering forwarding state
device tap1 entered promiscuous mode
br1: topology change detected, propagating
br1: port 2(tap1) entering forwarding state
tap0: no IPv6 routers present
tap1: no IPv6 routers present
kvm: 2915: cpu0 unimplemented perfctr wrmsr: 0xc0010000 data 0x0
kvm: 2915: cpu0 unimplemented perfctr wrmsr: 0xc0010001 data 0x0
kvm: 2915: cpu0 unimplemented perfctr wrmsr: 0xc0010002 data 0x0
kvm: 2915: cpu0 unimplemented perfctr wrmsr: 0xc0010003 data 0x0
kvm: 2914: cpu0 unimplemented perfctr wrmsr: 0xc0010000 data 0x0
kvm: 2914: cpu0 unimplemented perfctr wrmsr: 0xc0010001 data 0x0
kvm: 2914: cpu0 unimplemented perfctr wrmsr: 0xc0010002 data 0x0
kvm: 2914: cpu0 unimplemented perfctr wrmsr: 0xc0010003 data 0x0
rmap_remove: ffff880100de5500 8 0->BUG
------------[ cut here ]------------
kernel BUG at arch/x86/kvm/mmu.c:576!
invalid opcode: 0000 [#1] SMP
last sysfs file: /sys/devices/pci0000:00/0000:00:10.0/0000:01:09.0/resource
CPU 1
Modules linked in:
Pid: 2925, comm: qemu-system-x86 Not tainted 2.6.30-rc5 #3 System 
Product Name
RIP: 0010:[<ffffffff80217071>]  [<ffffffff80217071>] rmap_remove+0x151/0x200
RSP: 0018:ffff8801a0d379f8  EFLAGS: 00010292
RAX: 000000000000002a RBX: 0000000000000008 RCX: ffffffff809a3b40
RDX: ffff88002804d000 RSI: 0000000000000046 RDI: ffffffff809a3a34
RBP: ffff8801a0d37a28 R08: 0000000000008777 R09: 00000000ffffffff
R10: 0000000000000000 R11: 0000000000000000 R12: 0000000000000000
R13: ffff880100de5500 R14: ffff880101e23580 R15: ffff8801a0e1c000
FS:  000000004270d950(0063) GS:ffff88002804d000(0000) knlGS:000007fffffaa000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00000000014a8c18 CR3: 00000001a0c62000 CR4: 00000000000006e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
Process qemu-system-x86 (pid: 2925, threadinfo ffff8801a0d36000, task 
ffff8801af3605a0)
Stack:
  ffff8801a0d37a28 0000000000000000 0000000000000000 0000000000000000
  0000000000000500 ffff880101e23580 ffff8801a0d37ac8 ffffffff8021ad8d
  0000000000000000 ffff880100000000 000000000003020d 000000000016e772
Call Trace:
  [<ffffffff8021ad8d>] paging64_sync_page+0x9d/0x1a0
  [<ffffffff80218825>] ? rmap_write_protect+0xd5/0x150
  [<ffffffff8021890b>] kvm_sync_page+0x6b/0x90
  [<ffffffff8021a1ad>] mmu_sync_children+0xcd/0x120
  [<ffffffff8021cfd2>] ? x86_emulate_insn+0x292/0x4d30
  [<ffffffff8021c242>] ? x86_decode_insn+0x412/0xf10
  [<ffffffff8021a2c2>] mmu_sync_roots+0xc2/0xd0
  [<ffffffff8021a658>] kvm_mmu_load+0x138/0x200
  [<ffffffff8022822a>] ? handle_exit+0x14a/0x2c0
  [<ffffffff80213873>] kvm_arch_vcpu_ioctl_run+0x863/0xaa0
  [<ffffffff8020b5d5>] ? kvm_vm_ioctl+0x165/0x910
  [<ffffffff8027cda9>] ? do_futex+0x679/0x9a0
  [<ffffffff8020cad3>] kvm_vcpu_ioctl+0x5d3/0x790
  [<ffffffff8022b88e>] ? common_interrupt+0xe/0x13
  [<ffffffff8024eaeb>] ? __dequeue_entity+0x2b/0x50
  [<ffffffff802d8f31>] vfs_ioctl+0x31/0x90
  [<ffffffff802d9281>] do_vfs_ioctl+0x2f1/0x4e0
  [<ffffffff802d94f2>] sys_ioctl+0x82/0xa0
  [<ffffffff8022af6b>] system_call_fastpath+0x16/0x1b
Code: 04 75 e7 48 8b 47 20 49 89 fb 48 85 c0 0f 84 b7 00 00 00 48 89 c7 
eb d0 49 8b 55 00 4c 89 ee 48 c7 c7 b8 2e 7f 80 e8 1f 29
04 00 <0f> 0b eb fe 48 8b 4f 18 48 85 c9 0f 94 c2 83 fe 02 0f 9e c0 84
RIP  [<ffffffff80217071>] rmap_remove+0x151/0x200
  RSP <ffff8801a0d379f8>
---[ end trace c11385df745a1fea ]---
BUG: unable to handle kernel NULL pointer dereference at 0000000000000058
IP: [<ffffffff80216b4c>] mmu_page_remove_parent_pte+0xc/0x100
PGD 1a0ca8067 PUD 1a0ca9067 PMD 0
Oops: 0000 [#2] SMP
last sysfs file: /sys/devices/pci0000:00/0000:00:10.0/0000:01:09.0/resource
CPU 0
Modules linked in:
Pid: 2926, comm: qemu-system-x86 Tainted: G      D    2.6.30-rc5 #3 
System Product Name
RIP: 0010:[<ffffffff80216b4c>]  [<ffffffff80216b4c>] 
mmu_page_remove_parent_pte+0xc/0x100
RSP: 0018:ffff8801a0da57a8  EFLAGS: 00010292
RAX: 0000000000000000 RBX: 0000000000000000 RCX: 000000000000002b
RDX: ffffe20000000000 RSI: ffff8800ccac0220 RDI: 0000000000000000
RBP: ffff8801a0da57b8 R08: 000000000000006a R09: ffff8800ccd85e70
R10: 0000000000000000 R11: 0000000000000000 R12: ffff8800ccac0220
R13: ffff8800ccd85dc0 R14: 0000000000000044 R15: ffff8801a0db0000
FS:  0000000040fbc950(0063) GS:ffff880028034000(0000) knlGS:000007fffffd5000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000000000000058 CR3: 00000001a0c63000 CR4: 00000000000006e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
Process qemu-system-x86 (pid: 2926, threadinfo ffff8801a0da4000, task 
ffff8801ae971c20)
Stack:
  ffff8800ccd85590 000000000000007a ffff8801a0da5948 ffffffff80217323
  ffff8801a0da5808 0000000000000056 ffff8800ccd85dc0 ffffe20000000000
  ffff8801030f8160 0000000000000003 ffff880103f87000 ffffffff000001b8
Call Trace:
  [<ffffffff80217323>] kvm_mmu_zap_page+0x153/0x3a0
  [<ffffffff8020a207>] ? mark_page_dirty+0x27/0x60
  [<ffffffff80248f0b>] ? get_user_pages_fast+0x1db/0x2e0
  [<ffffffff8020a59c>] ? gfn_to_memslot+0x1c/0x30
  [<ffffffff8020a59c>] ? gfn_to_memslot+0x1c/0x30
  [<ffffffff8020a267>] ? gfn_to_hva+0x27/0x60
  [<ffffffff8020a4a5>] ? kvm_read_guest_page+0x65/0x70
  [<ffffffff8021993c>] kvm_mmu_pte_write+0x72c/0x910
  [<ffffffff8021a04f>] ? paging64_walk_addr+0x28f/0x320
  [<ffffffff8020a31c>] ? kvm_write_guest_page+0x7c/0x80
  [<ffffffff8020fb0d>] emulator_write_phys+0x4d/0x70
  [<ffffffff80211785>] emulator_write_emulated_onepage+0x95/0x120
  [<ffffffff80211880>] emulator_write_emulated+0x70/0x90
  [<ffffffff8021d11e>] x86_emulate_insn+0x3de/0x4d30
  [<ffffffff8021bcef>] ? decode_register_operand+0x8f/0x100
  [<ffffffff8021c50c>] ? x86_decode_insn+0x6dc/0xf10
  [<ffffffff8020e710>] ? kvm_find_cpuid_entry+0xf0/0x110
  [<ffffffff8020f91f>] emulate_instruction+0x15f/0x2f0
  [<ffffffff802191da>] kvm_mmu_page_fault+0x5a/0x90
  [<ffffffff80226e7f>] pf_interception+0x7f/0x190
  [<ffffffff80222a3d>] ? apic_update_ppr+0x2d/0x70
  [<ffffffff8022822a>] handle_exit+0x14a/0x2c0
  [<ffffffff8021363f>] kvm_arch_vcpu_ioctl_run+0x62f/0xaa0
  [<ffffffff8020b5d5>] ? kvm_vm_ioctl+0x165/0x910
  [<ffffffff8026e680>] ? autoremove_wake_function+0x0/0x40
  [<ffffffff8020cad3>] kvm_vcpu_ioctl+0x5d3/0x790
  [<ffffffff803ea171>] ? security_file_permission+0x11/0x20
  [<ffffffff802cba0f>] ? do_readv_writev+0x14f/0x1d0
  [<ffffffff802d8f31>] vfs_ioctl+0x31/0x90
  [<ffffffff802d9281>] do_vfs_ioctl+0x2f1/0x4e0
  [<ffffffff802d94f2>] sys_ioctl+0x82/0xa0
  [<ffffffff802cc4c1>] ? sys_writev+0x81/0x90
  [<ffffffff8022af6b>] system_call_fastpath+0x16/0x1b
Code: e6 48 89 df e8 66 fe ff ff 48 8b 1c 24 4c 8b 64 24 08 c9 c3 66 66 
2e 0f 1f 84 00 00 00 00 00 55 48 89 e5 53 48 89 fb 48 83 ec 08 <44> 8b 
4f 58 45 85 c9 0f 84 d7 00 00 00 48 8b 47 68 48 85 c0 0f
RIP  [<ffffffff80216b4c>] mmu_page_remove_parent_pte+0xc/0x100
  RSP <ffff8801a0da57a8>
CR2: 0000000000000058
---[ end trace c11385df745a1feb ]---

Starting with a clear disk cach makes the change of this happening 
bigger. The first time the screen mode of one of the vm's just changed 
to the left to right walking progress bar. This time I brought one of 
the windows to the front late in de bootprocess (the windows applying 
computer settings screen).

-- 
Hans

  reply	other threads:[~2009-05-12 22:19 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-12 21:12 just a dump Hans de Bruin
2009-05-12 22:20 ` Hans de Bruin [this message]
2009-05-15 14:49   ` Marcelo Tosatti
2009-05-16  8:38     ` Hans de Bruin
     [not found]       ` <20090516131046.GB3153@amt.cnet>
2009-05-21 10:22         ` Hans de Bruin
2009-05-21 10:36           ` Hans de Bruin
2009-05-21 11:03             ` Hans de Bruin
2009-05-23 21:47             ` Marcelo Tosatti
2009-05-24  8:47               ` Hans de Bruin
2009-05-24 11:49               ` Avi Kivity
2009-05-25 18:47                 ` Marcelo Tosatti
2009-05-21 13:51       ` Lucas Meneghel Rodrigues
2009-05-27  7:43         ` Hans de Bruin
2009-05-28 13:39           ` Lucas Meneghel Rodrigues
2009-07-05 18:40       ` Hans de Bruin
2009-07-06  7:39         ` Avi Kivity

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=4A09F62A.8010203@xs4all.nl \
    --to=bruinjm@xs4all.nl \
    --cc=kvm@vger.kernel.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