Hi, to be able to use the GOP instructions on FreeBSD 10.3 you'll need to merge r296103 [0]. If it's an AMD system it's a good idea to merge r297806 [1], too. Otherwise most Linux distros will panic at startup.
Regards, Yamagi 0: https://svnweb.freebsd.org/base?view=revision&revision=296103 1: https://svnweb.freebsd.org/base?view=revision&revision=297806 On Wed, 10 Aug 2016 20:36:34 +0700 Victor Sudakov <[email protected]> wrote: > Matt Churchyard wrote: > > > > >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 > > > > Sorry, I was being stupid. With the vm name on the end, it just exits > with error code 1 and without printing anytning. > > I have recompiled bhyve itself and the libvmmapi, maybe it's not > enough? The kernel module? It still remains that from 10.3 > > -- > Victor Sudakov, VAS4-RIPE, VAS47-RIPN > sip:[email protected] > _______________________________________________ > [email protected] mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-virtualization > To unsubscribe, send any mail to > "[email protected]" -- Homepage: www.yamagi.org XMPP: [email protected] GnuPG/GPG: 0xEFBCCBCB _______________________________________________ [email protected] mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-virtualization To unsubscribe, send any mail to "[email protected]"
