public inbox for kvm@vger.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 12:22:45 +0300	[thread overview]
Message-ID: <4C46BC65.9050003@gmail.com> (raw)
In-Reply-To: <20100721083728.GI27238@redhat.com>

Gleb Natapov wrote:
> On Wed, Jul 21, 2010 at 09:25:31AM +0300, Harri Olin wrote:
>> Gleb Natapov kirjoitti:
>>> On Mon, Jul 19, 2010 at 10:17:02AM +0300, Harri Olin wrote:
>>>> Gleb Natapov kirjoitti:
>>>>> On Thu, Jul 15, 2010 at 03:19:44PM +0200, Christoph Adomeit wrote:
>>>>>> But one Windows 2008 64 Bit Server Standard is freezing regularly.
>>>>>> This happens sometimes 3 times a day, sometimes it takes 2 days
>>>>>> until freeze. The Windows Machine is a clean fresh install.
>>>> I think I have seen same problem occur on my Windows 2008 SBS SP2
>>>> 64bit system, but a bit less often, only like once a week.
>>>> Now I haven't seen crashes but only freezes with qemu on 100% and
>>>> virtual system unresponsive.
>>>>
>>>> qemu command line:
>>>>  /usr/local/qemu-kvm-0.11.1/bin/qemu-system-x86_64 -drive
>>>> file=/dev/rigelvg/w2k8system,cache=none,boot=on -drive
>>>> file=/dev/rigelvg/w2k8data,cache=none -m 6144 -vnc :1 -net
>>>> nic,macaddr=C0:FF:12:FB:AA:01,model=e1000 -net tap -smp 4 -localtime
>>>>
>>>>
>>> Try with different model then e1000 please. Default driver that comes
>>> with Windows known to have problems.
>> Didn't help, changed to default realtek emulation, but system
>> freezed again. Command line:
>> /usr/local/qemu-kvm-0.11.1/bin/qemu-system-x86_64 -drive
>> file=/dev/rigelvg/w2k8system,cache=none,boot=on -drive
>> file=/dev/rigelvg/w2k8data,cache=none -m 6144 -vnc :1 -net
>> nic,macaddr=C0:FF:12:FB:AA:01 -net tap -smp 4 -localtime
>>
>> This time the virtual system was not totally unresponsive somehow,
>> system pinged just fine and I think DNS server worked too. However
>> on console mouse moved but didn't react to clicking, ctrl-alt-del,
>> etc.
>>
> Does sendkey from monitor works? qemu-kvm-0.11.1 is very old and this is
> not total freeze which even harder to debug. I don't see anything
> extraordinary in your logs. 4643 interrupt per second for 4 cpus is
> normal if windows runs multimedia or other app that need hi-res timers.
> Does your host swapping? Is there any chance that you can try upstream qemu-kvm?
> 

I haven't tested sendkey. I originally tried 0.12.2 or so but with that 
windows crashed more often with bluescreen, I went down to 0.11.1. This 
might be related to -td-rtc-hack and/or e1000 as using td-rtc-hack on 
0.11.1 windows crashed too to bluescreen.

System does not run any multimedia or so, on top of normal windows 2008 
small business server installation there should be only nagios client 
and apache.

Only thing that catches my eye on stats frozen vs normal is irq_exits 
which jumps from 200 to 10000 when frozen and irq_window which goes 10x.

Host has swap partition enabled but hasn't swapped once yet, currently 
there's over 1GB of free.

I'll update host kernel to latest stable and qemu-kvm to upstream later 
today.

Here's stats from running system:
  efer_reload                  0       0
  exits                386474714   23272
  fpu_reload           173420913   12775
  halt_exits            51894921    4294
  halt_wakeup           51039254    4223
  host_state_reload    188645310   13420
  hypercalls                   0       0
  insn_emulation       212729430   15545
  insn_emulation_fail        324       0
  invlpg                 5177828     134
  io_exits              23132581     161
  irq_exits              7485833     225
  irq_injections        59239306    4655
  irq_window             2147438     153
  largepages                   0       0
  mmio_exits           110931423    9026
  mmu_cache_miss          468410       0
  mmu_flooded             193153       0
  mmu_pde_zapped          352178       0
  mmu_pte_updated         678023       0
  mmu_pte_write           587175       0
  mmu_recycled             34998       0
  mmu_shadow_zapped       454073       0
  mmu_unsync               19084       0
  nmi_injections               0       0
  nmi_window                   0       0
  pf_fixed              25171943     120
  pf_guest               6209034       2
  remote_tlb_flush       3044169      23
  request_irq                  0       0
  signal_exits                 0       0
  tlb_flush              8422950     149


-- 
Harri.

  reply	other threads:[~2010-07-21  9:22 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 [this message]
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
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=4C46BC65.9050003@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox