From owner-freebsd-xen@FreeBSD.ORG Mon Feb 24 17:19:48 2014 Return-Path: Delivered-To: freebsd-xen@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 677696AA for ; Mon, 24 Feb 2014 17:19:48 +0000 (UTC) Received: from SMTP.CITRIX.COM (smtp.citrix.com [66.165.176.89]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 9B6591F66 for ; Mon, 24 Feb 2014 17:19:47 +0000 (UTC) X-IronPort-AV: E=Sophos;i="4.97,535,1389744000"; d="scan'208";a="105260857" Received: from accessns.citrite.net (HELO FTLPEX01CL02.citrite.net) ([10.9.154.239]) by FTLPIPO01.CITRIX.COM with ESMTP; 24 Feb 2014 17:19:45 +0000 Received: from [IPv6:::1] (10.80.16.47) by smtprelay.citrix.com (10.13.107.79) with Microsoft SMTP Server id 14.2.342.4; Mon, 24 Feb 2014 12:19:44 -0500 Message-ID: <530B7F2F.2010908@citrix.com> Date: Mon, 24 Feb 2014 18:19:43 +0100 From: =?UTF-8?B?Um9nZXIgUGF1IE1vbm7DqQ==?= User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:24.0) Gecko/20100101 Thunderbird/24.3.0 MIME-Version: 1.0 To: Karl Pielorz , Subject: Re: FreeBSD 10-R 8 vCPU panics at boot under XenServer (on 8 'core' CPU) References: <6A3B878077F7D071847052C0@Mail-PC.tdx.co.uk> <5302311E.2040700@citrix.com> <1740E0FEE5963358491F4B37@study64.tdx.co.uk> In-Reply-To: <1740E0FEE5963358491F4B37@study64.tdx.co.uk> X-Enigmail-Version: 1.6 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 8bit X-DLP: MIA2 X-BeenThere: freebsd-xen@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: Discussion of the freebsd port to xen - implementation and usage List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 24 Feb 2014 17:19:48 -0000 On 17/02/14 21:00, Karl Pielorz wrote: > > --On 17 February 2014 16:56:14 +0100 Roger Pau Monné > wrote: > >> In order to provide more debug info, could you apply the following patch: >> >> http://xenbits.xen.org/people/royger/0001-xen-debug-Xen-PV-timer.patch >> >> It will expand the panic message a little bit. Also, after applying the >> patch you can manually edit sys/dev/xen/timer/timer.c and increase >> NUM_RETRIES to see if that solves the problem. > > Ok, tried adjusting the NUM_RETRIES #define in that patch (I left the > PCI passthroughs in place at the moment). I had no idea what to set it > to - so I went for 600. With it set at 600 that same guest now boots Ok > now every time I've tried. > > But I did notice the whole 'SMP AP CPU #x Launched!' takes forever, and > varies a lot (e.g. one boot it took nearly 2 minutes to launch all CPU's > and continue). > > I removed the PCI passthroughs on that guest, and it now flies through > the AP launches. Unfortunately though I need the passthroughs :( > > I've passed through the onboard LSI 2308 SAS controller (mps), and a > dual port PCI-E Intel NIC (igb) - all the passthroughs work on FreeBSD > once it's booted - but obviously, not without causing the slow AP CPU > launches. I've passed through a dual port BCE card (Broadcom NetXtreme II BCM5709) without problems. As a test, could you try to only pass the nic or the SAS controller to see if we can figure out if this is specific to one of the devices? > I also remembered I set 'hw.pci.enable_msi=1' and 'hw.pci.enable_msix=0' > in /etc/sysctl.conf - someone else found that was necessary to use the > LSI in passthrough mode. > > Aside from the slow launches, do you think (as they work) it's going to > cause issues leaving those passthroughs active? Not sure, still have to figure out what's going on. Roger.