From owner-freebsd-bugs@FreeBSD.ORG Fri Jun 21 14:40:00 2013 Return-Path: Delivered-To: freebsd-bugs@smarthost.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id F2436E70 for ; Fri, 21 Jun 2013 14:40:00 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:1900:2254:206c::16:87]) by mx1.freebsd.org (Postfix) with ESMTP id D933E12B3 for ; Fri, 21 Jun 2013 14:40:00 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.7/8.14.7) with ESMTP id r5LEe0xV039557 for ; Fri, 21 Jun 2013 14:40:00 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.7/8.14.7/Submit) id r5LEe0hY039556; Fri, 21 Jun 2013 14:40:00 GMT (envelope-from gnats) Resent-Date: Fri, 21 Jun 2013 14:40:00 GMT Resent-Message-Id: <201306211440.r5LEe0hY039556@freefall.freebsd.org> Resent-From: FreeBSD-gnats-submit@FreeBSD.org (GNATS Filer) Resent-To: freebsd-bugs@FreeBSD.org Resent-Reply-To: FreeBSD-gnats-submit@FreeBSD.org, Hugo Silva Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 1ECAADDD for ; Fri, 21 Jun 2013 14:37:06 +0000 (UTC) (envelope-from nobody@FreeBSD.org) Received: from oldred.freebsd.org (oldred.freebsd.org [8.8.178.121]) by mx1.freebsd.org (Postfix) with ESMTP id EB8921293 for ; Fri, 21 Jun 2013 14:37:05 +0000 (UTC) Received: from oldred.freebsd.org ([127.0.1.6]) by oldred.freebsd.org (8.14.5/8.14.7) with ESMTP id r5LEb5ii043510 for ; Fri, 21 Jun 2013 14:37:05 GMT (envelope-from nobody@oldred.freebsd.org) Received: (from nobody@localhost) by oldred.freebsd.org (8.14.5/8.14.5/Submit) id r5LEb4Uo043458; Fri, 21 Jun 2013 14:37:04 GMT (envelope-from nobody) Message-Id: <201306211437.r5LEb4Uo043458@oldred.freebsd.org> Date: Fri, 21 Jun 2013 14:37:04 GMT From: Hugo Silva To: freebsd-gnats-submit@FreeBSD.org X-Send-Pr-Version: www-3.1 Subject: kern/179814: mountroot fails with error=19 under Xen on 9-STABLE X-BeenThere: freebsd-bugs@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 21 Jun 2013 14:40:01 -0000 >Number: 179814 >Category: kern >Synopsis: mountroot fails with error=19 under Xen on 9-STABLE >Confidential: no >Severity: non-critical >Priority: low >Responsible: freebsd-bugs >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Fri Jun 21 14:40:00 UTC 2013 >Closed-Date: >Last-Modified: >Originator: Hugo Silva >Release: 9.1-STABLE >Organization: >Environment: >Description: Somewhere between r250634 and now there appears to have been a change that prevents a HVM+PV domU from mounting root: xn0: at device/vif/0 on xenbusb_front0 xn0: Ethernet address: 00:16:3e:b4:bf:05 xenbusb_back0: on xenstore0 xctrl0: on xenstore0 xbd0: 32768MB at device/vbd/768 on xenbusb_front0 xbd0: attaching as ada0 xbd1: 2048MB at device/vbd/832 on xenbusb_front0 xbd1: attaching as ada1 xbd2: 49152MB at device/vbd/5632 on xenbusb_front0 xbd2: attaching as ada2 xn0: backend features: SMP: AP CPU #1 Launched! Trying to mount root from ufs:/dev/ad0p2 [rw,noatime]... mountroot: waiting for device /dev/ad0p2 ... Mounting from ufs:/dev/ad0p2 failed with error 19. Loader variables: vfs.root.mountfrom=ufs:/dev/ad0p2 vfs.root.mountfrom.options=rw,noatime Manual root filesystem specification: : [options] Mount using filesystem and with the specified (optional) option list. eg. ufs:/dev/da0s1a zfs:tank cd9660:/dev/acd0 ro (which is equivalent to: mount -t cd9660 -o ro /dev/acd0 /) ? List valid disk boot devices . Yield 1 second (for background tasks) Abort manual input mountroot> I ran into this issue when updating the kernel+userland to mitigate against the new mmap exploit. Reverting to the old (r250634) kernel makes the problem go away. I tried to compile XENHVM instead of my custom HVMPV kernel just to rule out some custom option being the culprit, however unlikely in this scenario. The same thing happened (mountroot prompt) Somehow, this seems to be a xen specific problem, as a physical server was also updated to the same revision that caused the mountroot problem on the virtual machine, and it booted without problems. For the time being we're running with a patched r250634 kernel. >How-To-Repeat: Update your HVM+PV VM to today's -STABLE and reboot. >Fix: >Release-Note: >Audit-Trail: >Unformatted: