All of lore.kernel.org
 help / color / mirror / Atom feed
From: Harri Olin <harri.olin@gmail.com>
To: Gleb Natapov <gleb@redhat.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 13:43:08 +0300	[thread overview]
Message-ID: <4C46CF3C.6070109@gmail.com> (raw)
In-Reply-To: <20100721103025.GK27238@redhat.com>

Gleb Natapov wrote:
> On Wed, Jul 21, 2010 at 01:09:06PM +0300, Harri Olin wrote:
>> Gleb Natapov wrote:
>> Frozen kvm_stat can be seen here; when I grabbed this, windows did
>> not answer to ping.
>> stats: http://mizar.remote.agasha.com/k/kvm/kvm_stat_hang.txt
>> trace: http://mizar.remote.agasha.com/k/kvm/kvm_trace_hang.txt
> Not much happens here. Windows gets timer irqs at 1024Hz rate and
> process them. What is your host kernel? Does it have hi-res timers?

Host kernel is vanilla 2.6.33.1 from kernel.org. Should have hi-res 
timers enabled.
full dmesg at: http://mizar.remote.agasha.com/k/kvm/dmesg.txt

[    0.415380] HPET: 4 timers in total, 0 timers will be used for 
per-cpu timer
[    0.416004] hpet0: at MMIO 0xfed00000, IRQs 2, 8, 0, 0
[    0.416263] hpet0: 4 comparators, 64-bit 14.318180 MHz counter

>> Here's another frozen state stat dump; when I got this windows did
>> answer to ping but was otherwise unresponsive:
>> stats: http://mizar.remote.agasha.com/k/kvm/kvm_stat_2_log.txt
>> trace: http://mizar.remote.agasha.com/k/kvm/kvm_trace_2.txt
>>
>> 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).

I have to check that next time when freeze happens.

# cat /proc/interrupts
            CPU0       CPU1       CPU2       CPU3
   0:       1144       1056       1081       1072   IO-APIC-edge      timer
   1:        324        329        348        329   IO-APIC-edge      i8042
   3:          1          1          0          0   IO-APIC-edge
   4:          0          0          1          1   IO-APIC-edge
   8:         16         15         15         15   IO-APIC-edge      rtc0
   9:          0          0          0          0   IO-APIC-fasteoi   acpi
  12:          1          1          0          1   IO-APIC-edge      i8042
  16:          0          0          0          0   IO-APIC-fasteoi 
uhci_hcd:usb3
  17:          0          0          0          0   IO-APIC-fasteoi 
uhci_hcd:usb4
  18:   47695411   47681526   47693374   47680775   IO-APIC-fasteoi 
arcmsr, ehci_hcd:usb1, uhci_hcd:usb5, uhci_hcd:usb8
  22:          0          0          0          0   IO-APIC-fasteoi 
uhci_hcd:usb7
  23:          0          0          0          0   IO-APIC-fasteoi 
ehci_hcd:usb2, uhci_hcd:usb6
  28:    2376183    2377506    2376812    2376143   PCI-MSI-edge      ahci
  29:   14545152   14557669   14546472   14559769   PCI-MSI-edge      eth0
NMI:          0          0          0          0   Non-maskable interrupts
LOC: 1522685098  614396609 1720798830  518770603   Local timer interrupts
SPU:          0          0          0          0   Spurious interrupts
PMI:          0          0          0          0   Performance 
monitoring interrupts
PND:          0          0          0          0   Performance pending work
RES:  109858789  114294880  107422261  113139171   Rescheduling interrupts
CAL:  228945035  210709845  246864690  232136482   Function call interrupts
TLB:       1161       2146       1090       2319   TLB shootdowns
TRM:          0          0          0          0   Thermal event interrupts
THR:          0          0          0          0   Threshold APIC interrupts
MCE:          0          0          0          0   Machine check exceptions
MCP:       4226       4226       4226       4226   Machine check polls
ERR:          0
MIS:          0

Also at: http://mizar.remote.agasha.com/k/kvm/interrupts.txt

-- 
Harri.

  reply	other threads:[~2010-07-21 10:43 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 [this message]
2010-07-21 13:03                   ` Harri Olin
2010-07-21 13:45                     ` Gleb Natapov
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=4C46CF3C.6070109@gmail.com \
    --to=harri.olin@gmail.com \
    --cc=Christoph.Adomeit@gatworks.de \
    --cc=gleb@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.