From owner-freebsd-virtualization@freebsd.org Fri Aug 5 08:22:54 2016 Return-Path: Delivered-To: freebsd-virtualization@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id AD9CEBAFF9A for ; Fri, 5 Aug 2016 08:22:54 +0000 (UTC) (envelope-from matt.churchyard@userve.net) Received: from smtp-outbound.userve.net (smtp-outbound.userve.net [217.196.1.22]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "*.userve.net", Issuer "Go Daddy Secure Certificate Authority - G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 47E251813 for ; Fri, 5 Aug 2016 08:22:54 +0000 (UTC) (envelope-from matt.churchyard@userve.net) Received: from owa.usd-group.com (owa.usd-group.com [217.196.1.2]) by smtp-outbound.userve.net (8.15.1/8.15.1) with ESMTPS id u758MlJV024484 (version=TLSv1 cipher=ECDHE-RSA-AES256-SHA bits=256 verify=FAIL); Fri, 5 Aug 2016 09:22:47 +0100 (BST) (envelope-from matt.churchyard@userve.net) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=userve.net; s=201508; t=1470385369; bh=UBbd7adAiV36lyk/eV1J8Wky2vTRmXcTCO6FIaAYz8Y=; h=From:To:Subject:Date:References:In-Reply-To; b=nPfSYyY1hzX+Wyg/Nl78eu/p4DRbcjC/jMTyKXWt2dZlaMnx28ezOoET110cCRTAp ivKAUoiIGEyiBbm7oKiAZAcjGmaqfrREmNBg7Ws5CJg3ngumvJHPe11h0swO4JX61D bwjSI3pH8K3gs6ShqDsZA21me34lSPLE7SvhA4qc= Received: from SERVER.ad.usd-group.com (192.168.0.1) by SERVER.ad.usd-group.com (192.168.0.1) with Microsoft SMTP Server (TLS) id 15.0.847.32; Fri, 5 Aug 2016 09:22:42 +0100 Received: from SERVER.ad.usd-group.com ([fe80::b19d:892a:6fc7:1c9]) by SERVER.ad.usd-group.com ([fe80::b19d:892a:6fc7:1c9%12]) with mapi id 15.00.0847.030; Fri, 5 Aug 2016 09:22:41 +0100 From: Matt Churchyard To: Victor Sudakov , "freebsd-virtualization@freebsd.org" Subject: RE: A couple of newbie questions Thread-Topic: A couple of newbie questions Thread-Index: AQHR7rpPT6M0ia2brUeMQ7dq7+Nn06A6AVmg Date: Fri, 5 Aug 2016 08:22:41 +0000 Message-ID: <1bbf6ac4afff44d5a73d2d4545a77c5d@SERVER.ad.usd-group.com> References: <20160805013959.GB88553@admin.sibptus.transneft.ru> In-Reply-To: <20160805013959.GB88553@admin.sibptus.transneft.ru> Accept-Language: en-GB, en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [192.168.0.10] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: "Discussion of various virtualization techniques FreeBSD supports." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 05 Aug 2016 08:22:54 -0000 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