From owner-freebsd-xen@FreeBSD.ORG Mon Aug 27 11:30:09 2012 Return-Path: Delivered-To: freebsd-xen@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id AD271106568A for ; Mon, 27 Aug 2012 11:30:09 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 7E4D08FC1B for ; Mon, 27 Aug 2012 11:30:09 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.5/8.14.5) with ESMTP id q7RBU9e2091470 for ; Mon, 27 Aug 2012 11:30:09 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.5/8.14.5/Submit) id q7RBU8Da091467; Mon, 27 Aug 2012 11:30:09 GMT (envelope-from gnats) Date: Mon, 27 Aug 2012 11:30:09 GMT Message-Id: <201208271130.q7RBU8Da091467@freefall.freebsd.org> To: freebsd-xen@FreeBSD.org From: Mark Felder Cc: Subject: Re: kern/162677: [xen] FreeBSD not compatible with "Current Stable Xen" X-BeenThere: freebsd-xen@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Mark Felder 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, 27 Aug 2012 11:30:09 -0000 The following reply was made to PR kern/162677; it has been noted by GNATS. From: Mark Felder To: bug-followup@freebsd.org, karl@ionvz.com Cc: Subject: Re: kern/162677: [xen] FreeBSD not compatible with "Current Stable Xen" Date: Mon, 27 Aug 2012 06:29:29 -0500 This forum thread seems to indicate that it's mostly an Intel hardware issue. This pfsense thread seems to have more details: http://forum.pfsense.org/index.php?topic=3294.15 Xen must have worked around it because I can confirm that FreeBSD ISOs boot just fine on Xen 4.2 on Intel hardware.