From mboxrd@z Thu Jan  1 00:00:00 1970
From: Phil Daws <uxbod@splatnix.net>
Subject: KVM Guest Lock up (100%) again!
Date: Thu, 4 Apr 2013 15:36:11 +0100 (BST)
Message-ID: <764654559.1031795.1365086171933.JavaMail.root@innovot.com>
References: <2122448695.1031741.1365086071426.JavaMail.root@innovot.com>
Reply-To: Phil Daws <uxbod@splatnix.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
To: kvm@vger.kernel.org
Return-path: <kvm-owner@vger.kernel.org>
Received: from mx1.dc1.innovot.com ([77.73.4.109]:52801 "EHLO
	mx1.dc1.innovot.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
	with ESMTP id S1761594Ab3DDOhb (ORCPT <rfc822;kvm@vger.kernel.org>);
	Thu, 4 Apr 2013 10:37:31 -0400
Received: from sm1.dc3.innovot.com (sm1.dc3.innovot.com [192.168.1.208])
	by mx1.dc3.innovot.com (Postfix) with ESMTP id 291DD4000E
	for <kvm@vger.kernel.org>; Thu,  4 Apr 2013 15:36:20 +0100 (BST)
Received: from localhost ([127.0.0.1])
          by sm1.dc3.innovot.com with SMTP ID 494
          for <kvm@vger.kernel.org>;
          Thu, 4 Apr 2013 15:36:19 +0100 (BST)
Received: from mx1.dc3.innovot.com (localhost [127.0.0.1])
	(using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
	(No client certificate requested)
	by mx1.dc3.innovot.com (Postfix) with ESMTPS id E8BFF4000E
	for <kvm@vger.kernel.org>; Thu,  4 Apr 2013 15:36:18 +0100 (BST)
Received: from wm1.dc3.innovot.com (unknown [192.168.1.221])
	by mx1.dc3.innovot.com (Postfix) with ESMTP id 1A9054000E
	for <kvm@vger.kernel.org>; Thu,  4 Apr 2013 15:36:14 +0100 (BST)
Received: from wm1.dc3.innovot.com (localhost.localdomain [127.0.0.1])
	by wm1.dc3.innovot.com (Postfix) with ESMTP id 997FDCCB1C
	for <kvm@vger.kernel.org>; Thu,  4 Apr 2013 15:36:13 +0100 (BST)
Received: from wm1.dc3.innovot.com (wm1.dc3.innovot.com [192.168.1.221])
	by wm1.dc3.innovot.com (Postfix) with ESMTP id 329FDCCB15
	for <kvm@vger.kernel.org>; Thu,  4 Apr 2013 15:36:13 +0100 (BST)
In-Reply-To: <2122448695.1031741.1365086071426.JavaMail.root@innovot.com>
Sender: kvm-owner@vger.kernel.org
List-ID: <kvm.vger.kernel.org>

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.