On Tue, Apr 26, 2016 at 11:16:20PM +0200, Johannes Krottmayer wrote: > Am 2016-04-26 um 22:38 schrieb Kevin O'Connor: > [...] > > To report a SeaBIOS issue, the SeaBIOS log is needed. Please see > > http://www.seabios.org/Debugging#Diagnostic_information > > $ qemu-system-x86_64 -chardev stdio,id=seabios -device > isa-debugcon,iobase=0x402,chardev=seabios -bios > ../qemu/seabios-1.9.2/out/bios.bin -machine pc,accel=kvm -cpu core2duo > -m 2048 -smp 2 -hda win10.img -boot c > SeaBIOS (version 1.9.2-20160426_212753-zeus) [...] > Booting from Hard Disk... > Booting from 0000:7c00 > KVM internal error. Suberror: 1 > emulation failure
It appears the fault is occurring in the OS bootloader, not in the SeaBIOS code. [...] > >> QEMU output with SeaBIOS 1.9.0 and above: > > > > Did it work with some prior version of SeaBIOS? > > Yes. Tested it with the default version (1.7.2.2) of my distribution, > 1.8.0, 1.8.1 and version 1.8.2. It's odd that it works with a different SeaBIOS version. You could try bisecting between 1.8.0 and 1.9.2 to see what change the crash starts at - but be aware that random differences in the SeaBIOS binary might be tickling the underlying issue. You could also try reporting to the kvm list - they'll know how to interpret the cpu dump. -Kevin _______________________________________________ SeaBIOS mailing list SeaBIOS@seabios.org https://www.coreboot.org/mailman/listinfo/seabios
