Date: Thu, 7 Sep 2017 07:53:33 +1000 From: Jason Tubnor <jason@tubnor.net> To: tech-lists <tech-lists@zyxst.net> Cc: "freebsd-virtualization@freebsd.org" <freebsd-virtualization@freebsd.org>, freebsd-current@freebsd.org Subject: Re: openbsd 6.0 or 6.1 guest on freebsd-12 (current) host Message-ID: <CACLnyCJNwRjHaQHS5b-uik0HW=mQXVS%2BC7vtWpvr1eQnMBcsJQ@mail.gmail.com> In-Reply-To: <c7446a9d-2ba9-7973-c2ed-0502b444215a@zyxst.net> References: <d3ef585f-6cdb-6a0a-e19f-517210f12b2f@zyxst.net> <CACLnyCKNnYFZ5QaQR18Rcv3Ayy-GDThd405U=185hEaunXuj_Q@mail.gmail.com> <c7446a9d-2ba9-7973-c2ed-0502b444215a@zyxst.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On 6 September 2017 at 22:15, tech-lists <tech-lists@zyxst.net> wrote: > > > Have you encountered anything on openbsd in a bhyve that you've found > not to work? > > As Thomas mentioned, there is/was a bug with certain CPUs, but this was due to the strict checking of CPU features that OpenBSD introduced ( https://marc.info/?l=openbsd-misc&m=149136173520510&w=2). Peter explained the switch to get around that issue (-w). The only other thing is Jumbo frame support, but that is really down to limits in VirtIO and not really a show stopper and doesn't affect anything in production for us. Enjoy bhyve, it has been a drop in replacement for our individual ESXi instances and has been bulletproof, which is good as we have hypervisor hosts over 6 hour drives away! (Oh the uplift from 11.0 to 11.1 was done remotely without nuking the host). Cheers, Jason.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CACLnyCJNwRjHaQHS5b-uik0HW=mQXVS%2BC7vtWpvr1eQnMBcsJQ>