From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from [140.186.70.92] (port=38390 helo=eggs.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1OEND9-0004US-OI for qemu-devel@nongnu.org; Tue, 18 May 2010 09:52:03 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.69) (envelope-from ) id 1OEND7-0001je-Bv for qemu-devel@nongnu.org; Tue, 18 May 2010 09:51:55 -0400 Received: from cantor2.suse.de ([195.135.220.15]:42966 helo=mx2.suse.de) by eggs.gnu.org with esmtp (Exim 4.69) (envelope-from ) id 1OEND7-0001jN-1G for qemu-devel@nongnu.org; Tue, 18 May 2010 09:51:53 -0400 Message-ID: <4BF29B78.2000604@suse.de> Date: Tue, 18 May 2010 15:51:52 +0200 From: Alexander Graf MIME-Version: 1.0 Subject: Re: [Qemu-devel] Suggested Parameters for SLES 10 64-bit References: <4BF25A7A.1010305@dlh.net> <5F70B456-4DC8-4A05-A872-00259D6C9374@suse.de> <4BF2647B.4090503@dlh.net> <17B889A5-5DC4-4651-8650-118E984DF711@suse.de> <4BF26805.8060008@dlh.net> <29239B8B-DFAB-485E-966B-D1EEDC0292D4@suse.de> <4BF27370.5000800@dlh.net> <676B44BA-E51E-4CBE-AC53-773F2AAAC0BB@suse.de> <4BF27546.8050808@dlh.net> <2A9FC14A-EDF8-4369-81BD-5232A4C6F647@suse.de> <4BF28152.9040100@dlh.net> <4BF28A51.1040603@suse.de> <4BF28DEA.5050402@dlh.net> <4BF28EE5.5070505@suse.de> <4BF29359.5040209@dlh.net> In-Reply-To: <4BF29359.5040209@dlh.net> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Peter Lieven Cc: qemu-devel@nongnu.org, kvm@vger.kernel.org Peter Lieven wrote: > Alexander Graf wrote: >> Peter Lieven wrote: >> >>> we are running on intel xeons here: >>> >> >> That might be the reason. Does it break when passing -no-kvm? >> >> >>> processor : 0 >>> vendor_id : GenuineIntel >>> cpu family : 6 >>> model : 26 >>> model name : Intel(R) Xeon(R) CPU L5530 @ 2.40GHz >>> stepping : 5 >>> cpu MHz : 2394.403 >>> cache size : 8192 KB >>> physical id : 1 >>> siblings : 4 >>> core id : 0 >>> cpu cores : 4 >>> apicid : 16 >>> initial apicid : 16 >>> fpu : yes >>> fpu_exception : yes >>> cpuid level : 11 >>> wp : yes >>> flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge >>> mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe >>> syscall rdtscp lm constant_tsc arch_perfmon pebs bts rep_good >>> xtopology tsc_reliable nonstop_tsc pni dtes64 monitor ds_cpl vmx est >>> tm2 ssse3 cx16 xtpr pdcm dca sse4_1 sse4_2 popcnt lahf_lm tpr_shadow >>> vnmi flexpriority ept vpid >>> bogomips : 4788.80 >>> clflush size : 64 >>> cache_alignment : 64 >>> address sizes : 40 bits physical, 48 bits virtual >>> power management: >>> >>> kvm-kmod is 2.6.32.7 >>> ... >>> >>> which commandline parameters do you supply to qemu-kvm? >>> >> >> None :) >> > It seems to stop working if i supply -no-kvm-irqchip. Can you try to > reproduce this? > > We introduced that parameter because we encountered some problems with > the e1000 kernel driver stopped to work in some > guests after live migration with a "nobody cared about interupt" (i > don't know the exact error anymore). supplying > -no-kvm-irqchip made live migration of these guests possible... > Sounds that familiar to someone? So it works with the in-kernel irqchip? That's the normally supported configuration anyways. If migration fails with that, that's a different thing and definitely needs to be addressed. Alex