From owner-freebsd-xen@FreeBSD.ORG Mon Feb 17 16:29:43 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 51201448 for ; Mon, 17 Feb 2014 16:29:43 +0000 (UTC) Received: from mail.tdx.com (mail.tdx.com [62.13.128.18]) by mx1.freebsd.org (Postfix) with ESMTP id 0F47D1449 for ; Mon, 17 Feb 2014 16:29:41 +0000 (UTC) Received: from Mail-PC.tdx.co.uk (storm.tdx.co.uk [62.13.130.251]) (authenticated bits=0) by mail.tdx.com (8.14.3/8.14.3/) with ESMTP id s1HGTbgd032749 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 17 Feb 2014 16:29:38 GMT Date: Mon, 17 Feb 2014 16:29:36 +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: <94A35E308ABE3947989C36EC@Mail-PC.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 (Win32) 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 16:29:43 -0000 --On 17 February 2014 16:56 +0100 Roger Pau Monn=C3=A9 = =20 wrote: > How many guests are you running on this host, and how many vCPUs has > each one assigned? Only 1 active guest (the FreeBSD one) - there are others on there, but=20 they're not running (so I'm hoping they don't count? :) > I don't think those modifications have any effect on the timer, but > could you try to recompile without the NO_ADAPTIE_* modifications and > without any device pass-through? Removed the NO_ADAPTIVE_ stuff from the Kernel - I'll have to do the PCI=20 passthrough removes later. > 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, with that patch applied, removing the NO_ADAPTIVE_* (but like I said -=20 still with the PCI passthroughs in place) I get: " panic: can't schedule timer on vCPU#0, interval: 112847ns " I'll increase NUM_TRIES, try that - then remove the PCI passthrough devices = and give that ago - that'll have to do those in a bit, and post when done. Thanks, -Karl