From mboxrd@z Thu Jan 1 00:00:00 1970 From: Avi Kivity Subject: Re: soft lockup after stop/cont Date: Wed, 10 Oct 2007 10:04:59 +0200 Message-ID: <470C87AB.6050900@qumranet.com> References: <20071010080152.GA27601@jim.sh> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Cc: kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org To: Jim Paris Return-path: In-Reply-To: <20071010080152.GA27601-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? No. > What isn't virtualized that allows it to > detect that? The host is a core 2 duo. > > It may be that the timer correction code detects that zillions of timer interrupts have not been serviced by the guest so it floods the guest with these interrupts. Does -no-kvm-irqchip help? -- Do not meddle in the internals of kernels, for they are subtle and quick to panic. ------------------------------------------------------------------------- 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/