On Tue, Oct 25, 2016 at 9:38 AM, Dave Shariff Yadallee - System
Administrator a.k.a. The Root of the Problem <r...@doctor.nl2k.ab.ca> wrote:
> On Tue, Oct 25, 2016 at 08:33:47AM -0600, Randy Terbush wrote:
> > On Tue, Oct 25, 2016 at 7:58 AM, The Doctor <doc...@doctor.nl2k.ab.ca>
> > wrote:
> > > On Tue, Oct 25, 2016 at 09:20:28AM +0000, Matt Churchyard wrote:
> > >
> > > > One other issue is that Windows doesn't support the virtio-net
> > > device by default. The easiest way to get this working is to boot the
> > > guest with the virtio driver ISO attached instead of the Windows
> > > disk (once Windows is installed and working). You can then install the
> > > driver for the network interface from the CD using the VNC console.
> > > >
> > > > Depending on what you are doing you may find it easier to use
> > > like iohyve/chyves/vm-bhyve/vmrc that handles all the raw bhyve
> > > for you.
> > > >
> > > > Matt
> > >
> > > I will look into the iohyve , saw that last night.
> > >
> > > Does this also apply to UEFU BSDs / Linuxes ?
> > >
> > ???Just to chime in quickly on this thread... I am a big fan of
> vm-bhyve. It
> > has made it much easier to sort bhyve out in general and get through some
> > of these new options for supported guests.
> > Regarding Linux and UEFI, much of this also applies there. I've
> > successfully installed a LinuxMint guest. I will offer that after the
> > install, the boot process hung at the EFI. After exiting from the Shell>
> > prompt that eventually appears, it is possible to navigate the UEFI bios
> > settings to pick a bootable device. Only after rerunning 'grub2-install'
> > was I able to have a Linux guest that would boot without fiddling.
> > ???
> Let me give you my setup.
> No Zpool here.
> I am running FreeBSD 11 UEFI on x86_64.
> I have set up some non-UEFI guest successfull ,
> Fedora, Centos and Ubuntu.
> If it the UEFI part using a non-zpool environment
> that I am trying to wrap my head around.
> Smilir to Windows, I did install Fedora using
> UEFI but then
> could not go to the
> second stage, i.e. booting into the VM.
> Hence I do need to understand how to this with my environment using
> purely bhyve.
As mentioned, I'm using vm-bhyve to insulating me from the learning curve
of "pure bhyve". https://github.com/churchers/vm-bhyve
A few more details about my setup.
FreeBSD 11-stable (reguired for vnc graphics to work with UEFI guests)
Relevant installed packages:
While vm-bhyve is running in a zpool, the guests are using disk image
The following template allowed me to install LinuxMint through graphic VNC
vm create -t mint -s 30G mint
vm install mint linuxmint-18-cinnamon-64bit.iso (32bit would not install
as a UEFI guest)
vm list (shows running bhyve guests and indicates the IP and port that VNC
is running on for this guest)
Top-level listing of the vm zpool shows the layout which includes a
.template and .iso directory to collect your configs and install isos. Nice
[root: /vm]# ls -l
drwxr-xr-x 2 root wheel 5 Jul 20 10:01 .config
drwxr-xr-x 2 root wheel 10 Oct 24 12:10 .iso
drwxr-xr-x 2 root wheel 17 Oct 24 11:56 .templates
drwxr-xr-x 2 root wheel 8 Oct 3 21:41 kali
drwxr-xr-x 2 root wheel 6 Oct 2 18:13 macos
drwxr-xr-x 2 root wheel 8 Oct 25 05:37 mint
drwxr-xr-x 2 root wheel 7 Oct 22 15:31 win2012
drwxr-xr-x 2 root wheel 5 Oct 10 16:58 winapp
(NOTE: still trying to get a working MacOS guest running...)
firstname.lastname@example.org mailing list
To unsubscribe, send any mail to