From mboxrd@z Thu Jan 1 00:00:00 1970 From: Phil Daws Subject: Re: KVM Guest Lock up (100%) again! Date: Mon, 8 Apr 2013 21:02:04 +0100 (BST) Message-ID: <717425441.1193987.1365451324088.JavaMail.root@innovot.com> References: <764654559.1031795.1365086171933.JavaMail.root@innovot.com> Reply-To: Phil Daws Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit To: kvm@vger.kernel.org Return-path: Received: from mx1.dc1.innovot.com ([77.73.4.109]:33664 "EHLO mx1.dc1.innovot.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S935872Ab3DHUDX (ORCPT ); Mon, 8 Apr 2013 16:03:23 -0400 Received: from sm1.dc3.innovot.com (sm1.dc3.innovot.com [192.168.1.208]) by mx1.dc3.innovot.com (Postfix) with ESMTP id C609840011 for ; Mon, 8 Apr 2013 21:02:09 +0100 (BST) Received: from localhost ([127.0.0.1]) by sm1.dc3.innovot.com with SMTP ID 807 for ; Mon, 8 Apr 2013 21:02:08 +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 9AC6140011 for ; Mon, 8 Apr 2013 21:02:08 +0100 (BST) Received: from wm1.dc3.innovot.com (unknown [192.168.1.221]) by mx1.dc3.innovot.com (Postfix) with ESMTP id F3FCA40011 for ; Mon, 8 Apr 2013 21:02:05 +0100 (BST) Received: from wm1.dc3.innovot.com (localhost.localdomain [127.0.0.1]) by wm1.dc3.innovot.com (Postfix) with ESMTP id 7543CCDAC7 for ; Mon, 8 Apr 2013 21:02:05 +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 2E129CDABC for ; Mon, 8 Apr 2013 21:02:05 +0100 (BST) In-Reply-To: <764654559.1031795.1365086171933.JavaMail.root@innovot.com> Sender: kvm-owner@vger.kernel.org List-ID: 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 ? 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