Date: Tue, 25 Oct 2016 09:38:20 -0600 From: "Dave Shariff Yadallee - System Administrator a.k.a. The Root of the Problem" <root@doctor.nl2k.ab.ca> To: Randy Terbush <randy@terbush.org> Cc: The Doctor <doctor@doctor.nl2k.ab.ca>, Matt Churchyard <matt.churchyard@userve.net>, "freebsd-virtualization@freebsd.org" <freebsd-virtualization@freebsd.org> Subject: Re: Windows 2016 Server Message-ID: <20161025153820.GA69757@doctor.nl2k.ab.ca> In-Reply-To: <CALmWkDamTgz4VJg5wX_s8JohfX_dRC26SDDGVQzmdCMjUtg%2B5g@mail.gmail.com> References: <20161021183120.GA21232@doctor.nl2k.ab.ca> <20161021190122.GA30602@doctor.nl2k.ab.ca> <alpine.BSF.2.20.1610212216310.22551@z.fncre.vasb> <0406d06f-aa1a-677c-775a-b09a3ebd3073@freebsd.org> <20161021222342.GA80184@doctor.nl2k.ab.ca> <33e8e02d845145918591d25196402491@SERVER.ad.usd-group.com> <20161025060637.GA20650@doctor.nl2k.ab.ca> <4cec0d5457ca45e1b2dee0b92055a439@SERVER.ad.usd-group.com> <20161025135818.GA28314@doctor.nl2k.ab.ca> <CALmWkDamTgz4VJg5wX_s8JohfX_dRC26SDDGVQzmdCMjUtg%2B5g@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, Oct 25, 2016 at 08:33:47AM -0600, Randy Terbush wrote: > On Tue, Oct 25, 2016 at 7:58 AM, The Doctor <doctor@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 network > > 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 install > > 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 something > > like iohyve/chyves/vm-bhyve/vmrc that handles all the raw bhyve commands > > 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. -- For effective Internet Etiquette and communications read http://catb.org/jargon/html/T/top-post.html, http://idallen.com/topposting.html & http://www.caliburn.nl/topposting.html
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20161025153820.GA69757>