Re: When qemu starts kernel image (given by -kernel option), d eos it initialize CPU registers like firmwares and bootloaders do before kernel loading?

[Berto Furth]

Hi Tomas,

I'm afraid I don't really know what's happening (hopefully someone else will!). 
I did a bit of a search and I see that DOSBox users seem to get this style of 
error because of problems with the sound card. Can you try removing the 
-soundhw argument and see if that makes any difference?

In regards to the Segmentation Fault, I'm afraid that's something that's quite 
difficult to troubleshoot. If you wanted to do further troubleshooting you'd 
need to compile QEMU from the source code and then run a core analysis tool 
like "gdb" to get an idea of what's going on.

Again, I guess all I can suggest is perhaps seeing if you can remove the 
soundhw or if possible change the soundhw parameter. (Try -soundhw help" to see 
what other options are available.)

Good luck!

On Sun, 17 Jan 2021, at 20:07, Tomas By wrote:
> On Sun, 17 Jan 2021 02:43:05 +0100, Berto Furth wrote:
> > Is this related to the same "-kernel" question or is this a new topic?
> 
> It is probably `new,' as I do not know what other question you mean.
> 
> 
> > Can you post the complete command line and parameters you're using to start 
> > QEMU?
> 
> #!/bin/sh
> qemu-system-i386 -m 16 -k en-us -rtc base=localtime -soundhw sb16,adlib 
> -device cirrus-vga -display gtk -drive 
> file=dos.img,format=raw,index=0,media=disk -drive 
> file=fat:rw:disk/,format=raw -boot order=c
> 
> ("disk" is a sub-directory of the one from which I start it.)
> 
> 
> > Interrupt 0x1E seems to be related to "SYSTEM DATA - DISKETTE PARAMETERS" 
> > according to Ralf Brown's interrupt list. Could a disk drive be 
> > misconfigured?
> 
> You tell me?
> 
> /Tomas
> 
>