Hello community,
I would like to ask for some advices on debugging a weird problem. The
setup is a qemu version is qemu-4.2.0-rc3 and kernel version
is 4.15.0-72-generic and distro is ubuntu 18.04. And the symptom is windows
stuck and cannot boot into system.
After some debugging, I observe
Hi,
I found my machine to be as to be similar to one of the stm32
implementations but in the list of machines which one to select?
BR.
Abhijeet.
On Thu, 4 Nov, 2021, 13:10 abhijeet inamdar,
wrote:
> Can I know exactly which board is it?! Would be helpful for me to look
> into.
>
>
> BR.
>
Can I know exactly which board is it?! Would be helpful for me to look into.
BR.
Abhijeet.
On Thu, 4 Nov, 2021, 12:15 Peter Maydell, wrote:
> On Wed, 3 Nov 2021 at 14:04, abhijeet inamdar
> wrote:
> > In a machine definition can there be a two different "cpu-type"
> > ( say ARM M or A or
On Wed, 3 Nov 2021 at 14:04, abhijeet inamdar
wrote:
> In a machine definition can there be a two different "cpu-type"
> ( say ARM M or A or R)that can be emulated ? (if it make sense)
Currently a machine can have multiple CPUs as long as
they are from the same guest architecture. So you can
Hi,
In a machine definition can there be a two different "cpu-type" ( say ARM M
or A or R)that can be emulated ? (if it make sense).
BR.
Abhijeet.
On Tue, 2 Nov, 2021, 15:49 Peter Maydell, wrote:
> On Tue, 2 Nov 2021 at 14:39, abhijeet inamdar
> wrote:
> >
> > Can you elaborate the Testing
On Tue, 2 Nov 2021 at 14:39, abhijeet inamdar
wrote:
>
> Can you elaborate the Testing point (3) as I have never done any unit test so.
Look at some of the existing tests like the one I suggest,
write tests that do that kind of thing. "Unit test" here
just means "this is a test case that tests
Can you elaborate the Testing point (3) as I have never done any unit test
so.
I have some general questions like the Ubuntu version I'm using is 16.04
LTS so for the latest QEMU will it be compatible? and for the debug is the
real hardware(board) required or just can make happen within software?
On Tue, 2 Nov 2021 at 13:15, abhijeet inamdar
wrote:
>
> Hi,
>
> I have a hardware which I want to emulate on QEMU based on arm Cortex M3. I
> tried to follow the examples like mps2 or stellaris.
>
> I'm finding it really hard to figure out how can I test the
> devices/peripherals I add to the
Hi,
I have a hardware which I want to emulate on QEMU based on arm Cortex M3. I
tried to follow the examples like mps2 or stellaris.
I'm finding it really hard to figure out how can I test the
devices/peripherals I add to the machine. As the binary which I have
contains all major protocols like
You mean hw/arm/msp2.c ?
On Wed, Sep 15, 2021, 13:55 Peter Maydell wrote:
> On Wed, 15 Sept 2021 at 12:13, abhijeet inamdar
> wrote:
> >
> > Now there are some many UART implemented in the hw/char. What should we
> look for or how do you choose which one to use? or implement similar kind.
>
>
On Wed, 15 Sept 2021 at 12:13, abhijeet inamdar
wrote:
>
> Now there are some many UART implemented in the hw/char. What should we look
> for or how do you choose which one to use? or implement similar kind.
You implement what the hardware you are modelling has, obviously.
This is why we have
Now there are some many UART implemented in the hw/char. What should we
look for or how do you choose which one to use? or implement similar kind.
Same case for I2C also.
I'm new to these so can you suggest me the basic one so that I can try and
implement it?
Thank you,
Abhijeet.
On Wed, Sep
On Wed, 15 Sept 2021 at 08:23, abhijeet inamdar
wrote:
>
> Hi,
>
> As my custom machine is based on cortex-m3 I checked the stellaris.c
> https://github.com/qemu/qemu/blob/stable-4.2/hw/arm/stellaris.c#1384,1390.
> Does only this part define the UART peripheral for this machine? Can you
>
Hi,
As my custom machine is based on cortex-m3 I checked the stellaris.c
https://github.com/qemu/qemu/blob/stable-4.2/hw/arm/stellaris.c#1384,1390.
Does only this part define the UART peripheral for this machine? Can you
point out any basic examples so that I can refer to ARM M3.
Any help would
On Tue, 14 Sept 2021 at 13:51, abhijeet inamdar
wrote:
>
> Is there any example for UART being added to the machine in 4.2.0?
Lots of machines have UARTs. Look at almost any Arm board.
-- PMM
Is there any example for UART being added to the machine in 4.2.0?
Thank you,
Abhijeet.
On Tue, Sep 14, 2021, 12:26 Peter Maydell wrote:
> On Tue, 14 Sept 2021 at 11:21, abhijeet inamdar
> wrote:
> >
> > My question is that can we see the list of devices for say any
> particular machine.
> >
On Tue, 14 Sept 2021 at 11:21, abhijeet inamdar
wrote:
>
> My question is that can we see the list of devices for say any particular
> machine.
> EX: if we do -m help.
> we do get the list of machines right so is their anything similar for the
> devices to check for a particular machine.
"-M
My question is that can we see the list of devices for say any particular
machine.
EX: if we do -m help.
we do get the list of machines right so is their anything similar for the
devices to check for a particular machine.
Thank you,
Abhijeet.
On Tue, Sep 14, 2021, 12:14 Peter Maydell wrote:
>
On Tue, 14 Sept 2021 at 10:58, abhijeet inamdar
wrote:
> Is there anything in qemu to check for a machine which all
> devices are added or working? Can we do that!?
I dunno what you're asking for; could you elaborate ?
In general each machine has a different set of devices that
it has, because
Hi,
Is there anything in qemu to check for a machine which all devices are
added or working? Can we do that!?
Thank you,
Abhijeet.
On Tue, Sep 14, 2021, 11:23 Peter Maydell wrote:
> On Tue, 14 Sept 2021 at 09:52, abhijeet inamdar
> wrote:
> > I was trying to emulate a machine i
On Tue, 14 Sept 2021 at 09:52, abhijeet inamdar
wrote:
> I was trying to emulate a machine in qemu-4.2.0 but was getting an error
> message:
>
> Unexpected error in qemu_chr_fe_init() at
> /home/qemu-4.2.0/chardev/char-fe.c:220:
> qemu-system-arm: Device 'serial0' is in use
&g
Hi,
I was trying to emulate a machine in qemu-4.2.0 but was getting an error
message:
Unexpected error in qemu_chr_fe_init() at
/home/qemu-4.2.0/chardev/char-fe.c:220:
qemu-system-arm: Device 'serial0' is in use
I tried to apply this patch
https://patchwork.kernel.org/project/qemu-devel/patch
Hi,
I was trying to use gdbstub what does vmlinux mean here?
Then launch gdb on the ‘vmlinux’ executable:
> gdb vmlinux
Is it my executable file or ?
On Mon, Jul 26, 2021, 15:44 abhijeet inamdar
wrote:
> Hi,
>
> Is there any particular Flash and RAM length for qemu to semihosting. I'm
>
Hi,
Is there any particular Flash and RAM length for qemu to semihosting. I'm
using q2-update-2017 tool chain and 16.04 Ubuntu.
On Fri, Jul 23, 2021, 14:16 Peter Maydell wrote:
> On Fri, 23 Jul 2021 at 13:05, abhijeet inamdar
> wrote:
> >
> > Means the memory mapping is not done correctly.
>
On Fri, 23 Jul 2021 at 13:05, abhijeet inamdar
wrote:
>
> Means the memory mapping is not done correctly.
>
> I have added '-d nochain' and '-singlestep' to the command line it gives me
> never ending
>
> Trace 0: 0x7ff207a5eac0 [/0572/0x312000c1] HardFault_Handler
> R00=218c
Means the memory mapping is not done correctly.
I have added '-d nochain' and '-singlestep' to the command line it gives me
never ending
Trace 0: 0x7ff207a5eac0 [/0572/0x312000c1] HardFault_Handler
R00=218c R01= R02=2264 R03=2264
R04=23f4 R05=23f4
On Fri, 23 Jul 2021 at 11:41, abhijeet inamdar
wrote:
>
> Hi,
>
> What information does this give me and how do I need to sort it out?
>
> after running qemu-system-arm along with -d
> in_asm,int,exec,cpu,guest_errors,unimp in the end i get this:
Adding '-d nochain' and '-singlestep' will make
Hi,
What information does this give me and how do I need to sort it out?
after running qemu-system-arm along with -d
in_asm,int,exec,cpu,guest_errors,unimp in the end i get this:
IN: Reset_Handler
0x050c: f7ff fff0 bl #0x4f0
Trace 0: 0x7f27e05ce100 [/050c/0x11c1]
On Thu, 22 Jul 2021 at 22:27, abhijeet inamdar
wrote:
>
> Hi,
>
> I downloaded the qemu-6.0.0. When I did ./configure inside qemu-6.0.0
> directory it say
> ERROR: Cannot find ninja
>
> wherein I did install pip3 install Ninja.
>
> What should I do?
You should install ninja, which is not a
eet inamdar
> wrote:
> > I have been trying to create my own machine and execute a hello_world on
> QEMU-4.2.0. I created mymachine.c in hw/arm and have my hello_world.c,
> mymachine.ld and startup_ARMCM3.S in qemu-4.2.0/proj.
>
> QEMU 4.2 is pretty old, I'm not sure if an
On Thu, 22 Jul 2021 at 13:57, abhijeet inamdar
wrote:
> I have been trying to create my own machine and execute a hello_world on
> QEMU-4.2.0. I created mymachine.c in hw/arm and have my hello_world.c,
> mymachine.ld and startup_ARMCM3.S in qemu-4.2.0/proj.
QEMU 4.2 is pretty old, I'm
Hi,
I have been trying to create my own machine and execute a hello_world on
QEMU-4.2.0. I created mymachine.c in hw/arm and have my hello_world.c,
mymachine.ld and startup_ARMCM3.S in qemu-4.2.0/proj.
So, firstly after adding mymachine.c in hw/arm I did "make" in the build
rt-manager QEMU 4.2.0 guest network no connection
I need to setup a CentOS 8 VM on my RHEL 8 workstation. I read that I can use
virt-manager for this and everything should work OK. I was able to built and
install the guest OS, but I cannot find anyway to get files from the host to
the guest,
I need to setup a CentOS 8 VM on my RHEL 8 workstation. I read that I can use
virt-manager for this and everything should work OK. I was able to built and
install the guest OS, but I cannot find anyway to get files from the host to
the guest, including getting the network hooked up. (I don't
Hi,
I have a .axf file how to debug it using gdb for qemu-system-arm?
Thanks,
Abhijeet.
On Wed, Jul 7, 2021, 12:09 abhijeet inamdar
wrote:
> I rectified it. Some headers were missing.
>
> Thanks,
> Abhijeet.
>
> On Wed, Jul 7, 2021, 11:24 abhijeet inamdar
> wrote:
>
>> Hi, I tried to
I rectified it. Some headers were missing.
Thanks,
Abhijeet.
On Wed, Jul 7, 2021, 11:24 abhijeet inamdar
wrote:
> Hi, I tried to implement from the example of stellaris.c but I'm getting
> some more warnings as follows:
>
> warning: implicit declaration of function 'qdev_prop_set_uint32'
>
Hi, I tried to implement from the example of stellaris.c but I'm getting
some more warnings as follows:
warning: implicit declaration of function 'qdev_prop_set_uint32'
[-Wimplicit-function-declaration]
qdev_prop_set_uint32(nvic, "num-irq", NUM_IRQ_LINES);
warning: implicit declaration of
plicit-function-declaration]
> qdev_connect_gpio_out_named(nvic, "SYSRESETREQ", 0,
> qemu_allocate_irq(_sys_reset, NULL, 0));
>
> Thanks,
> Abhijeet.
>
> On Tue, Jul 6, 2021, 16:59 Peter Maydell wrote:
>
>> On Tue, 6 Jul 2021 at 15:48, abhijeet inamdar
>> wrote:
On Tue, 6 Jul 2021 at 16:14, abhijeet inamdar
wrote:
>
> The warnings are as follows:
>
> warning: implicit declaration of function 'armv7m_init'
> [-Wimplicit-function-declaration]
> nvic = armv7m_init(systemMemory, memsz, NUM_IRQ_LINES, kernel_filename,
> cpu_type);
This function was removed
]
qdev_connect_gpio_out_named(nvic, "SYSRESETREQ", 0,
qemu_allocate_irq(_sys_reset, NULL, 0));
Thanks,
Abhijeet.
On Tue, Jul 6, 2021, 16:59 Peter Maydell wrote:
> On Tue, 6 Jul 2021 at 15:48, abhijeet inamdar
> wrote:
> >
> > Hi,
> >
> > I am tryi
On Tue, 6 Jul 2021 at 15:48, abhijeet inamdar
wrote:
>
> Hi,
>
> I am trying to build custom machine in QEMU-4.2.0.
>
> I'm getting some warning regarding armv7m_init() saying implicit declaration
> but I have defined it in the armv7m.c, even same kind of warning for the
Hi,
I am trying to build custom machine in QEMU-4.2.0.
I'm getting some warning regarding armv7m_init() saying implicit
declaration but I have defined it in the armv7m.c, even same kind of
warning for the qemu_allocate_irq().
I not able to find the right "commit" for both
On Mon, 28 Jun 2021 at 14:57, abhijeet inamdar
wrote:
>
> I sorted the MachineState error. We checkout the commit for serial_hds().
>
> Can get some link for the QEMU internal API changes for different versions
> machines. As I was not successful in finding one. Arm-cortex-m3 related.
Nope, I'm
I sorted the MachineState error. We checkout the commit for serial_hds().
Can get some link for the QEMU internal API changes for different versions
machines. As I was not successful in finding one. Arm-cortex-m3 related.
Thanks in advance.
BR.
Abhijeet.
On Mon, Jun 28, 2021, 15:30 Peter
On Mon, 28 Jun 2021 at 13:40, abhijeet inamdar
wrote:
>
> I didn't do any changes in the QEMU source code but added new for the .c and
> .h files for the custom machine.
That *is* changing the QEMU source code :-) Sorry, I'd missed you
were adding your own custom machine.
You'll find that
How else you add a custom machine??
BR.
Abhijeet.
On Mon, Jun 28, 2021, 14:40 abhijeet inamdar
wrote:
> I didn't do any changes in the QEMU source code but added new for the .c
> and .h files for the custom machine.
>
> BR.
> Abhijeet.
>
> On Mon, Jun 28, 2021, 14:35 Peter Maydell
> wrote:
>
On Mon, 28 Jun 2021 at 13:04, abhijeet inamdar
wrote:
>
> It is showing errors for serial_hds() and MachineState so what specific .h
> files I should add?
I'm not sure why you're changing the QEMU source code ? Hard to
say what is happening unless you say what your changes are.
thanks
-- PMM
I didn't do any changes in the QEMU source code but added new for the .c
and .h files for the custom machine.
BR.
Abhijeet.
On Mon, Jun 28, 2021, 14:35 Peter Maydell wrote:
> On Mon, 28 Jun 2021 at 13:04, abhijeet inamdar
> wrote:
> >
> > It is showing errors for serial_hds() and MachineState
asic program emulation.
>
> Now I have migrated to qemu-4.2.0. I want to run the same Hello_world.c
> which is not emulating.
>
> I have changed the .objs accordingly. What would you suggest?
>
> BR.
> Abhijeet.
>
> On Thu, Jun 24, 2021, 10:43 Peter Maydell
> wrote
Hi,
I have built custom hardware which is based on arm-m3 in qemu-2.10. It
works fine for Hello_world.c a basic program emulation.
Now I have migrated to qemu-4.2.0. I want to run the same Hello_world.c
which is not emulating.
I have changed the .objs accordingly. What would you suggest?
BR
On Wed, 23 Jun 2021 at 10:23, abhijeet inamdar
wrote:
>
> Hi,
>
> I want to know how to get the difference for an machine(ex: Akita) from
> qemu-2.10 to qemu-4.2.0.
>
> What all changes I should make for being compatible for it to be working in
> qemu-4.2.0 !?
Hi,
I want to know how to get the difference for an machine(ex: Akita) from
qemu-2.10 to qemu-4.2.0.
What all changes I should make for being compatible for it to be working in
qemu-4.2.0 !?
Best regards,
Abhijeet.
On Wed, Apr 22, 2020 at 04:13:29PM +0100, Peter Maydell wrote:
> On Wed, 22 Apr 2020 at 15:04, Gerd Hoffmann wrote:
> > 'pcspk' is the by far most tricky one. The device is present
> > unconditionally, -soundhw pcspk only triggers the registration
> > with the audiodev backend.
> >
> > 'hda'
On Wed, 22 Apr 2020, Philippe Mathieu-Daudé wrote:
Hi Jakob,
On 4/21/20 12:06 AM, Jakob Bohm wrote:
[...]
In fact, over the years, I have found it excruciatingly difficult to find
valid qemu documentation, as each feature effort tends to leave behind
half-updated pages and a bunch of
> > -soundhw hda
> >
> > After upgrade to 4.2.0 (qemu-4.2.0-7.fc32) I get the following
warning:
> > (qemu) audio: Device hda: audiodev default parameter is
deprecated, please specify audiodev=sound1
> >
> > The documentation `man
On 4/22/20 4:04 PM, Gerd Hoffmann wrote:
Hi,
I think the original intention was to deprecate -soundhw altogether, and
only use -device in new configs. However that was problematic with some
special devices, like pcspk and maybe others that are created by the machine
and not user creatable.
On Wed, 22 Apr 2020 at 15:04, Gerd Hoffmann wrote:
> 'pcspk' is the by far most tricky one. The device is present
> unconditionally, -soundhw pcspk only triggers the registration
> with the audiodev backend.
>
> 'hda' creates two devices (intel-hda + hda-duplex), so it is an actual
> shortcut
Hi,
> I think the original intention was to deprecate -soundhw altogether, and
> only use -device in new configs. However that was problematic with some
> special devices, like pcspk and maybe others that are created by the machine
> and not user creatable.
Ah, right, the pcspk issue. Thanks
Hi,
On 2020-04-20 16:44, Gerd Hoffmann wrote:
Hmm, good question how to proceed here best ...
"-soundhw hda" is a shortcut for "-device intel-hda -device hda-duplex"
You can use "-device intel-hda -device hda-duplex,audiodev=sound1" to
make the warning go away. That is pretty verbose when
> I'm using qemu-system-x86_64 with the following options:
> > -audiodev pa,id=sound1,server=/run/user/1000/pulse/native \
> > -soundhw hda
> >
> > After upgrade to 4.2.0 (qemu-4.2.0-7.fc32) I get the following
warning:
> > (qemu) audio: Device h
soundhw hda
> > >
> > > After upgrade to 4.2.0 (qemu-4.2.0-7.fc32) I get the following warning:
> > > (qemu) audio: Device hda: audiodev default parameter is deprecated,
> please specify audiodev=sound1
> > >
> > > The documentation `man qemu
On Fri, Apr 17, 2020 at 12:15:30PM +0100, Peter Maydell wrote:
> On Fri, 17 Apr 2020 at 12:08, Idar Lund wrote:
> > I'm using qemu-system-x86_64 with the following options:
> > -audiodev pa,id=sound1,server=/run/user/1000/pulse/native \
> > -soundhw hda
> >
> > A
On Fri, 17 Apr 2020 at 12:08, Idar Lund wrote:
> I'm using qemu-system-x86_64 with the following options:
> -audiodev pa,id=sound1,server=/run/user/1000/pulse/native \
> -soundhw hda
>
> After upgrade to 4.2.0 (qemu-4.2.0-7.fc32) I get the following warning:
> (qemu) audio: De
Hi,
I'm using qemu-system-x86_64 with the following options:
-audiodev pa,id=sound1,server=/run/user/1000/pulse/native \
-soundhw hda
After upgrade to 4.2.0 (qemu-4.2.0-7.fc32) I get the following warning:
(qemu) audio: Device hda: audiodev default parameter is deprecated, please
specify
How do I boot a UEFI linux guest with a windows 4.2.0 host and QEMU 4.2.0
installed ?
Thanks,
Jerry
65 matches
Mail list logo
