From owner-freebsd-xen@FreeBSD.ORG  Mon Feb 17 14:44:14 2014
Return-Path: <owner-freebsd-xen@FreeBSD.ORG>
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 D38F8763
 for <freebsd-xen@freebsd.org>; Mon, 17 Feb 2014 14:44:14 +0000 (UTC)
Received: from mail.tdx.com (mail.tdx.com [62.13.128.18])
 by mx1.freebsd.org (Postfix) with ESMTP id 9AB3F1907
 for <freebsd-xen@freebsd.org>; Mon, 17 Feb 2014 14:44:13 +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 s1HEiCq2021605
 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO)
 for <freebsd-xen@freebsd.org>; Mon, 17 Feb 2014 14:44:12 GMT
Date: Mon, 17 Feb 2014 14:44:12 +0000
From: Karl Pielorz <kpielorz_lst@tdx.co.uk>
To: freebsd-xen@freebsd.org
Subject: FreeBSD 10-R 8 vCPU panics at boot under XenServer (on 8 'core' CPU)
Message-ID: <6A3B878077F7D071847052C0@Mail-PC.tdx.co.uk>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
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
 <freebsd-xen.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-xen>,
 <mailto:freebsd-xen-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-xen/>
List-Post: <mailto:freebsd-xen@freebsd.org>
List-Help: <mailto:freebsd-xen-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-xen>,
 <mailto:freebsd-xen-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 17 Feb 2014 14:44:14 -0000


Hi,

I've got a FreeBSD 10-R amd64 DomU guest I'm using under XenServer 6.2 
(SP1) - this was working fine (i.e. had been restarted many times - while I 
look at things like HAST).

I noticed the other day it was only set to use 4 vCPU's - so I increased 
this to 8 (the machine has an 4 Core, 8 Thread Xeon 1230v3 in it - which 
Xen see's as 8 CPU cores).

However, it won't boot reliably now:

"
...
SMP: AP CPU #5 Launched
panic: can't schedule timer
cpuid = 0
KDB: stack backtrace:
#0 0xffffffff808e7dd0 at kdb_backtrace+0x60
#1 0xffffffff808af8b5 at panic+0x155
#2 0xffffffff807a14dd at xentimer_et_start+0xed
#3 0xffffffff80d66d6d at loadtimer+0xfd
#4 0xffffffff80d657fd at handleevents+0x308
#5 0xffffffff80d65fc8 at timercb+0x308
#6 0xffffffff807a152d at xentimer_intr+0x4d
#7 0xffffffff80883e5b at intr_event_handle+0x9b
...
"

Less than 8 vCPU's seems to boot OK (e.g. 7) and 8 vCPU's has booted a 
couple of times (out of 30+ reboots).

The system is running GENERIC with:

  options   NO_ADAPTIVE_MUTEXES
  options   NO_ADAPTIVE_RWLOCKS
  options   NO_ADAPTIVE_SX

In addition XenServer is set to pass through the bare machine's LSI and two 
Intel NIC's (which it does - and are working, once FreeBSD is booted).

Any idea's?

-Karl