From owner-freebsd-virtualization@freebsd.org Mon Mar 18 15:08:45 2019 Return-Path: Delivered-To: freebsd-virtualization@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 7F66B154343E; Mon, 18 Mar 2019 15:08:45 +0000 (UTC) (envelope-from asomers@gmail.com) Received: from mail-lj1-f173.google.com (mail-lj1-f173.google.com [209.85.208.173]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "GTS CA 1O1" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 84FFD8CDDB; Mon, 18 Mar 2019 15:08:44 +0000 (UTC) (envelope-from asomers@gmail.com) Received: by mail-lj1-f173.google.com with SMTP id n18so12419001ljg.11; Mon, 18 Mar 2019 08:08:44 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to; bh=7M6FM8s1F/5jupaGN3K/AHKe4vjcbT2kz9laQUtEgbc=; b=WjJowxElhZjN/QbCtNAdqdHEsNm6z+9r/Robvt6NVNFWh4P2zxokDzQTMYOHU2cSQg HeyjSG8AgDHpNkCJ2ta0sbvoOpSwh+E0CA6g5Si/fP4ibtIlmglQQbUscG6qUgV2CL+W W+XXG5FjJoJrbqc5M3ODwpEG1/9PIxacPu9euQUX+Bplr0r3ok026OfVhQLRaKYG/nYa aSADLi0ohSmBSBPT0dfR6OUsLYrQ3LoMZaCVJPXpb02WoM5uFmsYuNxN96Z3abQJH3al 84pR36FPnecAt6gHfArTxYsfLVLkNJfDEUGxhVZA/nT4MKK6z0gy1yCzPl7bV6IMWbt2 mxMA== X-Gm-Message-State: APjAAAUHiuYb8/wyZfvbf2N2v7w2UPS0CMb7yV3Iz15Dat4NyGq/sa55 uSY+r/dLB5+BhWXcfaKXDMFC6xLBtB52mgKqxAy5+vCg X-Google-Smtp-Source: APXvYqw7yw6A62K2ODW0etZ5sF4yJwXtruA9nFGh+4l532y8OAAL1UBKnuWfsomSE/RSihW54N34j1Nka6Ng9Jgpfiw= X-Received: by 2002:a2e:8582:: with SMTP id b2mr6017265lji.24.1552921722331; Mon, 18 Mar 2019 08:08:42 -0700 (PDT) MIME-Version: 1.0 References: <20190318150404.GB91631@rpi3.zyxst.net> In-Reply-To: <20190318150404.GB91631@rpi3.zyxst.net> From: Alan Somers Date: Mon, 18 Mar 2019 09:08:31 -0600 Message-ID: Subject: Re: bhyve zfs resizing To: "freebsd-virtualization@freebsd.org" , FreeBSD Content-Type: text/plain; charset="UTF-8" X-Rspamd-Queue-Id: 84FFD8CDDB X-Spamd-Bar: --- Authentication-Results: mx1.freebsd.org; spf=pass (mx1.freebsd.org: domain of asomers@gmail.com designates 209.85.208.173 as permitted sender) smtp.mailfrom=asomers@gmail.com X-Spamd-Result: default: False [-3.98 / 15.00]; ARC_NA(0.00)[]; TO_DN_EQ_ADDR_SOME(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-0.996,0]; FROM_HAS_DN(0.00)[]; TO_DN_SOME(0.00)[]; R_SPF_ALLOW(-0.20)[+ip4:209.85.128.0/17]; TO_MATCH_ENVRCPT_ALL(0.00)[]; MIME_GOOD(-0.10)[text/plain]; RCVD_TLS_LAST(0.00)[]; DMARC_NA(0.00)[freebsd.org]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; IP_SCORE(-1.31)[ip: (-0.53), ipnet: 209.85.128.0/17(-3.88), asn: 15169(-2.09), country: US(-0.07)]; MX_GOOD(-0.01)[cached: alt3.gmail-smtp-in.l.google.com]; RCPT_COUNT_TWO(0.00)[2]; RCVD_IN_DNSWL_NONE(0.00)[173.208.85.209.list.dnswl.org : 127.0.5.0]; NEURAL_HAM_SHORT(-0.66)[-0.657,0]; FORGED_SENDER(0.30)[asomers@freebsd.org,asomers@gmail.com]; MIME_TRACE(0.00)[0:+]; R_DKIM_NA(0.00)[]; FREEMAIL_ENVFROM(0.00)[gmail.com]; ASN(0.00)[asn:15169, ipnet:209.85.128.0/17, country:US]; FROM_NEQ_ENVFROM(0.00)[asomers@freebsd.org,asomers@gmail.com]; RCVD_COUNT_TWO(0.00)[2] X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Discussion of various virtualization techniques FreeBSD supports." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 18 Mar 2019 15:08:45 -0000 On Mon, Mar 18, 2019 at 9:05 AM tech-lists wrote: > > Hi, > > Apart from the performance benefit as per the section for bhyve in the > handbook, can the size of the zfs-backed guest: > > 1. be resized from the host? > 2. does the guest need to be inactive? > 3. can linux guests (or even windows ones) be resized as well? > > thanks, > -- > J. Do you mean using a zvol as the backing store for a VM? If so, then: 1) Yes. You can just do "zfs set volsize" on the host. 2) In theory no, but the guest may need to be rebooted to notice the change. And I'm not sure if the current bhyve code will expose the new size without a reboot or not. 3) Sure. But after you expand the zvol (or before you shrink it), you'll have to change the size of the guest's filesystem using the guest's native tools. -Alan