From mboxrd@z Thu Jan 1 00:00:00 1970 From: Carsten Otte Subject: Re: soft lockup after stop/cont Date: Thu, 11 Oct 2007 11:03:52 +0200 Message-ID: <470DE6F8.9090801@de.ibm.com> References: <20071010080152.GA27601@jim.sh> <470C87AB.6050900@qumranet.com> <20071010185443.GA14525@jim.sh> Reply-To: carsteno-tA70FqPdS9bQT0dZR+AlfA@public.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Cc: kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org, Avi Kivity To: Jim Paris Return-path: In-Reply-To: <20071010185443.GA14525-lSbMZ+N7itA@public.gmane.org> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: kvm-devel-bounces-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org Errors-To: kvm-devel-bounces-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org List-Id: kvm.vger.kernel.org Jim Paris wrote: > If I stop KVM in the monitor with "stop", wait a minute, and do > "cont", a Linux guest gives me a "BUG: soft lockup detected on CPU#0". > Is that expected behavior? We have the same behavior on s390 when running in a virtual environment. The issue is, that the guest physical cpu may be scheduled away while a timer runs down. I don't think there's anything kvm could do better regerding the soft lockup code. Soft lockup is just broken for virtualized environments and needs to be fixed. For the time being, just disable it in kconfig. ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/