Date: Fri, 5 Aug 2016 08:22:41 +0000 From: Matt Churchyard <matt.churchyard@userve.net> To: Victor Sudakov <vas@mpeks.tomsk.su>, "freebsd-virtualization@freebsd.org" <freebsd-virtualization@freebsd.org> Subject: RE: A couple of newbie questions Message-ID: <1bbf6ac4afff44d5a73d2d4545a77c5d@SERVER.ad.usd-group.com> In-Reply-To: <20160805013959.GB88553@admin.sibptus.transneft.ru> References: <20160805013959.GB88553@admin.sibptus.transneft.ru>
next in thread | previous in thread | raw e-mail | index | archive | help
Colleagues, >I like bhyve very much, and have sucessfully run FreeBSD and Ubuntu >16.04 server in FreeBSD 10.3 bhyve, with vm-bhyve as a shell. >Now I am trying to boot Windows 7 but have not succeeded so far.=20 >However there are things I don't quite understand. A couple of questions, = if you allow. >1. Why is it that for some guest systems, there are two stages: first bhyv= eload or grub2-bhyve and then bhyve itself. And for UEFI systems there is >= only one stage. Does it mean that eventually bhyveload and grub2-bhyve wil= l become totally obsolete and the one-stage VM startup procedure >will beco= me the universal method? Originally the quickest and easiest way to get guests running on bhyve was = to load the guest into memory "manually", then run it. This started with ju= st bhyveload to load FreeBSD guests, then expanded to supporting various ot= her guests with grub-bhyve. UEFI was required to get Windows running (and m= akes bhyve act a bit more like other hypervisors) but took a lot of effort. UEFI does seem to be the best way to run most guests. Linux guests have alw= ays been a bit finicky unless they have grub2 installed, and the ability to= get remote access to the console makes things like a bhyve web frontend fe= asible. Bhyveload is still a pretty quick and useful way to run FreeBSD guests thou= gh, and I don't think that or grub-bhyve will go anywhere. >2. All this fbuf/VNC stuff looks cool, but I don't quite understand. You c= an see the guest OS's console in VNC, like the Windows desktop, or only >th= e UEFI shell, and then you have to access the guest OS via RDP/ssh etc ? With the frame buffer enabled you see the full guest OS in vnc, same as you= would in Virtualbox/VMWare/etc. Matt >TIA for explanations. >-- >Victor Sudakov, VAS4-RIPE, VAS47-RIPN >sip:sudakov@sibptus.tomsk.ru
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1bbf6ac4afff44d5a73d2d4545a77c5d>