All of lore.kernel.org
 help / color / mirror / Atom feed
From: Phil Daws <uxbod@splatnix.net>
To: kvm@vger.kernel.org
Subject: KVM Guest Lock up (100%) again!
Date: Thu, 4 Apr 2013 15:36:11 +0100 (BST)	[thread overview]
Message-ID: <764654559.1031795.1365086171933.JavaMail.root@innovot.com> (raw)
In-Reply-To: <2122448695.1031741.1365086071426.JavaMail.root@innovot.com>

One of my KVM guests locked up again at 100% CPU!  Any thoughts on how I can diagnose it ? We would love to put into production but am very concerned about the current stability. I have tried to re-direct the console, through screen, to see whether there is a spin lock that is causing the problem; though all I got in the log file was a login prompt. What is the correct way of redirecting the console in KVM on a CentOS 6.4 system please ? Thanks.

       reply	other threads:[~2013-04-04 14:37 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <2122448695.1031741.1365086071426.JavaMail.root@innovot.com>
2013-04-04 14:36 ` Phil Daws [this message]
2013-04-08 20:02   ` KVM Guest Lock up (100%) again! Phil Daws
2013-04-10 14:10     ` Gleb Natapov
2013-04-12 14:10       ` Phil Daws
2013-04-12 15:13         ` Gleb Natapov
2013-04-12 16:31           ` Phil Daws

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=764654559.1031795.1365086171933.JavaMail.root@innovot.com \
    --to=uxbod@splatnix.net \
    --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.