From owner-freebsd-current@freebsd.org Wed Sep 16 01:54:11 2015 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 3E3779CDB17 for ; Wed, 16 Sep 2015 01:54:11 +0000 (UTC) (envelope-from julian@freebsd.org) Received: from vps1.elischer.org (vps1.elischer.org [204.109.63.16]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 198AB13A3 for ; Wed, 16 Sep 2015 01:54:10 +0000 (UTC) (envelope-from julian@freebsd.org) Received: from Julian-MBP3.local (ppp121-45-224-161.lns20.per1.internode.on.net [121.45.224.161]) (authenticated bits=0) by vps1.elischer.org (8.15.2/8.15.2) with ESMTPSA id t8G1s0Ne070369 (version=TLSv1.2 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO) for ; Tue, 15 Sep 2015 18:54:03 -0700 (PDT) (envelope-from julian@freebsd.org) Subject: Re: nanoBSD boot problem (on USB stick or as a HD) To: freebsd-current@freebsd.org References: From: Julian Elischer Message-ID: <55F8CBB2.1080109@freebsd.org> Date: Wed, 16 Sep 2015 09:53:54 +0800 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:38.0) Gecko/20100101 Thunderbird/38.2.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 16 Sep 2015 01:54:11 -0000 On 9/15/15 5:31 PM, Stefano Garzarella wrote: > Hi all, > I created a nanoBSD image for my gsoc project (ptnetmap on bhyve). > > I would like to boot this image on USB stick or in the hypervisor as a HD. > I have some problem because if I set NANO_DRIVE="da0" (for USB boot) > in the nanoBSD configuration file, the boot from USB stick works well, > but when I try to boot the same image in the hypervisor as a HD, > I have the following mountroot error: you have to override vfs.root.mountfrom in the hypervisor's loader bhyveload. otherwise it looks at /etc/fstab in the root filesystem, and you can't have it work both ways.. one possibility is to use gpart label to describe the device. possibly it woudl hav ehte same result in both cases, but I don't know for sure that it works for root device.. you'd have to test. > > Trying to mount root from ufs:/dev/da0s1a [ro]... > mountroot: waiting for device /dev/da0s1a ... > Mounting from ufs:/dev/da0s1a failed with error 19. > > Loader variables: > vfs.root.mountfrom=ufs:/dev/da0s1a > vfs.root.mountfrom.options=ro > > mountroot> > > > At this point I need to manually specify "ufs:/dev/ad0s1a" to properly mount > the root. > > Can you help me? > There is some tricks to avoid this mountroot error? > > Thanks, > Stefano Garzarella > _______________________________________________ > freebsd-current@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" >