From owner-freebsd-xen@FreeBSD.ORG Mon Feb 17 20:00:33 2014 Return-Path: Delivered-To: freebsd-xen@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 387CFE18 for ; Mon, 17 Feb 2014 20:00:33 +0000 (UTC) Received: from mail.tdx.com (mail.tdx.com [62.13.128.18]) by mx1.freebsd.org (Postfix) with ESMTP id EEB311A44 for ; Mon, 17 Feb 2014 20:00:32 +0000 (UTC) Received: from study64.tdx.co.uk (study64.tdx.co.uk [62.13.130.231]) (authenticated bits=0) by mail.tdx.com (8.14.3/8.14.3/) with ESMTP id s1HK0TD7055716 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 17 Feb 2014 20:00:30 GMT Date: Mon, 17 Feb 2014 20:00:28 +0000 From: Karl Pielorz To: =?UTF-8?Q?Roger_Pau_Monn=C3=A9?= , freebsd-xen@freebsd.org Subject: Re: FreeBSD 10-R 8 vCPU panics at boot under XenServer (on 8 'core' CPU) Message-ID: <1740E0FEE5963358491F4B37@study64.tdx.co.uk> In-Reply-To: <5302311E.2040700@citrix.com> References: <6A3B878077F7D071847052C0@Mail-PC.tdx.co.uk> <5302311E.2040700@citrix.com> X-Mailer: Mulberry/4.0.8 (Mac OS X) MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: quoted-printable Content-Disposition: inline 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, 17 Feb 2014 20:00:33 -0000 --On 17 February 2014 16:56:14 +0100 Roger Pau Monn=C3=A9=20 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=20 passthroughs in place at the moment). I had no idea what to set it to - so=20 I went for 600. With it set at 600 that same guest now boots Ok now every=20 time I've tried. But I did notice the whole 'SMP AP CPU #x Launched!' takes forever, and=20 varies a lot (e.g. one boot it took nearly 2 minutes to launch all CPU's=20 and continue). I removed the PCI passthroughs on that guest, and it now flies through the=20 AP launches. Unfortunately though I need the passthroughs :( I've passed through the onboard LSI 2308 SAS controller (mps), and a dual=20 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 also remembered I set 'hw.pci.enable_msi=3D1' and = 'hw.pci.enable_msix=3D0' in=20 /etc/sysctl.conf - someone else found that was necessary to use the LSI in=20 passthrough mode. Aside from the slow launches, do you think (as they work) it's going to=20 cause issues leaving those passthroughs active? Thanks, -Karl