Hi Alex, I have created a new QNX image, particularly for Qemu, and still, both the prompts are hanging without any further details. Please have a look at the results of both terminals below
qemu-system-aarch64.exe -M xlnx-zcu102 -m 16G -serial mon:stdio -display none -device loader,file="C:ifs.bin",addr=0x00100000,cpu-num=0 -drive file=qemu-raw-img,format=raw,index=1,if=sd -net nic,model=cadence_gem -net nic,model=cadence_gem -net nic,model=cadence_gem -net nic,model=cadence_gem,netdev=xzynq0 -netdev user,id=xzynq0,tftp=/tftpboot -nographic -global xlnx,zynqmp-boot.cpu-num=0 -global 'xlnx,zynqmp-boot.use-pmufw=true' -s -S qemu-system-aarch64.exe: warning: hub 0 is not connected to host network qemu-system-aarch64.exe: warning: global xlnx,zynqmp-boot.cpu-num has invalid class name qemu-system-aarch64.exe: warning: global 'xlnx,zynqmp-boot.use-pmufw has invalid class name QEMU: Terminated GDB For help, type "help". Type "apropos word" to search for commands related to "word"... Reading symbols from C:\Users\sayedf\qnx710\image-with-drivers\output\ifs.bin...(no debugging symbols found)...done. (gdb) target remote :1234 Remote debugging using :1234 warning: Can not parse XML target description; XML support was disabled at compile time 0x0000000080000800 in ?? () (gdb) c Continuing. [Inferior 1 (process 1) exited normally] Please have a look :) On Tue, Feb 20, 2024 at 11:22 PM Faiq Ali Sayed <faiqueali....@gmail.com> wrote: > The real hardware ( xlnx-zcu102 ) is being used for our software. The > software is in the development phase, and for that, I need to create a VM > for simulation purposes. > Qemu has a machine type (-M xlnx-zcu102) which is supported with the > board/hardware. > > I have two more images for the same hardware and I can create a VM using > these two images, but in the VM some basic binaries are missing like mkdir > and virtual disk etc. > > Now, the image for which I want to create a VM is currently working on > board and everything is working fine on real hardware. > I am not sure whether I can use this image for Qemu because this is > created particularly for hardware. > and giving a try to create a VM. > > Your valuable suggestions in this regard will be appreciated and mean a > lot to me :) > > > br! > Faiq > > > > On Tue, Feb 20, 2024 at 10:24 PM Peter Maydell <peter.mayd...@linaro.org> > wrote: > >> On Tue, 20 Feb 2024 at 20:56, Faiq Ali Sayed <faiqueali....@gmail.com> >> wrote: >> > >> > The image I am using is currently in use for real hardware, and >> > I received it from a third party/vendor. >> >> OK, so what exactly is the real hardware it's for? >> >> > Could you please suggest to me what I can do now? >> >> If QEMU has a model of the hardware the image is for: >> - use that QEMU machine type (and issues with getting it running >> will be related to making sure you're loading it at the right >> address and starting it the way it wants to be started) >> If QEMU does not have a model of the hardware the image is for: >> - ask your vendor for a build that targets some machine QEMU >> does have a model of >> >> Unfortunately in general in the Arm world guest OSes are >> not "runs on anything", but only "runs on the hardware >> they were built to run on". This remains true under emulation. >> >> thanks >> -- PMM >> > > > -- > Kind Regard- > Faiq Ali Sayed > > > -- Kind Regard- Faiq Ali Sayed