linux-kernel - Re: qemu-kvm loops after kernel udpate

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Thu, 13 Sep 2012 20:32:05 +0200
From:	Jiri Slaby <jslaby@...e.cz>
To:	Avi Kivity <avi@...hat.com>
CC:	Jiri Slaby <jirislaby@...il.com>,
	Marcelo Tosatti <mtosatti@...hat.com>, kvm@...r.kernel.org,
	LKML <linux-kernel@...r.kernel.org>
Subject: Re: qemu-kvm loops after kernel udpate

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

View attachment "report" of type "text/plain" (1628 bytes)