public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Gleb Natapov <gleb@redhat.com>
To: Christoph Adomeit <Christoph.Adomeit@gatworks.de>
Cc: kvm@vger.kernel.org
Subject: Re: Freezing Windows 2008 x64bit guest
Date: Thu, 15 Jul 2010 16:44:41 +0300	[thread overview]
Message-ID: <20100715134441.GQ4689@redhat.com> (raw)
In-Reply-To: <20100715131944.GA24978@mp3.niederrhein.de>

On Thu, Jul 15, 2010 at 03:19:44PM +0200, Christoph Adomeit wrote:
> Hi,
> 
> we are running several kvm servers with kvm 0.12.4 and kernel 2.6.32
> (actually we run proxmox ve)
> 
> These proxmox servers are running all kinds of vms rock-solid, be it
> linux or windows 32 platforms.
> 
> 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.
> 
> By Freezing I mean that the Machine console still shows the 
> windows logo but does not accept any keystroke and does not answer
> to ping or rdp or whatever. The virtual cpu-load is then shown
> as 100% (by proxmox).
> 
> We tried several combinations of ide or virtio, several virtual network cards (intel and realtek) and single-cpu vs multi cpu. The Problem persists.
> 
> The Windows Machine is a quite fresh install but runs exchange and 10 rdp sessions.
> 
> We are experienced linux-admins but we dont find any hints on the kvm servers what might be the problem, no syslogs,dmesgs, nothing. Also there are no 
> dumps on the windows guest.
> 
> Do you have any hints what might be the problem and what we could do to debug the problem and to get more information of the root cause ?
> 
When hang occurs ensure that problematic vm is the only on on the server and run
kvm_stat. Send output here. Also do the following:

# mount -t debugfs debugfs /sys/kernel/debug
# echo kvm > /sys/kernel/debug/tracing/set_event
# sleep 1
# cat /sys/kernel/debug/tracing/trace > /tmp/trace

Send /tmp/trace here too, but it may be huge, so send only last 1000
lines.

--
			Gleb.

  reply	other threads:[~2010-07-15 13:44 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 [this message]
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
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=20100715134441.GQ4689@redhat.com \
    --to=gleb@redhat.com \
    --cc=Christoph.Adomeit@gatworks.de \
    --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