From owner-freebsd-virtualization@freebsd.org  Sun Feb  7 03:48:55 2016
Return-Path: <owner-freebsd-virtualization@freebsd.org>
Delivered-To: freebsd-virtualization@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 8385FA9E615
 for <freebsd-virtualization@mailman.ysv.freebsd.org>;
 Sun,  7 Feb 2016 03:48:55 +0000 (UTC)
 (envelope-from mgrooms@shrew.net)
Received: from mx1.shrew.net (mx1.shrew.net [38.97.5.131])
 (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
 (Client did not present a certificate)
 by mx1.freebsd.org (Postfix) with ESMTPS id 5C81F13A5
 for <freebsd-virtualization@freebsd.org>; Sun,  7 Feb 2016 03:48:54 +0000 (UTC)
 (envelope-from mgrooms@shrew.net)
Received: from mail.shrew.net (mail.shrew.prv [10.24.10.20])
 by mx1.shrew.net (8.14.7/8.14.7) with ESMTP id u173kAuZ095753
 for <freebsd-virtualization@freebsd.org>; Sat, 6 Feb 2016 21:46:10 -0600 (CST)
 (envelope-from mgrooms@shrew.net)
Received: from [10.22.200.30] (cpe-72-179-24-154.austin.res.rr.com
 [72.179.24.154])
 by mail.shrew.net (Postfix) with ESMTPSA id BE17E18BDCE
 for <freebsd-virtualization@freebsd.org>; Sat,  6 Feb 2016 21:46:04 -0600 (CST)
Subject: Re: Question about bhyve disk images
To: freebsd-virtualization@freebsd.org
References: <E97C216F-6808-44F3-8AF6-0D1F51BEB9A5@ultra-secure.de>
 <56B69A83.3080406@redbarn.org>
From: Matthew Grooms <mgrooms@shrew.net>
Message-ID: <56B6BE95.5000507@shrew.net>
Date: Sat, 6 Feb 2016 21:48:37 -0600
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:38.0) Gecko/20100101
 Thunderbird/38.5.1
MIME-Version: 1.0
In-Reply-To: <56B69A83.3080406@redbarn.org>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.4.3
 (mx1.shrew.net [10.24.10.10]); Sat, 06 Feb 2016 21:46:10 -0600 (CST)
X-BeenThere: freebsd-virtualization@freebsd.org
X-Mailman-Version: 2.1.20
Precedence: list
List-Id: "Discussion of various virtualization techniques FreeBSD supports."
 <freebsd-virtualization.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-virtualization>, 
 <mailto:freebsd-virtualization-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-virtualization/>
List-Post: <mailto:freebsd-virtualization@freebsd.org>
List-Help: <mailto:freebsd-virtualization-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-virtualization>, 
 <mailto:freebsd-virtualization-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sun, 07 Feb 2016 03:48:55 -0000

On 2/6/2016 7:14 PM, Paul Vixie wrote:
>
> Rainer Duffner wrote:
>> Hi,
>>
>> is it possible to increase the size of these images (after creation,
>> and while the guest OS is running)?
>
> there is no driver-layer signal to tell the guest OS that a drive just 
> got larger, so the guest OS would have to poll, or be told to sense.
>
> with freebsd 10 as the guest OS, i've been able to use growfs to make 
> it expand the the hog (last) file system on a virtual drive. but i did 
> it by shutting down the guest, growing the zvol, booting the guest, 
> and running growfs inside the guest. i havn't tried avoiding the 
> shutdown and reboot.
>

I'm not sure if bhyve reports the current backing file size as the 
virtual block device size after it's been increased. But if it does, 
this may be useful ...

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=204901

-Matthew