From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S965724AbXDWKTH (ORCPT ); Mon, 23 Apr 2007 06:19:07 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S965714AbXDWKTH (ORCPT ); Mon, 23 Apr 2007 06:19:07 -0400 Received: from mx2.mail.elte.hu ([157.181.151.9]:53223 "EHLO mx2.mail.elte.hu" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S965724AbXDWKTG (ORCPT ); Mon, 23 Apr 2007 06:19:06 -0400 Date: Mon, 23 Apr 2007 12:18:39 +0200 From: Ingo Molnar To: Christian Hesse Cc: linux-kernel@vger.kernel.org, Con Kolivas , Nick Piggin , Mike Galbraith , Arjan van de Ven , Peter Williams , Thomas Gleixner , caglar@pardus.org.tr, Willy Tarreau , Gene Heskett , kvm-devel@lists.sourceforge.net, Avi Kivity Subject: Re: crash with CFS v4 and qemu/kvm (was: [patch] CFS scheduler, v4) Message-ID: <20070423101839.GA19599@elte.hu> References: <20070420140457.GA14017@elte.hu> <200704231128.23594.mail@earthworm.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200704231128.23594.mail@earthworm.de> User-Agent: Mutt/1.4.2.2i X-ELTE-VirusStatus: clean X-ELTE-SpamScore: -2.0 X-ELTE-SpamLevel: X-ELTE-SpamCheck: no X-ELTE-SpamVersion: ELTE 2.0 X-ELTE-SpamCheck-Details: score=-2.0 required=5.9 tests=BAYES_00 autolearn=no SpamAssassin version=3.0.3 -2.0 BAYES_00 BODY: Bayesian spam probability is 0 to 1% [score: 0.0000] Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org * Christian Hesse wrote: > On Friday 20 April 2007, Ingo Molnar wrote: > > i'm pleased to announce release -v4 of the CFS patchset. > > Hi Ingo, hi Avi, hi all, > > I'm trying to use kvm-20 with cfs v4 and get a crash: > > eworm@revo:~$ /usr/local/kvm/bin/qemu -snapshot /mnt/data/virtual/qemu/winxp.img > kvm_run: failed entry, reason 7 > kvm_run returned -8 > > It works (though it is a bit slow) if I start qemu with strace, so for > me it looks like a race condition? hm. Can you work it around with: echo 0 > /proc/sys/kernel/sched_granularity_ns ? If yes then this is a wakeup race: some piece of code relies on the upstream scheduler preempting the waker task immediately in 99% of the cases. and you might want to test -v5 too which i released earlier today. It has no bugfix in this area though, so it will likely still trigger this race - but it will also hopefully be even more pleasant to use than -v4 ;-) Ingo