From owner-freebsd-virtualization@freebsd.org Tue Aug 9 11:40:14 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 10735BB3A25 for ; Tue, 9 Aug 2016 11:40:14 +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 B6D1112EE for ; Tue, 9 Aug 2016 11:40:12 +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 u79Be23J052450 (version=TLSv1 cipher=ECDHE-RSA-AES256-SHA bits=256 verify=FAIL); Tue, 9 Aug 2016 12:40:02 +0100 (BST) (envelope-from matt.churchyard@userve.net) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=userve.net; s=201508; t=1470742803; bh=FDrIagus+/XqUU89C04jemUmDvIsblNB0v4KiIN0V1o=; h=From:To:CC:Subject:Date:References:In-Reply-To; b=kqK7H0eajwsmjHj/kh7j0K6tlpnlKeoHQMILn16E3IVSaQtb43NflAAzCbgM/FEn8 gJnLWrJuj6JFP+m8ImODFwAzAOPpFj7U8zGYJ/7FpBnklgJIT/CiGSwg85zu09zn/B ruJFhVKmWh0vp0hqYbvdjoxThPMV+RoNKJPvhkpE= 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; Tue, 9 Aug 2016 12:39:56 +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; Tue, 9 Aug 2016 12:39:56 +0100 From: Matt Churchyard To: Victor Sudakov CC: "freebsd-virtualization@freebsd.org" Subject: RE: Bhyve tests and findings Thread-Topic: Bhyve tests and findings Thread-Index: AQHR7kRdr3sAT9ONiUKmemTIvMbYHaA49GsAgAAiQQCAAG4VAIAAUWKAgAAKdYCAAAFIAIAGNT6AgAAx3aCAABVKgIAAKaBA Date: Tue, 9 Aug 2016 11:39:56 +0000 Message-ID: <6b97a900f4c446fd875b080780f6938b@SERVER.ad.usd-group.com> References: <20160804132810.Horde.PbxdxEormFX3MwsBMVBoRo7@mail.eeeit.de> <386acc93-afea-9c7e-bcb0-401d1f71fa1f@freebsd.org> <20160804205702.Horde.cclsReqAJZ4gP-yp7ySWYDW@mail.eeeit.de> <20160805013102.GA88553@admin.sibptus.transneft.ru> <20160805062219.GM148@e-new.0x20.net> <20160805065945.GA98590@admin.sibptus.transneft.ru> <20160805070420.GN148@e-new.0x20.net> <20160809055227.GA68689@admin.sibptus.transneft.ru> <008d6f674dd34becb787c2153029b0f4@SERVER.ad.usd-group.com> <20160809100707.GA78888@admin.sibptus.transneft.ru> In-Reply-To: <20160809100707.GA78888@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="koi8-r" 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: Tue, 09 Aug 2016 11:40:14 -0000 > > > > > >=20 > > > > > > uefi=3D"yes" > > > > > > graphics=3D"yes" > > > > >=20 > > > > > Dear Colleagues, > > > > >=20 > > > > > Can I enjoy and test all those nice "UEFI-GOP" features on a > > > > > 10.3-RELEASE system, or do I have to install CURRENT for that? > > > >=20 > > > > AFAIK you can checkout usr.sbin/bhyve from the 11 branch and compil= e it > > > > on 10.3. > > >=20 > > > I'm not sure how to compile something from a different branch without > > > compiling the whole world. make what? > >=20 > > For bhyve it's easy. Check out the sources, go to usr.sbin/bhyve and ru= n > >=20 > > make depend; make obj; make; make install.=20 >=20 > >Unfortunately, after all my efforts, with libvmmapi and bhyve compiled f= rom > >CURRENT sources: >=20 > >Aug 09 12:46:52: warning; UEFI graphics is only available in FreeBSD 11 = and newer > >Aug 09 12:46:52: booting >=20 > >Bummer! >=20 > It's possible that you do have a bhyve system with graphics support. Unfo= rtunately vm-bhyve isn't aimed at users who have manually merged changes, a= nd will blindly tell anyone that isn't running 11+ that they don't have gra= phics support.=20 >=20 > You have a couple of options - >=20 > 1) Run bhyve manually rather than using vm-bhyve > 2) Upgrade to the 11 beta > 3) Modify vm-bhyve to not automatically skip graphics support if the vers= ion is less than 11=20 >Aha! I've commented out the version check from vm-run, and now when >trying to install, I get: >=C1=D7=C7 09 17:01:05: initialising >=C1=D7=C7 09 17:01:05: [loader: none] >=C1=D7=C7 09 17:01:05: [uefi: yes] >=C1=D7=C7 09 17:01:05: [cpu: 1] >=C1=D7=C7 09 17:01:05: [memory: 1G] >=C1=D7=C7 09 17:01:05: [hostbridge: standard] >=C1=D7=C7 09 17:01:05: [com ports: com1] >=C1=D7=C7 09 17:01:05: [uuid: 093f9134-5e18-11e6-9502-5404a6b49a66] >=C1=D7=C7 09 17:01:05: [utctime: no] >=C1=D7=C7 09 17:01:05: [debug mode: no] >=C1=D7=C7 09 17:01:05: [primary disk: disk0.img] >=C1=D7=C7 09 17:01:05: [primary disk dev: file] >=C1=D7=C7 09 17:01:05: generated static mac 58:9c:fc:03:77:3b (based on 'w= in:0:1470736865:0') >=C1=D7=C7 09 17:01:05: initialising network device tap5 >=C1=D7=C7 09 17:01:05: adding tap5 -> bridge1 (isolated) >=C1=D7=C7 09 17:01:05: dynamically allocated port 5900 for vnc connections >=C1=D7=C7 09 17:01:05: booting >=C1=D7=C7 09 17:01:05: [bhyve options: -c 1 -m 1G -Hwl bootrom,/d02/vm/.c= onfig/BHYVE_UEFI.fd -U 093f9134-5e18-11e6-9502-5404a6b49a66] >=C1=D7=C7 09 17:01:05: [bhyve devices: -s 0,hostbridge -s 31,lpc -s 4:0,a= hci-hd,/d02/vm/win/disk0.img -s 5:0,virtio-net,tap5,mac=3D58:9c:fc:03:77:3b= -s >6:0,fbuf,tcp=3D0.0.0.0:5900,wait] >=C1=D7=C7 09 17:01:05: [bhyve console: -l com1,/dev/nmdm0A] >=C1=D7=C7 09 17:01:05: [bhyve iso device: -s 3:0,ahci-cd,/d02/vm/.iso/bhy= ve_win7_x64.iso] >=C1=D7=C7 09 17:01:05: starting bhyve (run 1) >=C1=D7=C7 09 17:01:05: bhyve exited with status 1 >=C1=D7=C7 09 17:01:05: destroying network device tap5 >=C1=D7=C7 09 17:01:05: stopped Looks like bhyve is exiting immediately. Easiest thing is to probably add d= ebug=3D"yes" to the guest config file then try and run it again. Any outpu= t from the bhyve command will be written to bhyve.log (note that's a differ= ent file to vm-bhyve.log). Matt