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

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 q

interrupt 001E

On Sun, 17 Jan 2021 10:07:51 +0100, 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. Ah, sorry, the subject line. /Tomas

seg fault

Hi again, I seem to always get Segmentation fault (core dumped) in the Linux terminal after running QEMU. Is this normal, or some indication of something somewhere? /Tomas

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

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?

interrupt 001E

On Sun, 17 Jan 2021 11:52:19 +0100, Hi, Berto Furth wrote: > Can you try removing the -soundhw argument and see if that makes any > difference? No difference. I think disk sounds more likely, as there is no sound in these programs. /Tomas

interrupt 001E

Hi, On Sun, 17 Jan 2021 02:43:05 +0100, Berto Furth wrote: > Interrupt 0x1E seems to be related to "SYSTEM DATA - DISKETTE > PARAMETERS" according to Ralf Brown's interrupt list. Could a disk > drive be misconfigured? On Sun, 17 Jan 2021 11:52:19 +0100, Berto Furth wrote: > I'm afraid I don't rea

Question for debugging option

Hi developers, I am trying to capture input instructions through QEMU, I see on the manual: "-d in_asm" shows input assembly code for each compiled TB. Does the option still work when enabling KVM? Thanks, Duo Zhang

Re: Question for debugging option

No, it won't work with KVM. Thanks, Arnab On Mon, Jan 18, 2021 at 7:03 AM Duo Zhang wrote: > Hi developers, > > I am trying to capture input instructions through QEMU, I see on the > manual: "-d in_asm" shows input assembly code for each compiled TB. Does > the option still work when enabling K

Re: Question for debugging option

Hi Berto, Thanks for your suggestion. I will try it. Best, Duo On Mon, Jan 18, 2021 at 12:39 AM Berto Furth wrote: > Can you use gdb in conjunction with qemu (the -gdb dev option)? That still > works with kvm. > > Good luck! > > On Mon, 18 Jan 2021, at 12:32, Duo Zhang wrote: > > Hi developers

Re: Question for debugging option

Hi Arnab, Thanks for your help. If I wanna capture executed instructions, should I revise kernel KVM? or is there any other way? Thanks, Duo On Sun, Jan 17, 2021 at 9:53 PM Arnabjyoti Kalita wrote: > No, it won't work with KVM. > > Thanks, > Arnab > > On Mon, Jan 18, 2021 at 7:03 AM Duo Zhang