From: Gleb Natapov <gleb@redhat.com>
To: Phil Daws <uxbod@splatnix.net>
Cc: kvm@vger.kernel.org
Subject: Re: KVM Guest Lock up (100%) again!
Date: Wed, 10 Apr 2013 17:10:27 +0300 [thread overview]
Message-ID: <20130410141027.GI17919@redhat.com> (raw)
In-Reply-To: <717425441.1193987.1365451324088.JavaMail.root@innovot.com>
On Mon, Apr 08, 2013 at 09:02:04PM +0100, Phil Daws wrote:
> Hello all,
>
> Another lock up again this evening :( am wondering whether should consider upgrading the kernel to 3.7.10 and the latest version of KVM. Thoughts ?
>
Please try with latest kvm/qemu. This is not the list to report vendor specific problems.
> Thanks.
>
> ----- Original Message -----
> To: kvm@vger.kernel.org
> Sent: Thursday, 4 April, 2013 3:36:11 PM
> Subject: KVM Guest Lock up (100%) again!
>
> 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.
> --
> To unsubscribe from this list: send the line "unsubscribe kvm" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> --
> To unsubscribe from this list: send the line "unsubscribe kvm" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
--
Gleb.
next prev parent reply other threads:[~2013-04-10 14:10 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 ` KVM Guest Lock up (100%) again! Phil Daws
2013-04-08 20:02 ` Phil Daws
2013-04-10 14:10 ` Gleb Natapov [this message]
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=20130410141027.GI17919@redhat.com \
--to=gleb@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=uxbod@splatnix.net \
/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