On Tue, 20 Feb 2024 at 22:22, 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.
Cool. So in principle this should work and there's likely some fixable issue with how you're loading the image. > 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. This is also useful information. I would suggest you look at what the difference is between the image that boots and the one that doesn't: is it the same format (and what format is that)? is the way it is loaded on the real hardware the same, or different? >From the debug info from gdb you provided, the file clearly is not a raw binary file -- the initial bytes seem to be largely ASCII text. So it might be that this image is in a file format that whatever the real-hardware loader recognizes, but QEMU doesn't, whereas the images you have that work are really raw binaries. In that case you'd want to convert the image somehow to a format QEMU can understand (eg ELF, or raw-binary). thanks -- PMM
