From owner-freebsd-virtualization@FreeBSD.ORG  Tue Jan 13 22:16:21 2015
Return-Path: <owner-freebsd-virtualization@FreeBSD.ORG>
Delivered-To: freebsd-virtualization@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115])
 (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by hub.freebsd.org (Postfix) with ESMTPS id A2129844;
 Tue, 13 Jan 2015 22:16:21 +0000 (UTC)
Received: from mail-qg0-x235.google.com (mail-qg0-x235.google.com
 [IPv6:2607:f8b0:400d:c04::235])
 (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits))
 (Client CN "smtp.gmail.com",
 Issuer "Google Internet Authority G2" (verified OK))
 by mx1.freebsd.org (Postfix) with ESMTPS id 62B223DA;
 Tue, 13 Jan 2015 22:16:21 +0000 (UTC)
Received: by mail-qg0-f53.google.com with SMTP id l89so4451438qgf.12;
 Tue, 13 Jan 2015 14:16:20 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
 h=mime-version:in-reply-to:references:date:message-id:subject:from:to
 :cc:content-type;
 bh=SpHbalUvXClPxHt0e7Zei7ItsSfb01WroY8weZCLML0=;
 b=e2iq4uK32OE5tRzMctILJnsDmg9vpa+oe+GAo0SMFJx1nf0tBV7lDJTktng4cIou0E
 /G8gckfdxVGo458nq+wfClanogcsdvtbiGQ+osMWwFzSjHIWKOzfwvk0/qfAcNDo+m5a
 10/sRobDodPSmUfcPiiTv+E2muPeh09FPJrCwcYDMcuCSK4/PHVfYddRMa0GxS4+n6W/
 rh7nRtUkZ6ZX+RekK2m9vaIpfBBE6mxkp98qT6XQe6NyeOT1v19fDD36J68fUGXYMoo6
 UMTk5iktAiv/wg2SgpXDp9DhGI5u+RX7URUo7SyeZfvl8cWfucPqlZjNEXKsTqzwaeHj
 7WIQ==
MIME-Version: 1.0
X-Received: by 10.229.211.193 with SMTP id gp1mr1493755qcb.19.1421187378837;
 Tue, 13 Jan 2015 14:16:18 -0800 (PST)
Received: by 10.140.96.13 with HTTP; Tue, 13 Jan 2015 14:16:18 -0800 (PST)
Received: by 10.140.96.13 with HTTP; Tue, 13 Jan 2015 14:16:18 -0800 (PST)
In-Reply-To: <54B5925F.8010308@freebsd.org>
References: <CAO8hVirsEttWhoPTQwvx6oy054Mk8idhDgUSLcsAMnsbgNXSSw@mail.gmail.com>
 <54B5925F.8010308@freebsd.org>
Date: Tue, 13 Jan 2015 14:16:18 -0800
Message-ID: <CAO8hVirb+xhno+PEtmt0NEOjAYFeBSUXMUuK7GFVrksiWEr93A@mail.gmail.com>
Subject: Re: Attaching block devices to a VM in bhyve
From: Jonathan Wong <jon.the.wong@gmail.com>
To: Allan Jude <allanjude@freebsd.org>
Content-Type: text/plain; charset=UTF-8
X-Content-Filtered-By: Mailman/MimeDel 2.1.18-1
Cc: freebsd-virtualization@freebsd.org
X-BeenThere: freebsd-virtualization@freebsd.org
X-Mailman-Version: 2.1.18-1
Precedence: list
List-Id: "Discussion of various virtualization techniques FreeBSD supports."
 <freebsd-virtualization.freebsd.org>
List-Unsubscribe: <http://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: <http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization>, 
 <mailto:freebsd-virtualization-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 13 Jan 2015 22:16:21 -0000

Thanks. Do you think it would be a hard thing to add in to bhyve or is it
related to something that's already being worked on?

Thanks,
Jon
On Jan 13, 2015 1:47 PM, "Allan Jude" <allanjude@freebsd.org> wrote:

> On 2015-01-13 16:45, Jonathan Wong wrote:
> > Hi.
> >
> > I was looking around and it seems is possible to attach zvols to a bhyve
> > vm, at least according to the vmrc script. Is it possible to attach a
> block
> > device to a VM after it has been launched?
> >
> > Thanks,
> > Jon
> > _______________________________________________
> > freebsd-virtualization@freebsd.org mailing list
> > http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization
> > To unsubscribe, send any mail to "
> freebsd-virtualization-unsubscribe@freebsd.org"
> >
>
> You can attach a block device, just use the path to the device in the
> place of a filename, same way you do with a zvol.
>
> However, it is not currently possible to attach a block device after
> bhyve has started.
>
> --
> Allan Jude
>
>