From mboxrd@z Thu Jan 1 00:00:00 1970 From: Avi Kivity Subject: Re: external module sched_in event Date: Sat, 22 Dec 2007 22:24:26 +0200 Message-ID: <476D727A.7090104@qumranet.com> References: <20071221174048.GB1292@v2.random> <476BFD74.2040509@qumranet.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Cc: kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org, Andrea Arcangeli To: Izik Eidus Return-path: In-Reply-To: <476BFD74.2040509-atKUWr5tajBWk0Htik3J/w@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 Izik Eidus wrote: >> This fixes my longstanding KVM instability and "-smp 2" now works >> flawlessy with svm too! -smp 2 -snapshot crashes in qemu userland but >> that's not kernel related, must be some thread mutex lock recursion or >> lock inversion in the qcow cow code. Removing -snapshot make -smp 2 >> stable. Multiple guests UP and SMP seems stable too. >> >> > you mean that without -snapshot, the userspace not hang at the sigwait() > in the qcow code? > The problem is probably exaggerated by -snapshot, which needs much more metadata activity than without -snapshot. -- Do not meddle in the internals of kernels, for they are subtle and quick to panic. ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/