From owner-freebsd-virtualization@FreeBSD.ORG Mon Sep 9 10:28:26 2013 Return-Path: Delivered-To: freebsd-virtualization@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 ESMTP id 946FE5C3 for ; Mon, 9 Sep 2013 10:28:26 +0000 (UTC) (envelope-from kpielorz_lst@tdx.co.uk) Received: from mail.tdx.com (mail.tdx.com [62.13.128.18]) by mx1.freebsd.org (Postfix) with ESMTP id 5DD46267E for ; Mon, 9 Sep 2013 10:28:26 +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 r89ASOkb065173 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Mon, 9 Sep 2013 11:28:25 +0100 (BST) Date: Mon, 09 Sep 2013 11:28:24 +0100 From: Karl Pielorz To: freebsd-virtualization@freebsd.org Subject: Trying Hyper-V support from the svn project source - panic booting kernel? Message-ID: 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-virtualization@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "Discussion of various virtualization techniques FreeBSD supports." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 09 Sep 2013 10:28:26 -0000 Hi, I'm trying to build a Hyper-V aware kernel/system from the SVN source at svn://svn.freebsd.org/base/projects/hyperv (r254955) I got the world compiled, and the new Hyper-V supporting kernel installed, went to boot to single user mode, and get the following panic: " Timecounter "Hyper-V" frequency 10000000 Hz quality 10000000 panic: acquiring blockable sleep lock with spinlock or critical section held (sleep mutex) 4 Bucket " /usr/src/sys/vm/uma-dbg.c:212 cpuid = 0 KDB: enter: panic [ thread pid 0 tid 100000 ] Stopped at kdb_enter+0x3e: movq $0, kdb_why db> " This is under Hyper-V 2012. Any pointers? Is this a known issue? Thanks, -Karl