From mboxrd@z Thu Jan 1 00:00:00 1970 From: Keir Fraser Subject: Re: vmx status report against cset 14912 - 1 fixed issue, 4 old issues Date: Wed, 25 Apr 2007 10:34:15 +0100 Message-ID: References: <10EA09EFD8728347A513008B6B0DA77AA3EE2C@pdsmsx411.ccr.corp.intel.com> Mime-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <10EA09EFD8728347A513008B6B0DA77AA3EE2C@pdsmsx411.ccr.corp.intel.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: "Zhao, Yunfeng" , xen-devel@lists.xensource.com List-Id: xen-devel@lists.xenproject.org On 25/4/07 10:27, "Zhao, Yunfeng" wrote: >> To be clear: this is an unmodified RHEL4 release kernel, with *latest* > PV >> drivers from -unstable? Any idea if this issue is specific to the RHEL4 >> kernel, or can you reproduce with other kernels? Does it very > definitely >> seem to be specific to multiprocessor guests? > [Yunfeng] The guest was booted with a 2.16.16 smp kernel which we built > for PV test. It only happens on SMP HVM linux guest.I also saw the same > issue on some SLES SMP HVM guests with SLES release kernel and PV > drivers. It would be interesting to see what happens if the platform-pci interrupt is pinned strictly to vcpu0. So, what happens if you boot the guest with 'acpi=0'? Or, what about if you kill any irqbalance programs that are running after boot, then 'cat /proc/interrupts' to find the xen-platform-pci interrupt number (x) and then 'echo 1 >/proc/irq//smp_affinity'? I couldn't repro just with SpecJBB but it's quite possible the kernel build is really required to repro. Specjbb itself does very little I/O. -- Keir