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 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. _______________________________________________ freebsd-virtualization@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-virtualization To unsubscribe, send any mail to "freebsd-virtualization-unsubscr...@freebsd.org"
