From: Jiri Slaby <jslaby@suse.cz>
To: Avi Kivity <avi@redhat.com>
Cc: Jiri Slaby <jirislaby@gmail.com>,
Marcelo Tosatti <mtosatti@redhat.com>,
kvm@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>
Subject: Re: qemu-kvm loops after kernel udpate
Date: Wed, 12 Sep 2012 20:11:20 +0200 [thread overview]
Message-ID: <5050D048.4010704@suse.cz> (raw)
In-Reply-To: <5050453B.6040702@redhat.com>
On 09/12/2012 10:18 AM, Avi Kivity wrote:
> On 09/12/2012 11:13 AM, Jiri Slaby wrote:
>>
>>> Please provide the output of vmxcap
>>> (http://goo.gl/c5lUO),
>>
>> Unrestricted guest no
>
> The big real mode fixes.
>
>
>>
>>> and a snapshot of kvm_stat while the guest is hung.
>>
>> kvm statistics
>>
>> exits 6778198 615942
>> host_state_reload 1988 187
>> irq_exits 1523 138
>> mmu_cache_miss 4 0
>> fpu_reload 1 0
>
> Please run this as root so we get the tracepoint based output; and press
> 'x' when it's running so we get more detailed output.
kvm statistics
kvm_exit 13798699 330708
kvm_entry 13799110 330708
kvm_page_fault 13793650 330604
kvm_exit(EXCEPTION_NMI) 6188458 330604
kvm_exit(EXTERNAL_INTERRUPT) 2169 105
kvm_exit(TPR_BELOW_THRESHOLD) 82 0
kvm_exit(IO_INSTRUCTION) 6 0
kvm_exit(PAUSE_INSTRUCTION) 5 0
kvm_exit(MCE_DURING_VMENTRY) 5 0
kvm_exit(DR_ACCESS) 5 0
kvm_exit(VMPTRLD) 5 0
kvm_exit(VMLAUNCH) 5 0
kvm_exit(INVLPG) 5 0
kvm_exit(VMCALL) 5 0
kvm_exit(WBINVD) 5 0
kvm_exit(MONITOR_INSTRUCTION) 5 0
kvm_exit(MWAIT_INSTRUCTION) 4 0
kvm_exit(NMI_WINDOW) 4 0
kvm_exit(VMREAD) 4 0
kvm_exit(XSETBV) 4 0
kvm_exit(RDPMC) 4 0
kvm_exit(CPUID) 4 0
kvm_exit(VMCLEAR) 4 0
kvm_exit(PENDING_INTERRUPT) 4 0
kvm_exit(VMRESUME) 4 0
kvm_exit(APIC_ACCESS) 4 0
kvm_exit(INVALID_STATE) 4 0
kvm_exit(MSR_READ) 4 0
kvm_exit(VMOFF) 4 0
kvm_exit(RDTSC) 4 0
kvm_exit(MSR_WRITE) 4 0
kvm_exit(VMPTRST) 4 0
kvm_exit(VMWRITE) 4 0
kvm_exit(HLT) 3 0
kvm_exit(EPT_VIOLATION) 3 0
kvm_exit(TASK_SWITCH) 3 0
kvm_exit(CR_ACCESS) 3 0
kvm_exit(TRIPLE_FAULT) 3 0
kvm_exit(VMON) 3 0
kvm_exit(EPT_MISCONFIG) 3 0
thanks,
--
js
suse labs
next prev parent reply other threads:[~2012-09-12 18:11 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-11 18:11 qemu-kvm loops after kernel udpate Jiri Slaby
2012-09-11 19:03 ` Marcelo Tosatti
2012-09-11 19:41 ` Jiri Slaby
2012-09-12 8:06 ` Avi Kivity
2012-09-12 8:13 ` Jiri Slaby
2012-09-12 8:18 ` Avi Kivity
2012-09-12 8:20 ` Jiri Slaby
2012-09-12 18:11 ` Jiri Slaby [this message]
2012-09-13 9:59 ` Avi Kivity
2012-09-13 18:32 ` Jiri Slaby
2012-09-18 19:40 ` Jiri Slaby
2012-09-18 19:46 ` Andrew Morton
2012-09-19 0:00 ` Stephen Rothwell
2012-09-19 0:20 ` Andrew Morton
2012-09-19 1:36 ` Stephen Rothwell
2012-09-19 14:18 ` [PATCH] mm: call invalidate_range_end in do_wp_page even for zero pages Haggai Eran
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=5050D048.4010704@suse.cz \
--to=jslaby@suse.cz \
--cc=avi@redhat.com \
--cc=jirislaby@gmail.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mtosatti@redhat.com \
/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).