From: "SourceForge.net" <noreply@sourceforge.net>
To: noreply@sourceforge.net
Subject: [ kvm-Bugs-1906189 ] All SMP guests often halt
Date: Tue, 25 Aug 2009 02:20:29 +0000 [thread overview]
Message-ID: <E1Mfle9-0003el-RX@49zxpd1.ch3.sourceforge.com> (raw)
Bugs item #1906189, was opened at 2008-03-03 11:33
Message generated for change (Comment added) made by sf-robot
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=893831&aid=1906189&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: None
Group: None
>Status: Closed
Resolution: None
Priority: 5
Private: No
Submitted By: Technologov (technologov)
Assigned to: Nobody/Anonymous (nobody)
Summary: All SMP guests often halt
Initial Comment:
All SMP configurations are very unstable - both on Intel and AMD. KVM-62.
Symptons: guests often soft-lock ups, or more precisely, they slow down to unacceptable speeds.
Guests may hard-lockup totally, or even BSOD in some cases.
I have tried:
Windows 2000
Windows XP
Windows Server 2003
Windows Server 2008
The KVM acts, but it looks like a loop.
=====================================================
[alexeye@pink-intel win2000-Pro]$ dmesg | tail -n40
Ignoring de-assert INIT to vcpu 0
Ignoring de-assert INIT to vcpu 1
Ignoring de-assert INIT to vcpu 0
Ignoring de-assert INIT to vcpu 1
SIPI to vcpu 1 vector 0x10
apic write: bad size=1 fee00030
Ignoring de-assert INIT to vcpu 0
Ignoring de-assert INIT to vcpu 1
Ignoring de-assert INIT to vcpu 0
Ignoring de-assert INIT to vcpu 1
SIPI to vcpu 1 vector 0x10
apic write: bad size=1 fee00030
Ignoring de-assert INIT to vcpu 0
Ignoring de-assert INIT to vcpu 1
Ignoring de-assert INIT to vcpu 0
Ignoring de-assert INIT to vcpu 1
Ignoring de-assert INIT to vcpu 1
SIPI to vcpu 1 vector 0x21
SIPI to vcpu 1 vector 0x21
SIPI to vcpu 1 vector 0x21
Ignoring de-assert INIT to vcpu 0
Ignoring de-assert INIT to vcpu 1
SIPI to vcpu 1 vector 0x21
Ignoring de-assert INIT to vcpu 0
Ignoring de-assert INIT to vcpu 1
SIPI to vcpu 1 vector 0x10
apic write: bad size=1 fee00030
Ignoring de-assert INIT to vcpu 0
Ignoring de-assert INIT to vcpu 1
Ignoring de-assert INIT to vcpu 0
Ignoring de-assert INIT to vcpu 1
Ignoring de-assert INIT to vcpu 1
SIPI to vcpu 1 vector 0x21
SIPI to vcpu 1 vector 0x21
SIPI to vcpu 1 vector 0x21
Ignoring de-assert INIT to vcpu 0
Ignoring de-assert INIT to vcpu 1
SIPI to vcpu 1 vector 0x21
Ignoring de-assert INIT to vcpu 0
Ignoring de-assert INIT to vcpu 1
=====================================================
(gdb) bt
#0 0x0000003a016c9aa7 in ioctl () from /lib64/libc.so.6
#1 0x000000000051bb29 in kvm_run (kvm=0x2a9b040, vcpu=0) at libkvm.c:850
#2 0x00000000004fda86 in kvm_cpu_exec (env=<value optimized out>)
at /root/Linstall/kvm-62rc2/qemu/qemu-kvm.c:127
#3 0x00000000004fe5d5 in kvm_main_loop_cpu (env=0x2b56490)
at /root/Linstall/kvm-62rc2/qemu/qemu-kvm.c:307
#4 0x00000000004110fd in main (argc=44675488, argv=<value optimized out>)
at /root/Linstall/kvm-62rc2/qemu/vl.c:7862
=====================================================
kvm statistics
efer_reload 103701 0
exits 512480997 20642
fpu_reload 24781662 799
halt_exits 1824249 170
halt_wakeup 828699 68
host_state_reload 49593245 1617
hypercalls 0 0
insn_emulation 389188282 14239
insn_emulation_fail 1110 0
invlpg 0 0
io_exits 28855411 928
irq_exits 19131361 3248
irq_window 0 0
largepages 0 0
mmio_exits 16078802 0
mmu_cache_miss 4219404 415
mmu_flooded 4110773 410
mmu_pde_zapped 499335 6
mmu_pte_updated 10381639 1327
mmu_pte_write 14567944 1737
mmu_recycled 17419 0
mmu_shadow_zapped 4372079 410
=====================================================
-Alexey, 03.03.2008.
----------------------------------------------------------------------
>Comment By: SourceForge Robot (sf-robot)
Date: 2009-08-25 02:20
Message:
This Tracker item was closed automatically by the system. It was
previously set to a Pending status, and the original submitter
did not respond within 14 days (the time period specified by
the administrator of this Tracker).
----------------------------------------------------------------------
Comment By: Avi Kivity (avik)
Date: 2009-08-10 12:29
Message:
Does this still happen?
----------------------------------------------------------------------
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=893831&aid=1906189&group_id=180599
next reply other threads:[~2009-08-25 2:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-25 2:20 SourceForge.net [this message]
-- strict thread matches above, loose matches on Subject: below --
2009-08-10 12:29 [ kvm-Bugs-1906189 ] All SMP guests often halt SourceForge.net
2008-03-03 11:33 SourceForge.net
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=E1Mfle9-0003el-RX@49zxpd1.ch3.sourceforge.com \
--to=noreply@sourceforge.net \
/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;
as well as URLs for NNTP newsgroup(s).