Date: Sun, 21 Oct 2018 23:27:42 +0700 From: Victor Sudakov <vas@mpeks.tomsk.su> To: "Rodney W. Grimes" <freebsd-rwg@pdx.rh.cn85.dnsmgr.net> Cc: Jason Barbier <kusuriya@serversave.us>, freebsd-virtualization@freebsd.org Subject: Re: bhyve uefi="csm" Message-ID: <20181021162742.GA10064@admin.sibptus.ru> In-Reply-To: <201810211601.w9LG1nFh005684@pdx.rh.CN85.dnsmgr.net> References: <AAC759B3-7E11-41E9-B7A4-4FE2E20F3E1D@serversave.us> <201810211601.w9LG1nFh005684@pdx.rh.CN85.dnsmgr.net>
next in thread | previous in thread | raw e-mail | index | archive | help
Rodney W. Grimes wrote: > > Can you tell us a bit about your set up, like are you using helper scripts like libvirt? > > To answer the question you asked when I run a vm with the CSM firmware it works for me. > > You should always be able to boot a vm that uses > and boots with the non CSM uefi firmware with the > CSM version of the firmware, failures may start > to show up if your booting something that is > either purely legacy, or efi aware but falls > back to csm because it didnt like something. If my goal were to boot FreeDOS in bhyve, would that be ever possible? > > The older ED2K uefi that we are using and > some of the hatchetry that was used to craft > its CSM are in a poor state and could use > some love. -- Victor Sudakov, VAS4-RIPE, VAS47-RIPN 2:5005/49@fidonet http://vas.tomsk.ru/
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20181021162742.GA10064>