From nobody@FreeBSD.org  Fri Mar 16 03:19:12 2012
Return-Path: <nobody@FreeBSD.org>
Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52])
	by hub.freebsd.org (Postfix) with ESMTP id 6D60D106566B
	for <freebsd-gnats-submit@FreeBSD.org>; Fri, 16 Mar 2012 03:19:12 +0000 (UTC)
	(envelope-from nobody@FreeBSD.org)
Received: from red.freebsd.org (red.freebsd.org [IPv6:2001:4f8:fff6::22])
	by mx1.freebsd.org (Postfix) with ESMTP id 43F9B8FC12
	for <freebsd-gnats-submit@FreeBSD.org>; Fri, 16 Mar 2012 03:19:12 +0000 (UTC)
Received: from red.freebsd.org (localhost [127.0.0.1])
	by red.freebsd.org (8.14.4/8.14.4) with ESMTP id q2G3JCos022354
	for <freebsd-gnats-submit@FreeBSD.org>; Fri, 16 Mar 2012 03:19:12 GMT
	(envelope-from nobody@red.freebsd.org)
Received: (from nobody@localhost)
	by red.freebsd.org (8.14.4/8.14.4/Submit) id q2G3JCWv022353;
	Fri, 16 Mar 2012 03:19:12 GMT
	(envelope-from nobody)
Message-Id: <201203160319.q2G3JCWv022353@red.freebsd.org>
Date: Fri, 16 Mar 2012 03:19:12 GMT
From: "is, jang." <ilsujang@gmail.com>
To: freebsd-gnats-submit@FreeBSD.org
Subject: [XEN] Problems ROOT MOUNT ERROR <freebsd 8.3>
X-Send-Pr-Version: www-3.1
X-GNATS-Notify:

>Number:         166174
>Category:       kern
>Synopsis:       [xen] Problems ROOT MOUNT ERROR <freebsd 8.3>
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    freebsd-xen
>State:          open
>Quarter:        
>Keywords:       
>Date-Required:  
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Fri Mar 16 03:20:07 UTC 2012
>Closed-Date:    
>Last-Modified:  Tue Jun  5 16:10:14 UTC 2012
>Originator:     is,jang.
>Release:        freebsd 8.3.RC-1
>Organization:
>Environment:
>Description:
installed FreeBSD 8.3 RC1 from the installation CD on a Xenserver 6.0. This virtual machine runs without any problems.

When I try to boot a XEN kernel built from the standard configuration file 


No managed disk device shown by the ? command 

I also tried to boot the XEN kernel but also in this case the root device could not be mounted.
>How-To-Repeat:

>Fix:


>Release-Note:
>Audit-Trail:
Responsible-Changed-From-To: freebsd-bugs->freebsd-xen 
Responsible-Changed-By: linimon 
Responsible-Changed-When: Sat Mar 17 04:38:07 UTC 2012 
Responsible-Changed-Why:  
Over to maintainer(s). 

http://www.freebsd.org/cgi/query-pr.cgi?pr=166174 

From: moto kawasaki <moto@kawasaki3.org>
To: bug-followup@FreeBSD.org
Cc: ilsujang@gmail.com
Subject: Re: kern/166174: [xen] Problems ROOT MOUNT ERROR <freebsd 8.3>
Date: Tue, 01 May 2012 12:00:02 +0900 (JST)

 Hi,
 
 I'd report the similar case which I am facing.
 
 My envrionment is;
   XenServer 5.6 SP2
   FreeBSD 8.3-RELEASE (amd64) -- XENHVM kernel
 
 when booting this FreeBSD VM, its kernel cannot mount root disk.
 
 (case 1: ad0s1a, from /etc/fstab) ==========================
 
 
 ums0: <Endpoint1 Interrupt Pipe) on usbus0
 ums0: 3 buttons and [Z] coordinates ID=0
 Trying to mount root from ufs:/dev/ad0s1a
 ROOT MOUNT ERROR:
 If you have invalid mount options, reboot, and first try the following from
 the loader prompt:
 
      set ufs.root.mountfrom.options=rw
 
 and then remove invalid mount options from /ete/fstab.
 
 Loader variables:
 vfs.root.mountfrom=ufs:/dev/ad0s1a
 vfs.root.mountfrom.options=rw
 Manual root filesgstem specification:
   <fstype>:<device>  Mount <device> using filesystem <fstype>
                        eg. ufs:/dev/da0s1a
                        eg. cd9660:/deu/acd0
                        This is equivalent to: mount -t cd9660 /deu/acd0 /
   ? List valid disk boot devices
   <empty line> Abort manual input
 
 mountroot> _
 ============================================================
 
 (case 2: xbd, entered by hand just after the case 1) =======
 mountroot> ufs:/dev/xbd0s1a
 Trying to mount root from ufs:/dev/xbd0s1a
 ROOT MOUNT ERROR:
 If you have invalid mount options, reboot, and first try the following from
 the loader prompt:
 
      set ufs.root.mountfrom.options=rw
 
 and then remove invalid mount options from /ete/fstab.
 
 Loader variables:
 vfs.root.mountfrom=ufs:/dev/ad0s1a
 vfs.root.mountfrom.options=rw
 Manual root filesgstem specification:
   <fstype>:<device>  Mount <device> using filesystem <fstype>
                        eg. ufs:/dev/da0s1a
                        eg. cd9660:/deu/acd0
                        This is equivalent to: mount -t cd9660 /deu/acd0 /
   ? List valid disk boot devices
   <empty line> Abort manual input
 
 mountroot> _
 ============================================================
 
 
 
 HVMXEN kernel of FreeBSD 8.2-RELEASE-p6 works just fine in this
 environment.
 
 Also, I can try other "mountroot>" devices if you could tell me within
 a day or two.
 
 Thank you!!
 
 
 
 
 Best Regards,
 
 
 
 -- 
 moto kawasaki <moto@kawasaki3.org>

From: "Bill Cole" <fbsdbugs-20120604@billmail.scconsult.com>
To: bug-followup@FreeBSD.org, ilsujang@gmail.com
Cc:  
Subject: Re: kern/166174: [xen] Problems ROOT MOUNT ERROR &lt;freebsd 8.3&gt;
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.
 
 

From: Sean Bruno <seanbru@yahoo-inc.com>
To: bug-followup@FreeBSD.org, ilsujang@gmail.com
Cc:  
Subject: Re: kern/166174: [xen] Problems ROOT MOUNT ERROR &lt;freebsd
 8.3&gt;
Date: Mon, 04 Jun 2012 15:14:51 -0700

 I've got stable/8, stable/9 and -current XEN PV and XENHVM instances
 running in the freebsd cluster and have done so for quite some time.
 
 http://people.freebsd.org/~sbruno/ref8-xen32.txt
 http://people.freebsd.org/~sbruno/ref8-xen64.txt
 
 Does this help at all?
 
 Sean
 

From: "Bill Cole" <bill@scconsult.com>
To: bug-followup@FreeBSD.org, ilsujang@gmail.com
Cc:  
Subject: Re: kern/166174: [xen] Problems ROOT MOUNT ERROR &lt;freebsd 8.3&gt;
Date: Mon, 04 Jun 2012 19:30:14 -0400

 That appears to be more helpful than I would have expected.
 
 It looks like stable/8 includes r233791 of 2012-04-02 which is described 
 as:
 
     MFC Revision 233465
 
     Correct failure to attach the PV block front device on Citrix
     XenServer configurations that advertise the multi-page ring 
 extension,
     but only allow a single page of ring space.
 
 Sounds promising, and the small change (only to 
 sys/dev/xen/blkfront/blkfront.c) was not MFC'd into RELENG_8_3.
 
 Looks like my next step will be to switch my csup tag to RELENG_8

From: "Bill Cole" <fbsdbugs-20120604@billmail.scconsult.com>
To: bug-followup@FreeBSD.org, ilsujang@gmail.com
Cc:  
Subject: Re: kern/166174: [xen] Problems ROOT MOUNT ERROR &lt;freebsd 8.3&gt;
Date: Tue, 05 Jun 2012 12:02:29 -0400

 I have confirmed that this is fixed in stable/8. I ran csup with a 
 supfile pointing to the tag "RELENG_8" and followed the canonical 
 process to rebuild, install, and merge the world, kernel, and system 
 config with the same kernel config files, and everything worked 
 normally: the system attached the xbd device as ad0 and mounted it just 
 as in FreeBSD 8.2
 
>Unformatted:
