From owner-freebsd-xen@FreeBSD.ORG Mon Jun 4 20:40:13 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 1CF3D1065673 for ; Mon, 4 Jun 2012 20:40:13 +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 06EB48FC18 for ; Mon, 4 Jun 2012 20:40:13 +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 q54KeCoR024571 for ; Mon, 4 Jun 2012 20:40:12 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.5/8.14.5/Submit) id q54KeCGA024570; Mon, 4 Jun 2012 20:40:12 GMT (envelope-from gnats) Date: Mon, 4 Jun 2012 20:40:12 GMT Message-Id: <201206042040.q54KeCGA024570@freefall.freebsd.org> To: freebsd-xen@FreeBSD.org From: "Bill Cole" Cc: Subject: Re: kern/166174: [xen] Problems ROOT MOUNT ERROR < freebsd 8.3> X-BeenThere: freebsd-xen@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Bill Cole 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, 04 Jun 2012 20:40:13 -0000 The following reply was made to PR kern/166174; it has been noted by GNATS. From: "Bill Cole" To: bug-followup@FreeBSD.org, ilsujang@gmail.com Cc: Subject: Re: kern/166174: [xen] Problems ROOT MOUNT ERROR <freebsd 8.3> Date: Mon, 04 Jun 2012 16:29:08 -0400 This problem remains in 8.3-RELEASE and in the current RELENG_8_3. A kernel built for amd64 with the XENHVM config on 8.2p4 boots properly under XenServer 5.6 or 6.0, but the same config with 8.3 fails to detect and attach the xbd0 device for the root filesystem. The 8.3 GENERIC kernel boots normally as well, but without the Xen PV drivers. I have tried to get a XENHVM kernel working both by updating a 8.2p4 XENHVM system to RELENG_8_3 with its existing config and by installing a fresh 8.3-RELEASE/GENERIC system on a new VM and building XENHVM kernels on it: in all cases the failure is identical. I was able to update the 8.3-RELEASE/GENERIC system to a RELENG_8_3/GENERIC kernel and world from source without any trouble. I am reasonably experienced with custom-built kernel installs & I'm pretty sure that I've gone back over every "stupid sysadmin" failure mode and eliminated it. Device driver code is a realm for younger brains, but I am suspicious that the root cause is somewhere in the extensive changes made to src/sys/dev/xen/blkfront/blkfront.c and connected code ahead of the 8.3 release.