From owner-freebsd-current@freebsd.org Sun Jul 9 16:13:58 2017 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 C14DAD900FD for ; Sun, 9 Jul 2017 16:13:58 +0000 (UTC) (envelope-from kaduk@mit.edu) Received: from dmz-mailsec-scanner-6.mit.edu (dmz-mailsec-scanner-6.mit.edu [18.7.68.35]) (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 6E745645A0 for ; Sun, 9 Jul 2017 16:13:57 +0000 (UTC) (envelope-from kaduk@mit.edu) X-AuditID: 12074423-dd5ff70000000c44-84-5962550d410d Received: from mailhub-auth-2.mit.edu ( [18.7.62.36]) (using TLS with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by dmz-mailsec-scanner-6.mit.edu (Symantec Messaging Gateway) with SMTP id 09.11.03140.D0552695; Sun, 9 Jul 2017 12:08:46 -0400 (EDT) Received: from outgoing.mit.edu (OUTGOING-AUTH-1.MIT.EDU [18.9.28.11]) by mailhub-auth-2.mit.edu (8.13.8/8.9.2) with ESMTP id v69G8jtj025135; Sun, 9 Jul 2017 12:08:45 -0400 Received: from kduck.kaduk.org (24-107-191-124.dhcp.stls.mo.charter.com [24.107.191.124]) (authenticated bits=56) (User authenticated as kaduk@ATHENA.MIT.EDU) by outgoing.mit.edu (8.13.8/8.12.4) with ESMTP id v69G8fcc004193 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Sun, 9 Jul 2017 12:08:44 -0400 Date: Sun, 9 Jul 2017 11:08:42 -0500 From: Benjamin Kaduk To: Boris Samorodov Cc: freebsd-current@FreeBSD.org Subject: Re: [bhyve] FreeBSD guest, Handbook, vmrun.sh Message-ID: <20170709160841.GN80947@kduck.kaduk.org> References: <20170709153718.GM80947@kduck.kaduk.org> <0d526def-9e14-078a-5933-ab97cd643e8c@passap.ru> <8ac4e8a3-35c9-0054-0e5f-c663b80fd97b@passap.ru> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <8ac4e8a3-35c9-0054-0e5f-c663b80fd97b@passap.ru> User-Agent: Mutt/1.7.1 (2016-10-04) X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFupjleLIzCtJLcpLzFFi42IRYrdT0eULTYo0WLja0uLvs/PMFnPefGBy YPKY8Wk+i8eTma/YApiiuGxSUnMyy1KL9O0SuDJm3utlLPjMWzHv/leWBsZ1XF2MnBwSAiYS J/dfYO1i5OIQEljMJHFg20VGkISQwAZGiaedbBCJK0wSW6YtYAVJsAioSBzd/x7MZhNQk1i/ 4hoziC0CFD9xfgM7iM0sIC/xa2sTkM3BISxgJtGyWRIkzAu07OLvHnaImWcZJa68eMQGkRCU ODnzCQtEr7rEn3mXmEF6mQWkJZb/44AZ2bx1NtgqTgFbiX+z1jKB2KICyhJ/D99jmcAoOAvJ pFlIJs1CmDQLyaQFjCyrGGVTcqt0cxMzc4pTk3WLkxPz8lKLdM30cjNL9FJTSjcxgoPaRXkH 48s+70OMAhyMSjy8C2QTI4VYE8uKK3MPMUpyMCmJ8or1JkQK8SXlp1RmJBZnxBeV5qQWH2KU 4GBWEuEts0mKFOJNSaysSi3Kh0lJc7AoifOKazRGCAmkJ5akZqemFqQWwWRlODiUJHhXBAM1 ChalpqdWpGXmlCCkmTg4QYbzAA0/8QHoFt7igsTc4sx0iPwpRl2OO30bvjAJseTl56VKifNK ggwSACnKKM2DmwNKRhLZ+2teMYoDvSXMyxcEVMUDTGRwk14BLWECWsJWlwCypCQRISXVwGiw u3T3ldWrtmto/jlnp8hVLtBYMflq+re3nTUL33Oy3vhR4WMmXBE2yXjDbCW2IM/jf2YbvD75 5MXkNM6M517rzC1idt3lV7xQ5a596+K5K75tjIcbeG34Tzazh8v8mn4zpLNTws/+/5dA86i4 my8Zr3xsClwlmnzytLRF/dzjl5l372BUTlBiKc5INNRiLipOBAD/atUeIQMAAA== X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.23 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: Sun, 09 Jul 2017 16:13:58 -0000 On Sun, Jul 09, 2017 at 06:58:09PM +0300, Boris Samorodov wrote: > 09.07.2017 18:48, Boris Samorodov пишет: > > 09.07.2017 18:37, Benjamin Kaduk пишет: > >> > >> Documentation looks okay, as -I is documented during > >> the install stage, and is not supposed to be needed during > >> normal operation. > >> > >> The quoted error message from vmrun.sh happens when it thinks you > >> need to install on the given filesystem image > >> (if [ $force_install -eq 1 -o $need_install -eq 1 ];) > >> so it might be worth checking that your guest.img contains a valid > >> FFS filesystem on it. (Hmm, maybe you used ZFS and vmrun.sh isn't > >> prepared to handle that?) > > > > Yes, I used AutoZFS installer function to install FreeBSD. > > ----- > % sudo mdconfig -f quest.img > mdo0 > > % gpart show md0 > => 40 16777136 md0 GPT (8.0G) > 40 1024 1 freebsd-boot (512K) > 1064 984 - free - (492K) > 2048 4194304 2 freebsd-swap (2.0G) > 4196352 12578816 3 freebsd-zfs (6.0G) > 16775168 2008 - free - (1.0M) > ----- > > So, that seems the same bug as at my previous email: > https://lists.freebsd.org/pipermail/freebsd-current/2017-July/066514.html Is it? I refer to this part of vmrun.sh: file -s ${first_diskdev} | grep "boot sector" > /dev/null rc=$? if [ $rc -ne 0 ]; then file -s ${first_diskdev} | grep ": Unix Fast File sys" > /dev/null rc=$? fi if [ $rc -ne 0 ]; then need_install=1 else need_install=0 fi Which is not expected to be particularly robust. (BTW, I think there is not agreement as to whether vmrun.sh should be used in general use, or alternate solutions for VM managemnet.) -Ben