On Fri, Nov 16, 2018 at 8:03 AM Warner Losh <i...@bsdimp.com> wrote: > > > > On Thu, Nov 15, 2018 at 12:10 PM Rebecca Cran <rebe...@bluestop.org> wrote: >> >> On Wednesday, 14 November 2018 19:56:56 MST Warner Losh wrote: >> >> > What is the ConOut evifar look like? We set serial when the UEFI env says >> > to do so. >> >> Booting with: >> >> sudo bhyve -A -P -c 2 -H -m 4G -s 0:0,hostbridge -s 31:0,lpc -s 2,ahci- >> cd,FreeBSD-12.0-BETA4-amd64-disc1.iso -s >> 29,fbuf,tcp=0.0.0.0:5900,w=800,h=600,wait -l bootrom,/usr/local/share/uefi- >> firmware/BHYVE_UEFI.fd -u vm5 >> >> dh in the shell shows: >> >> 7D: ConsoleOut SimpleTextOut GraphicsOutput(GraphicsOutput) >> PCIIO DevicePath(PciRoot (0x0)/Pci(0x1D,0x0)) >> >> 84: StdErr ConsoleOut ConsoleIn SimpleTextOut SimpleTextInEx SimpleTextIn >> DevicePath(t(115200,8,N,1)/VenVt100Plus()) >> >> 89: SimpleTextOut SimpleTextInEx SimpleTextIn DevicePath(Uart(115200,8,N,1)/ >> VenPcAnsi()) > > > If I read that right, then the ConOut variable first has the video device > listed, then the serial port (this wasn't the form I expected to see it in, > so I'm not sure thats the case). In either event, we should get console > output on both the serial and the video at least until the /etc/rc script > starts... > > Warner
Perhaps this is not a special case of FreeBSD guest, since the latest versions of FreeBSD are loaded normally in other UEFI systems (e.g Virtualbox, KVM). For example someone from CBSD Telegram chat reported a similar problem for OpenIndiana 2018 ( which uses FreeBSD loader however) in bhyve. Thus, perhaps the root of this problem should be sought in uefi-edk2-bhyve the package. Latest CBSD release (12.0.1) fixed this problem by disabling serial console. However, CBSD uses an alternative boot method for bhyve ( uefi-edk2-bhyve + reFIND ) _______________________________________________ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
