public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Gleb Natapov <gleb@redhat.com>
To: Harri Olin <harri.olin@gmail.com>
Cc: Christoph Adomeit <Christoph.Adomeit@gatworks.de>,
	"kvm@vger.kernel.org" <kvm@vger.kernel.org>
Subject: Re: Freezing Windows 2008 x64bit guest
Date: Wed, 21 Jul 2010 16:45:16 +0300	[thread overview]
Message-ID: <20100721134516.GA27177@redhat.com> (raw)
In-Reply-To: <4C46F020.7020800@gmail.com>

On Wed, Jul 21, 2010 at 04:03:28PM +0300, Harri Olin wrote:
> Gleb Natapov wrote:
> >On Wed, Jul 21, 2010 at 01:09:06PM +0300, Harri Olin wrote:
> >>Gleb Natapov wrote:
> >>On both times irq_exits go to 10000 but irq_injections stay at
> >>around 4600. On both times qemu process was at 100% cpu load.
> >irq_exits are exits due to host interrupt. What "cat /proc/interrupts"
> >show? Which counter grows at this rate there (or 1/4 of the rate but for
> >each host cpu).
> 
> System froze again just a moment ago and there are 6100 "local timer
> interrupts" and around 3600 "Rescheduling interrupts" every second
> happening.
> 
> #cat /proc/interrupts; sleep 1; cat /proc/interrupts; sleep 1; ....
> http://mizar.remote.agasha.com/k/kvm/interrupts.txt
> http://mizar.remote.agasha.com/k/kvm/interrupts1.txt
> 
> quick calculations
>                                              total
> RES: 110847929 115251972 108671867 114338799 449110567 	per second:
> RES: 110848996 115252094 108673031 114340080 449114201 	3634
> RES: 110850059 115252174 108674157 114341446 449117836 	3635
> RES: 110851132 115252276 108675332 114342801 449121541 	3705
> 						
>                                                total		
> LOC: 1531251837 618157953 1727791012 522296117 4399496919 per second:
> LOC: 1531252861 618161024 1727792036 522297141 4399503062 6143
> LOC: 1531253884 618164095 1727793060 522298165 4399509204 6142
> LOC: 1531254907 618167166 1727794084 522299189 4399515346 6142

Same qemu and command line as before? Without -no-hpet?

--
			Gleb.

  reply	other threads:[~2010-07-21 13:45 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-15 13:19 Freezing Windows 2008 x64bit guest Christoph Adomeit
2010-07-15 13:44 ` Gleb Natapov
2010-07-19  7:17   ` Harri Olin
2010-07-19  7:42     ` Gleb Natapov
2010-07-21  6:25       ` Harri Olin
2010-07-21  8:28         ` Christoph Adomeit
2010-07-21  8:37         ` Gleb Natapov
2010-07-21  9:22           ` Harri Olin
2010-07-21  9:48             ` Gleb Natapov
2010-07-21 10:09               ` Harri Olin
2010-07-21 10:30                 ` Gleb Natapov
2010-07-21 10:43                   ` Harri Olin
2010-07-21 13:03                   ` Harri Olin
2010-07-21 13:45                     ` Gleb Natapov [this message]
2010-07-21 14:05                       ` Harri Olin
2010-07-27 21:53           ` Harri Olin
2010-07-28 15:18             ` Gleb Natapov
2010-12-13 19:42               ` Manfred Heubach
2010-12-13 20:12                 ` Dor Laor
2010-12-13 20:44                   ` Vadim Rozenfeld
2010-12-14 23:57                     ` AW: " Manfred Heubach
2010-12-15 10:48                       ` Vadim Rozenfeld

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=20100721134516.GA27177@redhat.com \
    --to=gleb@redhat.com \
    --cc=Christoph.Adomeit@gatworks.de \
    --cc=harri.olin@gmail.com \
    --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