From mboxrd@z Thu Jan 1 00:00:00 1970 From: Sebastian Hetze Subject: Re: syscall rmdir hangs with autofs Date: Mon, 19 Jul 2010 17:38:15 +0200 Message-ID: <20100719153816.41DBDB0016@mail.linux-ag.de> References: <20100719114034.62BDD30303F5@mail.linux-ag.de> <4C444358.8010500@redhat.com> <20100719124847.0CDBBA005F@mail.linux-ag.de> <4C444E78.8030907@redhat.com> <20100719134558.A0CD2A005F@mail.linux-ag.de> <4C445A94.2050802@redhat.com> <20100719144750.334F2303001B@mail.linux-ag.de> <4C446942.6090907@redhat.com> <20100719152518.641BAB001A@mail.linux-ag.de> <4C446F20.4060106@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: Sebastian Hetze , kvm@vger.kernel.org To: Avi Kivity Return-path: Received: from ironport.linux-ag.com ([62.245.157.240]:54205 "EHLO ironport.linux-ag.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S935158Ab0GSPiR (ORCPT ); Mon, 19 Jul 2010 11:38:17 -0400 Received: from localhost (mail.linux-ag.de [62.245.157.206]) by mail.linux-ag.de (Postfix) with ESMTP id 41DBDB0016 for ; Mon, 19 Jul 2010 17:38:16 +0200 (CEST) Content-Disposition: inline In-Reply-To: <4C446F20.4060106@redhat.com> Sender: kvm-owner@vger.kernel.org List-ID: On Mon, Jul 19, 2010 at 06:28:32PM +0300, Avi Kivity wrote: > On 07/19/2010 06:23 PM, Sebastian Hetze wrote: >> >>> What's your hardware platform? EPT/NPT capable? Host kernel version? >>> >> Intel S5520HC Board with 2 Xeon CPU E5520, HT enabled >> 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 nx rdtscp lm constant_tsc arch_perfmon pebs bts rep_good >> xtopology nonstop_tsc aperfmperf pni dtes64 monitor ds_cpl vmx est tm2 >> ssse3 cx16 xtpr pdcm dca sse4_1 sse4_2 popcnt lahf_lm ida tpr_shadow >> vnmi flexpriority ept vpid >> >> (so yes, EPT is available) >> >> host kernel is vanilla 2.6.34 >> >> > > Well, EPT makes it unlikely that there's an mmu bug involved. > > Is the guest smp? Can you try UP? yes, the guest starts with -smp 6 Since the system is quite busy and the problem occurs only ever two weeks or so, UP is no option. > > Can you try 2.6.32.latest in the guest? This we can certainly do. Is 2.6.32.16 your recommendation or will any newer kernel do also?