Date: Mon, 22 Oct 2018 10:14:08 -0700 (PDT) From: "Rodney W. Grimes" <freebsd-rwg@pdx.rh.CN85.dnsmgr.net> To: Victor Sudakov <vas@mpeks.tomsk.su> Cc: Jason Barbier <kusuriya@serversave.us>, freebsd-virtualization@freebsd.org Subject: Re: bhyve uefi="csm" Message-ID: <201810221714.w9MHE83d011516@pdx.rh.CN85.dnsmgr.net> In-Reply-To: <20181021162742.GA10064@admin.sibptus.ru>
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? Today no, due to the fact we do not have a ATA/legacy emulation, but rather only ahci disk emultaion, though I would be wrong on that point if FreeDOS has an ahci disk driver. This goal is on my "want" list for bhyve to be able to do. THere is a GSOC ata driver emulation that works some, but I do not think it can accomplish this task at this time. I do not know if the CSM code is up to this task either, but it should be. > > 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. > -- Rod Grimes rgrimes@freebsd.org
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201810221714.w9MHE83d011516>