From owner-freebsd-current@freebsd.org Sun Jul 9 16:38:38 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 7ACF7D905D8 for ; Sun, 9 Jul 2017 16:38:38 +0000 (UTC) (envelope-from bsam@passap.ru) Received: from forward3h.cmail.yandex.net (forward3h.cmail.yandex.net [IPv6:2a02:6b8:0:f35::13]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "forwards.mail.yandex.net", Issuer "Yandex CA" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 36BA864D11; Sun, 9 Jul 2017 16:38:38 +0000 (UTC) (envelope-from bsam@passap.ru) Received: from smtp2j.mail.yandex.net (smtp2j.mail.yandex.net [IPv6:2a02:6b8:0:801::ac]) by forward3h.cmail.yandex.net (Yandex) with ESMTP id 42B1B20CB5; Sun, 9 Jul 2017 19:38:27 +0300 (MSK) Received: from smtp2j.mail.yandex.net (localhost.localdomain [127.0.0.1]) by smtp2j.mail.yandex.net (Yandex) with ESMTP id 8326F3EC0E93; Sun, 9 Jul 2017 19:38:25 +0300 (MSK) Received: by smtp2j.mail.yandex.net (nwsmtp/Yandex) with ESMTPSA id 00RDUqbno1-cPW0F73e; Sun, 09 Jul 2017 19:38:25 +0300 (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client certificate not present) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=passap.ru; s=mail; t=1499618305; bh=XKFtJDVj6N3lM4LWu/JwbOFGPXCU3jUAo4VQhSurMEE=; h=Subject:To:Cc:References:From:Message-ID:Date:In-Reply-To; b=By6+z87B3pnAdJVOiwsKU79m6WG2GmZzKcfOZQbpHX3f7RHpAkrGDdH8Ej4AbVlle KYq8ciJ2m2vdCq4acgUge7tsdez3mB8aLv9CestD9ku+SJgR7J/De7dK5k6dpwhCGE idsnMV3ztNnpK+2i35C3ZqbEZ129l+76VdJMutAM= Authentication-Results: smtp2j.mail.yandex.net; dkim=pass header.i=@passap.ru X-Yandex-Suid-Status: 1 0,1 0 Subject: Re: [bhyve] FreeBSD guest, Handbook, vmrun.sh To: Benjamin Kaduk Cc: freebsd-current@FreeBSD.org References: <20170709153718.GM80947@kduck.kaduk.org> <0d526def-9e14-078a-5933-ab97cd643e8c@passap.ru> <8ac4e8a3-35c9-0054-0e5f-c663b80fd97b@passap.ru> <20170709160841.GN80947@kduck.kaduk.org> From: Boris Samorodov Message-ID: <7b73ab2d-0f6f-f11a-b37f-23f148af8277@passap.ru> Date: Sun, 9 Jul 2017 19:38:25 +0300 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.2.1 MIME-Version: 1.0 In-Reply-To: <20170709160841.GN80947@kduck.kaduk.org> Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 8bit 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:38:38 -0000 09.07.2017 19:08, Benjamin Kaduk пишет: > 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.) OK, normal bhyveload/bhyve ended up at a successful boot. Benjamin, thank you for your comments and help! -- WBR, bsam