From owner-freebsd-xen@FreeBSD.ORG  Sat Dec 28 16:28:05 2013
Return-Path: <owner-freebsd-xen@FreeBSD.ORG>
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 D26F96E1
 for <freebsd-xen@freebsd.org>; Sat, 28 Dec 2013 16:28:05 +0000 (UTC)
Received: from mail.tdx.com (mail.tdx.com [62.13.128.18])
 by mx1.freebsd.org (Postfix) with ESMTP id 9961F1833
 for <freebsd-xen@freebsd.org>; Sat, 28 Dec 2013 16:28:05 +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 rBSGOkVh056199
 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO)
 for <freebsd-xen@freebsd.org>; Sat, 28 Dec 2013 16:24:46 GMT
Date: Sat, 28 Dec 2013 16:24:46 +0000
From: Karl Pielorz <kpielorz_lst@tdx.co.uk>
To: freebsd-xen@freebsd.org
Subject: Panic booting with FreeBSD 10 r259073 under XenServer 6.2
Message-ID: <DAADDDF63FAE63733D4E4ED3@study64.tdx.co.uk>
X-Mailer: Mulberry/4.0.8 (Mac OS X)
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: Sat, 28 Dec 2013 16:28:05 -0000


Hi,

I just updated a Xen guest here (I'm running FreeBSD under XenServer 6.2 on 
an Intel E3 based machine).

I went from 9.2-STABLE to 10 'stable' (i.e. I just checked out 
base/stable/10 - and built it).

svn info shows it's r259073.

The build / install all went OK - but booting the new kernel for the first 
time (GENERIC) I get the following panic:

"
Netvsc initializing... SMP: AP CPU #7 Launched!
panic: can't schedule timer
cpuid = 0
KDB: stack backtrace:
#0 0xffffffff808e7d30 at kdb_backtrace+0x60
#1 0xffffffff808af815 at panic+0x155
#2 0xffffffff807a13fd at xentimer_et_start+0xed
#3 0xffffffff80d66c2d at loadtimer+0xfd
#4 0xffffffff80d656bd at handleevents+0x2dd
#5 0xffffffff80d65e88 at timercb+0x308
#6 0xffffffff807a144d at xentimer_intr+0x4d
#7 0xffffffff80883dbb at intr_event_handle+0x9b
#8 0xffffffff80d8d088 at intr_execute_handlers+0x48
#9 0xffffffff80d967c9 at xen_intr_handle_upcall+0x159
#10 0xffffffff80c75f6c at Xxen_intr_upcall+0x8c
#11 0xffffffff80861158 at mi_startup+0x118
#12 0xffffffff802d3ddc at btext+0x2c
"

I know there's been a flurry of Xen patches submitted to the list recently 
- but I'm playing catchup with mail at the moment. Is the above a known 
issue? / Any suggestions?

Thanks,

-Karl