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: Thu, 13 Sep 2012 20:32:05 +0200 [thread overview]
Message-ID: <505226A5.1030809@suse.cz> (raw)
In-Reply-To: <5051AE8B.7090904@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 1702 bytes --]
On 09/13/2012 11:59 AM, Avi Kivity wrote:
> On 09/12/2012 09:11 PM, Jiri Slaby wrote:
>> 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
>
> Strange, it's unable to fault in the very first page.
>
> Please provide a trace as per http://www.linux-kvm.org/page/Tracing (but
> append -e kvmmmu to the command line).
Attached. Does it make sense? It wrote things like:
failed to read event print fmt for kvm_mmu_unsync_page
to the stderr.
thanks,
--
js
suse labs
[-- Attachment #2: report --]
[-- Type: text/plain, Size: 1627 bytes --]
version = 6
CPU 0 is empty
cpus=2
qemu-kvm-6170 [001] 457.811896: kvm_mmu_get_page: [FAILED TO PARSE] gfn=0 role=122882 root_count=0 unsync=0 created=1
qemu-kvm-6170 [001] 457.811899: kvm_mmu_get_page: [FAILED TO PARSE] gfn=262144 role=122882 root_count=0 unsync=0 created=1
qemu-kvm-6170 [001] 457.811900: kvm_mmu_get_page: [FAILED TO PARSE] gfn=524288 role=122882 root_count=0 unsync=0 created=1
qemu-kvm-6170 [001] 457.811902: kvm_mmu_get_page: [FAILED TO PARSE] gfn=786432 role=122882 root_count=0 unsync=0 created=1
qemu-kvm-6171 [001] 462.416705: kvm_mmu_prepare_zap_page: [FAILED TO PARSE] gfn=786432 role=122882 root_count=1 unsync=0
qemu-kvm-6171 [001] 462.416712: kvm_mmu_prepare_zap_page: [FAILED TO PARSE] gfn=524288 role=122882 root_count=1 unsync=0
qemu-kvm-6171 [001] 462.416715: kvm_mmu_prepare_zap_page: [FAILED TO PARSE] gfn=262144 role=122882 root_count=1 unsync=0
qemu-kvm-6171 [001] 462.416717: kvm_mmu_prepare_zap_page: [FAILED TO PARSE] gfn=0 role=122882 root_count=1 unsync=0
qemu-kvm-6171 [001] 462.485197: kvm_mmu_prepare_zap_page: [FAILED TO PARSE] gfn=0 role=253954 root_count=0 unsync=0
qemu-kvm-6171 [001] 462.485202: kvm_mmu_prepare_zap_page: [FAILED TO PARSE] gfn=262144 role=253954 root_count=0 unsync=0
qemu-kvm-6171 [001] 462.485205: kvm_mmu_prepare_zap_page: [FAILED TO PARSE] gfn=524288 role=253954 root_count=0 unsync=0
qemu-kvm-6171 [001] 462.485209: kvm_mmu_prepare_zap_page: [FAILED TO PARSE] gfn=786432 role=253954 root_count=0 unsync=0
next prev parent reply other threads:[~2012-09-13 18:32 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
2012-09-13 9:59 ` Avi Kivity
2012-09-13 18:32 ` Jiri Slaby [this message]
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=505226A5.1030809@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