>At first glance this looks like a coreboot issue, so I would ask on >the coreboot mailing list. Also, you may wish to retry without the >q35 machine type as I'm not sure how well coreboot supports it. > >If you think it is a SeaBIOS issue, then please retry with native >SeaBIOS (ie, remove the -bios part of the command line).
Thank you for the reply. I since tried to use FILO as my payload instead of SeaBIOS and still have issues, so I agree it seems to be an issue with coreboot or my coreboot configuration. I have also tried the pc machine type and not setting any machine type in QEMU with no luck. I put up a post on the coreboot mailing list, so hopefully they can point me in the right direction. Thanks again. On Wed, Aug 12, 2015 at 4:05 PM, Kevin O'Connor <[email protected]> wrote: > On Wed, Aug 12, 2015 at 10:23:00AM -0700, Dustin Brazeau wrote: > > I'm attempting to use QEMU, coreboot and SeaBIOS to boot a live Fedora > > image. I have built a coreboot image with SeaBIOS as the payload. I can > get > > QEMU to boot all the way to the SeaBIOS's boot menu, but pressing F12 > > doesn't not take me to the boot menu list and then SeaBIOS continually > > prints out handle_02. > > > > Here is my qemu command line: > > qemu-system-i386 -M q35 -bios build/coreboot.rom -serial stdio -hda > > images/linux_hd.img -cdrom images/Fedora-Live-Workstation-x86_64-22-3.iso > > -m 512 > > At first glance this looks like a coreboot issue, so I would ask on > the coreboot mailing list. Also, you may wish to retry without the > q35 machine type as I'm not sure how well coreboot supports it. > > If you think it is a SeaBIOS issue, then please retry with native > SeaBIOS (ie, remove the -bios part of the command line). > > -Kevin >
_______________________________________________ SeaBIOS mailing list [email protected] http://www.seabios.org/mailman/listinfo/seabios
