Date: Wed, 10 Aug 2016 12:00:34 +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: <75264feddcff47bf920081457bbd3e7b@SERVER.ad.usd-group.com> In-Reply-To: <20160810030200.GA90959@admin.sibptus.transneft.ru> References: <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> <6b97a900f4c446fd875b080780f6938b@SERVER.ad.usd-group.com> <20160810030200.GA90959@admin.sibptus.transneft.ru>
next in thread | previous in thread | raw e-mail | index | archive | help
> > > > > > > > > > > > > uefi="yes" > > > > > > > graphics="yes" > > > > > > > > > > > > Dear Colleagues, > > > > > > > > > > > > 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? > > > > > > > > > > AFAIK you can checkout usr.sbin/bhyve from the 11 branch and > > > > > compile it on 10.3. > > > > > > > > I'm not sure how to compile something from a different branch > > > > without compiling the whole world. make what? > > > > > > For bhyve it's easy. Check out the sources, go to usr.sbin/bhyve > > > and run > > > > > > make depend; make obj; make; make install. > > > > >Unfortunately, after all my efforts, with libvmmapi and bhyve > > >compiled from CURRENT sources: > > > > >Aug 09 12:46:52: warning; UEFI graphics is only available in > > >FreeBSD 11 and newer Aug 09 12:46:52: booting > > > > >Bummer! > > > > It's possible that you do have a bhyve system with graphics support. Unfortunately vm-bhyve isn't aimed at users who have manually merged changes, and will blindly tell anyone that isn't running 11+ that they don't have graphics support. > > > > You have a couple of options - > > > > 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 > > version is less than 11 > > >Aha! I've commented out the version check from vm-run, and now when > >trying to install, I get: > > >ΑΧΗ 09 17:01:05: initialising > >ΑΧΗ 09 17:01:05: [loader: none] > >ΑΧΗ 09 17:01:05: [uefi: yes] > >ΑΧΗ 09 17:01:05: [cpu: 1] > >ΑΧΗ 09 17:01:05: [memory: 1G] > >ΑΧΗ 09 17:01:05: [hostbridge: standard] ΑΧΗ 09 17:01:05: [com > >ports: com1] ΑΧΗ 09 17:01:05: [uuid: > >093f9134-5e18-11e6-9502-5404a6b49a66] > >ΑΧΗ 09 17:01:05: [utctime: no] > >ΑΧΗ 09 17:01:05: [debug mode: no] > >ΑΧΗ 09 17:01:05: [primary disk: disk0.img] ΑΧΗ 09 17:01:05: > >[primary disk dev: file] ΑΧΗ 09 17:01:05: generated static mac > >58:9c:fc:03:77:3b (based on 'win:0:1470736865:0') ΑΧΗ 09 17:01:05: > >initialising network device tap5 ΑΧΗ 09 17:01:05: adding tap5 -> > >bridge1 (isolated) ΑΧΗ 09 17:01:05: dynamically allocated port 5900 > >for vnc connections ΑΧΗ 09 17:01:05: booting ΑΧΗ 09 17:01:05: [bhyve > >options: -c 1 -m 1G -Hwl bootrom,/d02/vm/.config/BHYVE_UEFI.fd -U > >093f9134-5e18-11e6-9502-5404a6b49a66] > >ΑΧΗ 09 17:01:05: [bhyve devices: -s 0,hostbridge -s 31,lpc -s > >4:0,ahci-hd,/d02/vm/win/disk0.img -s > >5:0,virtio-net,tap5,mac=58:9c:fc:03:77:3b -s > >>6:0,fbuf,tcp=0.0.0.0:5900,wait] ΑΧΗ 09 17:01:05: [bhyve console: -l > >com1,/dev/nmdm0A] ΑΧΗ 09 17:01:05: [bhyve iso device: -s > >3:0,ahci-cd,/d02/vm/.iso/bhyve_win7_x64.iso] > >ΑΧΗ 09 17:01:05: starting bhyve (run 1) ΑΧΗ 09 17:01:05: bhyve exited > >with status 1 ΑΧΗ 09 17:01:05: destroying network device tap5 ΑΧΗ 09 > >17:01:05: stopped > > Looks like bhyve is exiting immediately. Easiest thing is to probably add debug="yes" to the guest config file then try and run it again. Any output from the bhyve command will be written to bhyve.log (note that's a different file to vm-bhyve.log). > Tried that. root@vas:/d02/vm/win # file bhyve.log bhyve.log: empty root@vas:/d02/vm/win # more win.conf guest="windows" uefi="yes" graphics="yes" cpu=1 memory=1G network0_type="virtio-net" network0_switch="isolated" disk0_type="ahci-hd" disk0_name="disk0.img" debug="yes" uuid="093f9134-5e18-11e6-9502-5404a6b49a66" network0_mac="58:9c:fc:03:77:3b" root@vas:/d02/vm/win # >I have tried replicating manually all the options vm is passing to bhyve, like >bhyve -c 1 -m 1G -Hwl bootrom,/d02/vm/.config/BHYVE_UEFI.fd \ > -U 093f9134-5e18-11e6-9502-5404a6b49a66 \ >> -s 0,hostbridge -s 31,lpc -s 4:0,ahci-hd,/d02/vm/win/disk0.img \ > -s 5:0,virtio-net,tap5,mac=58:9c:fc:03:77:3b -s 6:0,fbuf,tcp=0.0.0.0:5900,wait \ > -l com1,stdio \ > -s 3:0,ahci-cd,/d02/vm/.iso/bhyve_win7_x64.iso > But bhyve just spits out the "usage" help (that's why it exits immediately). But I cannot find out what's incorrect with the options. You just need the vm name (win) on the end: # bhyve [options] vm-name Matt -- 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?75264feddcff47bf920081457bbd3e7b>