Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 9 Aug 2016 11:39:56 +0000
From:      Matt Churchyard <matt.churchyard@userve.net>
To:        Victor Sudakov <vas@mpeks.tomsk.su>
Cc:        "freebsd-virtualization@freebsd.org" <freebsd-virtualization@freebsd.org>
Subject:   RE: Bhyve tests and findings
Message-ID:  <6b97a900f4c446fd875b080780f6938b@SERVER.ad.usd-group.com>
In-Reply-To: <20160809100707.GA78888@admin.sibptus.transneft.ru>
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>

next in thread | previous in thread | raw e-mail | index | archive | help
> > > > > >=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



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?6b97a900f4c446fd875b080780f6938b>