Date: Wed, 20 Jan 2016 21:01:03 -0600 From: Adam Vande More <amvandemore@gmail.com> To: Sergey Manucharian <sm@ara-ler.com> Cc: FreeBSD virtualization <freebsd-virtualization@freebsd.org> Subject: Re: floppy image in bhyve Message-ID: <CA%2BtpaK09Ozij=euQba--1h_w-0Yp7AH9sOrhAjYMWPxeXDr8UA@mail.gmail.com> In-Reply-To: <20160121020649.GC24662@dendrobates.araler.com> References: <CAO7uigCAXueBupQkFeY%2BTSBMdE3Q_msFtYN5nQco7pT0n6_pvQ@mail.gmail.com> <569FCF63.5040808@freebsd.org> <20160120203158.GA4849@debian.ara-ler.com> <CALXRTbdk3XHL=BvJM-0gwwVA5X_Rh30f5_aDvaJGsm7Ye2WW-w@mail.gmail.com> <20160121020649.GC24662@dendrobates.araler.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, Jan 20, 2016 at 8:06 PM, Sergey Manucharian <sm@ara-ler.com> wrote: > Yes, that a good idea especially taking into account that I have many > variables. I'm trying to migrate Windows 7 on an encrypted volume from > VBox to bhyve. > Another option would be to migrate to GELI, possibly on a ZVOL if available. Then tie bhyve windows vm startup/shutdown scripts to unlock/lock device as needed. -- Adam
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CA%2BtpaK09Ozij=euQba--1h_w-0Yp7AH9sOrhAjYMWPxeXDr8UA>