Feed for discussion General in project QNX Community QEMU™ Project.

post119448: QNX7/QEMU virt machine ARM64 with u-boot: loading kernel OK but stucks on Starting application...

antonio rosario intilisano(deleted) — Fri, 25 Jan 2019 10:57:22 GMT

IFS QNX image using mkifs builded successfully (ELF type, see attached to get full log)

[image=0x40000000]

[virtual=aarch64le,elf] boot = {

      startup-armv8_fm

      PATH=/proc/boot:/bin:/usr/bin:/sbin:/usr/sbin LD_LIBRARY_PATH=/proc/boot:/lib:/usr/lib:/lib/dll:/lib/dll procnto-smp-instr-safety

}

mkifs output:

40000200    100     ----      --- Startup-header

40000300  11208 40000800      --- /tmp/file6FDyfo (1510146467)

40011308     5c     ----      --- Image-header

40011364   25c8     ----      --- Image-directory

I used mkimage to make the image bootable from u-boot

$mkimage -A arm64 -O QNX -T kernel -C none  -a 0x40000000 -e 0x40000000  -n Test QNX arm64 image -d aarch64le.bin uboot-image.img

The image is recognized successfully by u-boot as ELF image but the boostrap process is blocked after the loading kernel:

=> fatload nvme 0:1 0x40000000  .boot/uboot-image.img

20608792 bytes read in 10 ms (1.9 GiB/s)

=> bootm 0x40000000

## Booting kernel from Legacy Image at 40000000 ...

   Image Name:   VRTE QNX arm64 image

   Created:      2019-01-25  10:34:11 UTC

   Image Type:   AArch64 QNX Kernel Image (uncompressed)

   Data Size:    20608728 Bytes = 19.7 MiB

   Load Address: 40000000

   Entry Point:  40000000

   Verifying Checksum ... OK

   Loading Kernel Image ... OK

## Starting application at 0x40000800 ...

QEMU-configuration:

$qemu-system-aarch64 -cpu cortex-a53 -machine virt,highmem=off -serial stdio -bios ../u-boot-2018.11/u-boot.bin -drive if=none,file=qnx-aarch64le-qemu.img,id=mydisk,format=raw -device nvme,drive=mydisk,serial=foo -device virtio-rng-pci -m 1G -display none  -netdev user,id=net0 -device e1000,netdev=net0 -monitor none -smp 1

Thank you!

post112690: Has anyone played with this vaguely recently?

Danny Clark(deleted) — Tue, 16 Dec 2014 01:27:57 GMT

If so, any new info?

This looks nifty but also possibly abandoned.

post91975: QEMU User space emulator

Robin Vogt — Thu, 08 Mar 2012 14:18:12 GMT

Hello all,

I have the following problem:

I'm using QNX 6.3.2 on x86 and Version 0.9 of this project.

In addition to the QEMU System emulator, a also need the QEMU User space emulator for x86 and ppc.

But neither in the precompiled binaries, nor after compiling the 0.9 Source myself, i can find the needed binaries for user space emulation (qemu-i386 and qemu-ppc).

Can anybody tell me how i can get them, or are they not supportet in Version 0.9?

Thanks a lot for your help!

Robin

post57281: How do I load QNX on the QEMU(ARM) emulator?

Mark reeder(deleted) — Mon, 21 Jun 2010 13:21:32 GMT

I have QEMU configured on a LINUX system. What is my next step?

1. Where do I get QNX 6.3.2 to install? Is this something that I need to create?

2. Is there a ARM runtime kit? (we have the x86 runtime kit but need ARM)

post55322: Re: running QNX with "qemu-minimal.build" problem

A T — Thu, 20 May 2010 21:39:03 GMT

I have a similar problem.

# uname -a

QNX localhost 6.5.0 2010/03/12-01: 55:55 EST x86pc x86

then start qemu

# qemu-hda hd.raw -vga std -m 128

qemu is written in the following

Booting from Hard Disk ...

Hit Esc for. Altboot .................................D

is exactly the letter D - in the end. Then nothing happens.

All this runs under vmware (vmware -> QNX 6.5.0 -> qemu -> qnx6).

How do I fix this?

post47320: Re: Booting QNX on QEMU(ARM)

Leonid Khait(deleted) — Mon, 15 Feb 2010 16:56:59 GMT

This is the list of ARM processors emulated in qemu-system-arm 0.9.0

Supported machines are:

integratorcp926 ARM Integrator/CP (ARM926EJ-S) (default)

integratorcp1026 ARM Integrator/CP (ARM1026EJ-S)

versatilepb ARM Versatile/PB (ARM926EJ-S)

versatileab ARM Versatile/AB (ARM926EJ-S)

realview ARM RealView Emulation Baseboard (ARM926EJ-S)

Which BSP is better to test QNX elf image as a kernel to start ander qemu?

I have no succsess right now.

post30906: Re: Booting QNX on QEMU(ARM)

Johnson Thomas — Thu, 04 Jun 2009 22:20:24 GMT

Hi Collin,

Its doing something, but no idea whats its doing.I was trying for at91sam9263 BSP, the same thing happens. I integrated the u-boot loader also into the image and I have a uImage now. I tried to run u-boot.bin but its crashing with the following message

qemu: fatal: Trying to execute code outside RAM or ROM at 0x23f00488

R00=23f7871c R01=23f78718 R02=00000000 R03=00000000

R04=00000000 R05=00000000 R06=00000000 R07=00000000

R08=00000000 R09=00000000 R10=00000000 R11=00000000

R12=00000000 R13=23ed2f74 R14=00010094 R15=23f00488

PSR=200001d3 --C- A svc32

s00=00000000(       0) s01=00000000(       0) d00=0000000000000000(       0)

s02=00000000(       0) s03=00000000(       0) d01=0000000000000000(       0)

s04=00000000(       0) s05=00000000(       0) d02=0000000000000000(       0)

s06=00000000(       0) s07=00000000(       0) d03=0000000000000000(       0)

s08=00000000(       0) s09=00000000(       0) d04=0000000000000000(       0)

s10=00000000(       0) s11=00000000(       0) d05=0000000000000000(       0)

s12=00000000(       0) s13=00000000(       0) d06=0000000000000000(       0)

s14=00000000(       0) s15=00000000(       0) d07=0000000000000000(       0)

s16=00000000(       0) s17=00000000(       0) d08=0000000000000000(       0)

s18=00000000(       0) s19=00000000(       0) d09=0000000000000000(       0)

s20=00000000(       0) s21=00000000(       0) d10=0000000000000000(       0)

s22=00000000(       0) s23=00000000(       0) d11=0000000000000000(       0)

s24=00000000(       0) s25=00000000(       0) d12=0000000000000000(       0)

s26=00000000(       0) s27=00000000(       0) d13=0000000000000000(       0)

s28=00000000(       0) s29=00000000(       0) d14=0000000000000000(       0)

s30=00000000(       0) s31=00000000(       0) d15=0000000000000000(       0)

FPSCR: 00000000

Aborted

This is happening with every BSP or image that I am trying. Is there any settings or anything that has to be done for QEMU or to the way I am creating the image.

Any help would be great.

Thanks,

Johnson

post30877: Re: Booting QNX on QEMU(ARM)

Colin Burgess — Thu, 04 Jun 2009 19:29:49 GMT

I'm pretty sure you need to tell qemu that it's emulating an omap2420 - the default ARM reference board it emulates is not going to have the same peripherals at the same locations.

For that matter, I don't think that 0.9.1 emulates an omap2420

Johnson Thomas wrote:

> Hi,

> I am trying to boot QNX on QEMU (ARM platform). I downloaded one of the BSPs from qnx site and built. I made the ifs image from this build file(using elf.boot).i ran this on qemu-system-arm -kernel PATH_TO_IFS_IMAGE and an empty QEMU window pops up. I have no clue of what is happening.

>

> the mkifs -v generated this.

>

>   Offset   Size    Entry   Ramoff Target=Host

> 80010000    180        0      --- /opt/qnx640/target/qnx6/armle/boot/sys/elf.boot

> 80010180    100     ----      --- Startup-header

> 80010280   c188 80011be0      --- /tmp/fileoSTxRg

> 8001c288     5c     ----      --- Image-header

> 8001c2e4    760     ----      --- Image-directory

>     ----    ---     ----      --- tmp=/dev/shmem

>     ----    ---     ----      --- dev/console=/dev/ser1

>     ----    ---     ----      --- bin/sh=/proc/boot/ksh

> 8001ca44    314     ----      --- proc/boot/.script=/tmp/fileNzj1X1

> 8001d000  6b000 fe03adf0      --- proc/boot/procnto-v6=/tmp/filecBHu7v

> 80088000  73000    389c4      --- proc/boot/libc.so.3=/opt/qnx640/target/qnx6/ar

> mle/lib/libc.so

>     ----    ---     ----      --- proc/boot/libc.so=libc.so.3

> 800fb000   ec1e     2364      --- proc/boot/devn-smc9000.so=/opt/qnx640/target/q

> nx6/armle/lib/dll/devn-smc9000.so

> 8010a000  2acf3     5738      --- proc/boot/libsocket.so.2=/opt/qnx640/target/qn

> x6/armle/lib/libsocket.so

>     ----    ---     ----      --- proc/boot/libsocket.so=libsocket.so.2

> 80135000   88c6     2208      --- proc/boot/devnp-shim.so=/opt/qnx640/target/qnx

> 6/armle/lib/dll/devnp-shim.so

> 8013e000   a9d0     2fdc      --- proc/boot/libusbdi.so.2=/opt/qnx640/target/qnx

> 6/armle/lib/libusbdi.so

>     ----    ---     ----      --- proc/boot/libusbdi.so=libusbdi.so.2

> 80149000   a799     1ad8      --- proc/boot/devu-ohci.so=/opt/qnx640/target/qnx6

> /armle/lib/dll/devu-ohci.so

> 80154000  1019b   101cc8      --- proc/boot/devc-seromap=/opt/qnx640/target/qnx6

> /armle/boot/sys/devc-seromap

> 80165000  12f20   10193c      --- proc/boot/fs-etfs-omap2420=/opt/qnx640/target/

> qnx6/armle/boot/sys/fs-etfs-omap2420

> 80178000   37e6   1009d4      --- proc/boot/etfsctl=/opt/qnx640/target/qnx6/arml

> e/usr/bin/etfsctl

> 8017c000   54d9   100f98      --- proc/boot/i2c-omap59xx=/opt/qnx640/target/qnx6

> /armle/boot/sys/i2c-omap59xx

> 80182000  8dc15   10e200      --- proc/boot/io-pkt-v4=/opt/qnx640/target/qnx6/ar

> mle/sbin/io-pkt-v4

> 80210000   4dfa   100998      --- proc/boot/nicinfo=/opt/qnx640/target/qnx6/arml

> e/usr/sbin/nicinfo

> 80215000  164df   1015f0      --- proc/boot/ifconfig=/opt/qnx640/target/qnx6/arm

> le/sbin/ifconfig

> 8022c000   a87d   1011f8      --- proc/boot/ping=/opt/qnx640/target/qnx6/armle/u

> sr/bin/ping

> 80237000   2257   100638      --- proc/boot/cat=/opt/qnx640/target/qnx6/armle/bi

> n/cat

> 8023a000  13ad3   101d74      --- proc/boot/fs-nfs2=/opt/qnx640/target/qnx6/arml

> e/usr/sbin/fs-nfs2

> 8024e000   521b   100e60      --- proc/boot/ls=/opt/qnx640/target/qnx6/armle/bin                                                                                                   /ls

> 80254000  2abd8   1017c0      --- proc/boot/ksh=/opt/qnx640/target/qnx6/armle/bi                                                                                                   n/ksh

> 8027f000   527f   1015b4      --- proc/boot/pipe=/opt/qnx640/target/qnx6/armle/s                                                                                                   bin/pipe

> 80285000   fdd4   101594      --- proc/boot/pidin=/opt/qnx640/target/qnx6/armle/                                                                                                   bin/pidin

> 80295000   1fd6   100598      --- proc/boot/uname=/opt/qnx640/target/qnx6/armle/                                                                                                   bin/uname

> 80297000   3820   100d50      --- proc/boot/slogger=/opt/qnx640/target/qnx6/arml                                                                                                   e/usr/sbin/slogger

> 8029b000   295b   100a44      --- proc/boot/sloginfo=/opt/qnx640/target/qnx6/arm                                                                                                   le/bin/sloginfo

> 8029e000   4963   100ea4      --- proc/boot/slay=/opt/qnx640/target/qnx6/armle/b                                                                                                   in/slay

> 802a3000   975f   101058      --- proc/boot/cp=/opt/qnx640/target/qnx6/armle/bin                                                                                                   /cp

> 802ad000   5b68   1015ac      --- proc/boot/waitfor=/opt/qnx640/target/qnx6/arml                                                                                                   e/bin/waitfor

> 802b3000   353f   100d18      --- proc/boot/shutdown=/opt/qnx640/target/qnx6/arm                                                                                                   le/bin/shutdown

> 802b6540      4     ----      --- Image-trailer

>

> I even tried integrating the u-boot bootloader to the image.I donwloaded the latest u-boot and in this did the following

> ARCH=arm

> export $ARCH

> CROSS_COMPILE=arm-unknown-nto-qnx6.4.0-

> make omap2420h4_config       (I downloaded the omap2420 BSP from qnx)

> make all

>

> it generated a u-boot.bin file. I used the mkimage command and generated a uImage also. But when i run this u-boot.bin using the command qemu-system-arm -kernel u-boot.bin , again the same empty qemu window opens.Is it atleast possible to get a uboot command line console using this u-boot.bin?

> Any help would be great.

>

> Thanks,

> Johnson

>

> _______________________________________________

> General

> http://community.qnx.com/sf/go/post30838

--

cburgess@qnx.com

post30838: Booting QNX on QEMU(ARM)

Johnson Thomas — Thu, 04 Jun 2009 16:53:55 GMT

Hi,

I am trying to boot QNX on QEMU (ARM platform). I downloaded one of the BSPs from qnx site and built. I made the ifs image from this build file(using elf.boot).i ran this on qemu-system-arm -kernel PATH_TO_IFS_IMAGE and an empty QEMU window pops up. I have no clue of what is happening.

the mkifs -v generated this.

  Offset   Size    Entry   Ramoff Target=Host

80010000    180        0      --- /opt/qnx640/target/qnx6/armle/boot/sys/elf.boot

80010180    100     ----      --- Startup-header

80010280   c188 80011be0      --- /tmp/fileoSTxRg

8001c288     5c     ----      --- Image-header

8001c2e4    760     ----      --- Image-directory

    ----    ---     ----      --- tmp=/dev/shmem

    ----    ---     ----      --- dev/console=/dev/ser1

    ----    ---     ----      --- bin/sh=/proc/boot/ksh

8001ca44    314     ----      --- proc/boot/.script=/tmp/fileNzj1X1

8001d000  6b000 fe03adf0      --- proc/boot/procnto-v6=/tmp/filecBHu7v

80088000  73000    389c4      --- proc/boot/libc.so.3=/opt/qnx640/target/qnx6/ar

mle/lib/libc.so

    ----    ---     ----      --- proc/boot/libc.so=libc.so.3

800fb000   ec1e     2364      --- proc/boot/devn-smc9000.so=/opt/qnx640/target/q

nx6/armle/lib/dll/devn-smc9000.so

8010a000  2acf3     5738      --- proc/boot/libsocket.so.2=/opt/qnx640/target/qn

x6/armle/lib/libsocket.so

    ----    ---     ----      --- proc/boot/libsocket.so=libsocket.so.2

80135000   88c6     2208      --- proc/boot/devnp-shim.so=/opt/qnx640/target/qnx

6/armle/lib/dll/devnp-shim.so

8013e000   a9d0     2fdc      --- proc/boot/libusbdi.so.2=/opt/qnx640/target/qnx

6/armle/lib/libusbdi.so

    ----    ---     ----      --- proc/boot/libusbdi.so=libusbdi.so.2

80149000   a799     1ad8      --- proc/boot/devu-ohci.so=/opt/qnx640/target/qnx6

/armle/lib/dll/devu-ohci.so

80154000  1019b   101cc8      --- proc/boot/devc-seromap=/opt/qnx640/target/qnx6

/armle/boot/sys/devc-seromap

80165000  12f20   10193c      --- proc/boot/fs-etfs-omap2420=/opt/qnx640/target/

qnx6/armle/boot/sys/fs-etfs-omap2420

80178000   37e6   1009d4      --- proc/boot/etfsctl=/opt/qnx640/target/qnx6/arml

e/usr/bin/etfsctl

8017c000   54d9   100f98      --- proc/boot/i2c-omap59xx=/opt/qnx640/target/qnx6

/armle/boot/sys/i2c-omap59xx

80182000  8dc15   10e200      --- proc/boot/io-pkt-v4=/opt/qnx640/target/qnx6/ar

mle/sbin/io-pkt-v4

80210000   4dfa   100998      --- proc/boot/nicinfo=/opt/qnx640/target/qnx6/arml

e/usr/sbin/nicinfo

80215000  164df   1015f0      --- proc/boot/ifconfig=/opt/qnx640/target/qnx6/arm

le/sbin/ifconfig

8022c000   a87d   1011f8      --- proc/boot/ping=/opt/qnx640/target/qnx6/armle/u

sr/bin/ping

80237000   2257   100638      --- proc/boot/cat=/opt/qnx640/target/qnx6/armle/bi

n/cat

8023a000  13ad3   101d74      --- proc/boot/fs-nfs2=/opt/qnx640/target/qnx6/arml

e/usr/sbin/fs-nfs2

8024e000   521b   100e60      --- proc/boot/ls=/opt/qnx640/target/qnx6/armle/bin                                                                                                   /ls

80254000  2abd8   1017c0      --- proc/boot/ksh=/opt/qnx640/target/qnx6/armle/bi                                                                                                   n/ksh

8027f000   527f   1015b4      --- proc/boot/pipe=/opt/qnx640/target/qnx6/armle/s                                                                                                   bin/pipe

80285000   fdd4   101594      --- proc/boot/pidin=/opt/qnx640/target/qnx6/armle/                                                                                                   bin/pidin

80295000   1fd6   100598      --- proc/boot/uname=/opt/qnx640/target/qnx6/armle/                                                                                                   bin/uname

80297000   3820   100d50      --- proc/boot/slogger=/opt/qnx640/target/qnx6/arml                                                                                                   e/usr/sbin/slogger

8029b000   295b   100a44      --- proc/boot/sloginfo=/opt/qnx640/target/qnx6/arm                                                                                                   le/bin/sloginfo

8029e000   4963   100ea4      --- proc/boot/slay=/opt/qnx640/target/qnx6/armle/b                                                                                                   in/slay

802a3000   975f   101058      --- proc/boot/cp=/opt/qnx640/target/qnx6/armle/bin                                                                                                   /cp

802ad000   5b68   1015ac      --- proc/boot/waitfor=/opt/qnx640/target/qnx6/arml                                                                                                   e/bin/waitfor

802b3000   353f   100d18      --- proc/boot/shutdown=/opt/qnx640/target/qnx6/arm                                                                                                   le/bin/shutdown

802b6540      4     ----      --- Image-trailer

I even tried integrating the u-boot bootloader to the image.I donwloaded the latest u-boot and in this did the following

ARCH=arm

export $ARCH

CROSS_COMPILE=arm-unknown-nto-qnx6.4.0-

make omap2420h4_config       (I downloaded the omap2420 BSP from qnx)

make all

it generated a u-boot.bin file. I used the mkimage command and generated a uImage also. But when i run this u-boot.bin using the command qemu-system-arm -kernel u-boot.bin , again the same empty qemu window opens.Is it atleast possible to get a uboot command line console using this u-boot.bin?

Any help would be great.

Thanks,

Johnson

post30143: Re: Networking with linux host

Rodrigo Campos — Wed, 27 May 2009 16:15:00 GMT

Yes, we managed to setup a network.

We are using kvm, and our line to boot is like this:

kvm -m 512 -net tap,script=/etc/kvm/kvm-ifup -net nic,model=ne2k_pci,macaddr=52:00:D4:85:30:00 -drive file=/var/lib/kvm/qnx/qnx-momentics.raw

Then, modify qnxbasedma.build in the guest as documented here: http://community.qnx.com/sf/wiki/do/viewPage/projects.qemu/wiki/NeutrinoAsGuestInQEMU and it should work =)

Hope it helps

post28105: Re: One more try ofqemu+Neutrino

Alex Chapiro — Mon, 27 Apr 2009 03:47:13 GMT

I used 6.4.1, so your changes should be there. Maybe I misinterpreted the connection failure and fixed the wrong cause. At the same time with "fixing" of pci problem, I changed Realtec 8139 to Ne2000. which probably helped. Maybe I'll try default boot in combination with Ne2000 to prove that it works.

post28101: Re: One more try ofqemu+Neutrino

Colin Burgess — Mon, 27 Apr 2009 01:38:40 GMT

If you use an updated bios.boot (from 6.4.0 or later) you shouldn't have an issue with pci-bios anymore.

See PR57626 for details...

Alex Chapiro wrote:

> I haven't tried it for a while being discouraged after my first experiments with qemu0.9. Couple of days ago I opened qemu.org and found new release 0.10.2. Decided to try once again. To streamline the way I decided to use Windows front end QEMU Manager 6 (dull UI but saves time). Host OS Windows7RC1, guest -6.4.1M4. Maybe in contrast with frustration I felt after the first try now things seem to be much more positive:-).

> Installation -good (just no problem, besides known issue with pci which can be easy fixed).

> Networking - not bad. I had Internet immediately after the first reboot. To run debug session via qconn turned out to be a bit more complicated (just because of my stupidity :-) Not necessary to install tap any more.

> Host disk space sharing - good (without problem I connected shared host folder as extra hard drive).

> HID - not so good, but acceptable (or near that). Actually keyboard & mouse worked much better than before and than on SUN VM (just terrible experience). Feel a bit shame about that:-)

> Performance. I didn't test it specially. At least system response fast enough to be not annoying. I didn't used accelerator KQEMU. Computer Intel quad 6400 8gb ram, NVIDIA GeForce 8600 GT.

> Graphics. I didn't find at the first glance any problem with Photon.

>

> Conclusion. At last it can be used. Or sort of...

>

> _______________________________________________

> General

> http://community.qnx.com/sf/go/post28082

>

--

cburgess@qnx.com

post28082: One more try ofqemu+Neutrino

Alex Chapiro — Sat, 25 Apr 2009 04:27:54 GMT

I haven't tried it for a while being discouraged after my first experiments with qemu0.9. Couple of days ago I opened qemu.org and found new release 0.10.2. Decided to try once again. To streamline the way I decided to use Windows front end QEMU Manager 6 (dull UI but saves time). Host OS Windows7RC1, guest -6.4.1M4. Maybe in contrast with frustration I felt after the first try now things seem to be much more positive:-).

Installation -good (just no problem, besides known issue with pci which can be easy fixed).

Networking - not bad. I had Internet immediately after the first reboot. To run debug session via qconn turned out to be a bit more complicated (just because of my stupidity :-) Not necessary to install tap any more.

Host disk space sharing - good (without problem I connected shared host folder as extra hard drive).

HID - not so good, but acceptable (or near that). Actually keyboard & mouse worked much better than before and than on SUN VM (just terrible experience). Feel a bit shame about that:-)

Performance. I didn't test it specially. At least system response fast enough to be not annoying. I didn't used accelerator KQEMU. Computer Intel quad 6400 8gb ram, NVIDIA GeForce 8600 GT.

Graphics. I didn't find at the first glance any problem with Photon.

Conclusion. At last it can be used. Or sort of...

post22099: Re: running QNX with "qemu-minimal.build" problem

Pietro Descombes — Thu, 12 Feb 2009 15:17:25 GMT

Hi Colin,

I'm back! So,

Shame on me! I took the wrong project source (core_networking instead of coreos_pub). I didn't even have a procnto!! Once rectified, I still had the same problems though (83 and 2). But following your instructions, that is,

- changing the build file as you told to, and

- adding "-r stage" to mkifs command

solved the problems :-))

Thanks a lot for your helpful replies !!!

Pietro

For those whom it might help, here is la little detail on changes that made it work for me:

In "qemu-minimal.build" (to match later versions)

- change the link code-line to match "procmgr_symlink ../../proc/boot/libc.so.3 /usr/lib/ldqnx.so.2"

- change all the "io.net" into "io-pkt-v4" and replace "waitfor /dev/io-net/en0" by "waitfor /proc/boot/io-pkt-v4"

- comment or remove "npm-tcpip.so"

Then make image using "mkifs -r stage -v qemu-minimal.build qemu-minimal.ifs" (the verbose mode has helped me finding out and fixing what was being done).

post21101: Re: running QNX with "qemu-minimal.build" problem

Colin Burgess — Fri, 30 Jan 2009 16:45:56 GMT

Hi Pietro,

Ok, it sounds like you are using 6.4.0

In that case, you change your qemu-minimal.build to use libc.so.3

Change the libc.so.2 back to libc.so (or libc.so.3)

if you are going to run any 6.3.2 binaries then also add libc.so.2 (it's fairly small)

You should then change the /usr/lib/ldqnx.so.2 link to point to libc.so.3

io-net is no longer shipped with 6.4.0 - now it's io-pkt, and npm-tcpip.so is included directly

in that binary.  You should probably check to see if the driver has been updated to the devnp-*.so version.

WRT mkifs not getting the components from your build, mkxfs will normally look in $QNX_TARGET, which is the

momentics install.  You should try adding -r <yourbuilddir> as an option to mkifs

Regards,

Colin

Pietro Descombes wrote:

> Hi Colin,

>

> thanks for replying!

> So,

>

> 1) yes! the ./trunk/utils/t/tcpdump/win32/Include/errno.h file reveals the natures of errors

> #define ELIBEXEC 83 /* Cannot exec a shared library directly */

> #define ENOENT 2 /* No such file or directory */

> This shows not surprisingly components are missing from the image (2) and not executed (83).

> (no ESHLIBACC in this file)

>

>

> 2) versions: You're write to point out that I might be confused: I've got Momentics 6.4.0 (qnxsdp-6.4.0-x86-200810211530-linux.bin) which installed itself in '/opt/qnx640'.

> Regarding the QNX source, as I downloaded it a few days ago with svn, and updated it just before sending my post, so I have the latest build (or almost if changed since then). That's why I THINK I have source 6.4.0.

> The only thing I changed in the version number in the 'qemu-minimal.build' welcome message.

> There are many files named 'version*' but they don't help much.

>

>

> 3) libc.so

> I think that's the trick! I do have several files called that way in $QNX_TARGET (but none in the source):

> /opt/qnx640/target/qnx6/x86/lib/libc.so.3

> /opt/qnx640/target/qnx6/x86/lib/libc.so.1

> /opt/qnx640/target/qnx6/x86/lib/libc.so

> /opt/qnx640/target/qnx6/x86/lib/libc.so.2

>

> In 'qemu-minimal.build' replacing, the line "libc.so" by "libc.so.2" avoids all the (83) errors :-)) . "Mounting Filesystems" and "Starting esh" don't show error messages anymore, but I still can't type anything in the (esh) console.

>

> I've tried several other unsuccessful tweaks in 'qemu-minimal.build'.  and other ".build" files found in 'opt/target/qnx6/x86/boot/build/': different behaviour, still nothing usable.

>

>

> 4) I still wonder what why I get those:

> << Warning: Host file 'npm-tcpip.so' missing.

> Warning: Host file 'io-net' missing. >>

> which I can't find anywhere. I can disable them by removing the components in 'qemu-minimal.build', but that message shows that there is a problem somewhere.

>

> And why are there so many missing files in '/dev/' (see qemu's running outputs), files not included properly?

>

>

> I have a sneaking suspicion that the compilation isn't doing all it's job. All the elements stated in  'qemu-minimal.build' come from Momentics rather than 'stage' or 'trunk'. Even 'procnto' doesn't come from my compilation. How come?

>

>

> Yes, that's a long post... I hope you have the patience to read that.

> You did help me already, but things still don't work on.

>

> Pietro

>

>

> _______________________________________________

> General

> http://community.qnx.com/sf/go/post21096

>

--

cburgess@qnx.com

post21096: Re: RE: running QNX with "qemu-minimal.build" problem

Pietro Descombes — Fri, 30 Jan 2009 16:30:15 GMT

Hi Colin,

thanks for replying!

So,

1) yes! the ./trunk/utils/t/tcpdump/win32/Include/errno.h file reveals the natures of errors

#define ELIBEXEC 83 /* Cannot exec a shared library directly */

#define ENOENT 2 /* No such file or directory */

This shows not surprisingly components are missing from the image (2) and not executed (83).

(no ESHLIBACC in this file)

2) versions: You're write to point out that I might be confused: I've got Momentics 6.4.0 (qnxsdp-6.4.0-x86-200810211530-linux.bin) which installed itself in '/opt/qnx640'.

Regarding the QNX source, as I downloaded it a few days ago with svn, and updated it just before sending my post, so I have the latest build (or almost if changed since then). That's why I THINK I have source 6.4.0.

The only thing I changed in the version number in the 'qemu-minimal.build' welcome message.

There are many files named 'version*' but they don't help much.

3) libc.so

I think that's the trick! I do have several files called that way in $QNX_TARGET (but none in the source):

/opt/qnx640/target/qnx6/x86/lib/libc.so.3

/opt/qnx640/target/qnx6/x86/lib/libc.so.1

/opt/qnx640/target/qnx6/x86/lib/libc.so

/opt/qnx640/target/qnx6/x86/lib/libc.so.2

In 'qemu-minimal.build' replacing, the line "libc.so" by "libc.so.2" avoids all the (83) errors :-)) . "Mounting Filesystems" and "Starting esh" don't show error messages anymore, but I still can't type anything in the (esh) console.

I've tried several other unsuccessful tweaks in 'qemu-minimal.build'. and other ".build" files found in 'opt/target/qnx6/x86/boot/build/': different behaviour, still nothing usable.

4) I still wonder what why I get those:

<< Warning: Host file 'npm-tcpip.so' missing.

Warning: Host file 'io-net' missing. >>

which I can't find anywhere. I can disable them by removing the components in 'qemu-minimal.build', but that message shows that there is a problem somewhere.

And why are there so many missing files in '/dev/' (see qemu's running outputs), files not included properly?

I have a sneaking suspicion that the compilation isn't doing all it's job. All the elements stated in 'qemu-minimal.build' come from Momentics rather than 'stage' or 'trunk'. Even 'procnto' doesn't come from my compilation. How come?

Yes, that's a long post... I hope you have the patience to read that.

You did help me already, but things still don't work on.

Pietro

post20978: RE: running QNX with "qemu-minimal.build" problem

Colin Burgess — Thu, 29 Jan 2009 13:13:05 GMT

Pietro - the errors you see can be translated in errno.h

It looks like you have 6.3.2 installed.   The libc.so version changed from 2 to 3

in 6.4.0, and this is used as the ldqnx.so.2 dynamic linker, hence 83 (ESHLIBACC)

The following errors are as a result of the core servers failing to start.

For running 6.3.2 binaries on 6.4.0 we do supply a compat version of libc.so.2

Colin

________________________________

From: Pietro Descombes [mailto:community-noreply@qnx.com]

Sent: Thu 1/29/2009 7:31 AM

To: general-qemu

Subject: running QNX with "qemu-minimal.build" problem

Hi everyone,

I'm trying to run QNX (source code) on QEMU but either the compilation,

or the image creation went wrong. I expect to end-up with a running

console/shell.

What I did and what happened is detailed here:

$ ls

    image/       qconf-override.mk   stage/

    hide-gnu.sh  qemu-minimal.build  trunk/

$ sudo su

# ./hide-gnu.sh trunk

    Locating GNUmakefile's in trunk/

    Touching trunk/utils/t/tcpdump/win32/prj/Makefile.dnm

# cd trunk

# svn info

    URL: http://community.qnx.com/svn/repos/core_networking/trunk

    Repository Root: http://community.qnx.com/svn/repos/core_networking

    Repository UUID: 79cfb829-523c-0410-9886-d489a5a0dd87

    Revision: 764

    Node Kind: directory

    Schedule: normal

    Last Changed Author: seanb@qnx.com

    Last Changed Rev: 764

    Last Changed Date: 2009-01-27 21:47:03 +0100 (Tue, 27 Jan 2009)

# make OSLIST=nto CPULIST=x86 hinstall

    (... lot of output)

# ls ../stage

    usr

# ls ../stageetc

    openssl

# make OSLIST=nto CPULIST=x86 install

    (... lot of output)

# cd ..

# exit

$ ls stage

    etc  usr  x86

$ ls stageetc

    openssl

$ mkifs qemu-minimal.build image/qemu-minimal.ifs

    Warning: Host file 'npm-tcpip.so' missing.

    Warning: Host file 'io-net' missing.

$ dinit -H -R -f image/qemu-minimal.ifs image/qnx_on_qemu.img

    All existing files on image/qnx_on_qemu.img will be lost!  Are you

sure (y or n) ? y

    Using loader /opt/qnx640/target/qnx6/x86/boot/sys/ipl-diskpc2-flop

    Disk 'image/qnx_on_qemu.img' contains 2097152 blocks (1048576K).

$ dinit -B pc2 image/qnx_on_qemu.img

    Using loader /opt/qnx640/target/qnx6/x86/boot/sys/ipl-diskpc2

$ qemu -hda image/qnx_on_qemu.img -k fr-ch

The screen shot (qemu) is attached to this mail (basically says "unable

to start ..." and "unable to access dev/...").

- Does the problem come from the missing files ('npm-tcpip.so' and

'io-net': I only found trunk/sys/dev_qnx/shim/x86/dll/io-net.o) ? (I

don't think so, but that's the only clue I get)

- Is it the 'qemu-minimal.build' from

[NeutrinoAsGuestInQEMU/qemu-minimal.build] that needs to be fixed?

- Or is there anything above that looks strange to you?

- I found no information about that 'stageetc' directory that was

created by 'make hinstall' , I tried to link it inside 'stage/etc' but I

got no better results.

Thanks for any help.

Pietro

_______________________________________________

General

http://community.qnx.com/sf/go/post20977

post20977: running QNX with "qemu-minimal.build" problem

Pietro Descombes — Thu, 29 Jan 2009 12:31:24 GMT

Hi everyone,

I'm trying to run QNX (source code) on QEMU but either the compilation,

or the image creation went wrong. I expect to end-up with a running

console/shell.

What I did and what happened is detailed here:

$ ls

    image/       qconf-override.mk   stage/

    hide-gnu.sh  qemu-minimal.build  trunk/

$ sudo su

# ./hide-gnu.sh trunk

    Locating GNUmakefile's in trunk/

    Touching trunk/utils/t/tcpdump/win32/prj/Makefile.dnm

# cd trunk

# svn info

    URL: http://community.qnx.com/svn/repos/core_networking/trunk

    Repository Root: http://community.qnx.com/svn/repos/core_networking

    Repository UUID: 79cfb829-523c-0410-9886-d489a5a0dd87

    Revision: 764

    Node Kind: directory

    Schedule: normal

    Last Changed Author: seanb@qnx.com

    Last Changed Rev: 764

    Last Changed Date: 2009-01-27 21:47:03 +0100 (Tue, 27 Jan 2009)

# make OSLIST=nto CPULIST=x86 hinstall

    (... lot of output)

# ls ../stage

    usr

# ls ../stageetc

    openssl

# make OSLIST=nto CPULIST=x86 install

    (... lot of output)

# cd ..

# exit

$ ls stage

    etc  usr  x86

$ ls stageetc

    openssl

$ mkifs qemu-minimal.build image/qemu-minimal.ifs

    Warning: Host file 'npm-tcpip.so' missing.

    Warning: Host file 'io-net' missing.

$ dinit -H -R -f image/qemu-minimal.ifs image/qnx_on_qemu.img

    All existing files on image/qnx_on_qemu.img will be lost!  Are you

sure (y or n) ? y

    Using loader /opt/qnx640/target/qnx6/x86/boot/sys/ipl-diskpc2-flop

    Disk 'image/qnx_on_qemu.img' contains 2097152 blocks (1048576K).

$ dinit -B pc2 image/qnx_on_qemu.img

    Using loader /opt/qnx640/target/qnx6/x86/boot/sys/ipl-diskpc2

$ qemu -hda image/qnx_on_qemu.img -k fr-ch

The screen shot (qemu) is attached to this mail (basically says "unable

to start ..." and "unable to access dev/...").

- Does the problem come from the missing files ('npm-tcpip.so' and

'io-net': I only found trunk/sys/dev_qnx/shim/x86/dll/io-net.o) ? (I

don't think so, but that's the only clue I get)

- Is it the 'qemu-minimal.build' from

[NeutrinoAsGuestInQEMU/qemu-minimal.build] that needs to be fixed?

- Or is there anything above that looks strange to you?

- I found no information about that 'stageetc' directory that was

created by 'make hinstall' , I tried to link it inside 'stage/etc' but I

got no better results.

Thanks for any help.

Pietro

post16637: RE: Ques/Sugges-tions

Colin Burgess — Mon, 17 Nov 2008 12:57:08 GMT

QNX6 can host qemu, but as yet we don't support the (Intel or AMD)VT or kqemu acceleration techniques.

-----Original Message-----

From: Gottfried Czech [mailto:community-noreply@qnx.com]

Sent: Mon 11/17/2008 7:47 AM

To: general-qemu

Subject: Re: Ques/Sugges-tions

Hi,

I need to run a Windows XP on a Neutrino Host System to use Windows for a visualisation of my Realtime Application. QNX Support

told me about Qemu. But I do not find a fitting combination there.

Does this constellation (QNX Neutrino host, running Qemu, hosting Windows XP as guest OS) exist.

Or are there other feasible solutionsl.

Many Thanks

Gottfried Czech

_______________________________________________

General

http://community.qnx.com/sf/go/post16636

post16636: Re: Ques/Sugges-tions

Gottfried Czech — Mon, 17 Nov 2008 12:47:45 GMT

Hi,

I need to run a Windows XP on a Neutrino Host System to use Windows for a visualisation of my Realtime Application. QNX Support

told me about Qemu. But I do not find a fitting combination there.

Does this constellation (QNX Neutrino host, running Qemu, hosting Windows XP as guest OS) exist.

Or are there other feasible solutionsl.

Many Thanks

Gottfried Czech

post15489: Re: QNX on non-x86 qemu targets

Yao Zhao(deleted) — Fri, 24 Oct 2008 02:15:51 GMT

qemu-system-ppc only supports a couple of boards, I can only boot PREP currently with Linux target, of course Linux host too.

taihu and ref405ep can't work with u-boot for now. didn't try mac yet because no interest.

I didn't find bsp for taihu so only ref405ep is a choice, but seems no ipl support either, so u-boot is one choice but qemu didn't support it completely yet, I need to read more to see whether it is worth or I can patch for qemu. a lot of code need to read:(

but seems someone used another ppc emulator to boot u-boot, then it is easy to most embedded OSes:)

post15488: Re: Networking with linux host

Yao Zhao(deleted) — Fri, 24 Oct 2008 02:04:50 GMT

I am using kvm and qemu on my Linux host.

/usr/bin/qemu -boot c -m 256 -hda '/home/yao/workspace/vm/qnx/qnx632/qnx632_x86' -cdrom  '/home/yao/workspace/vm/qnx/qnx632/newbios.iso' -net nic,vlan=1,macaddr=00:01:02:03:04:07 -net tap,vlan=1,ifname=vmtap1 -localtime &

my host

vmtap1    Link encap:Ethernet  HWaddr 00:ff:48:db:fc:2e

          inet addr:172.20.0.1  Bcast:172.20.255.255  Mask:255.255.0.0

          inet6 addr: fe80::2ff:48ff:fedb:fc2e/64 Scope:Link

          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1

          RX packets:8 errors:0 dropped:0 overruns:0 frame:0

          TX packets:46 errors:0 dropped:0 overruns:0 carrier:0

          collisions:0 txqueuelen:500

          RX bytes:2736 (2.6 KB)  TX bytes:6298 (6.1 KB)

so I only ifconfig en0 172.20.0.2/16 in my qnx target then route add default 172.20.0.1.

if you have nat setup in your host then you should be able to access Internet via your Linux host.

what is your host interface macaddr?

post13368: Re: can't locate pci server

Alex Chapiro — Sat, 13 Sep 2008 03:32:32 GMT

I think it's explained in the article published in this project (Neutrino as a guest). Problem is that diskboot fails to launch pci-bios. Recommended after installation add pci-bios command to startup script section of mkifs script and rebuild image.

post12985: can't locate pci server

Ricardo Perrone — Mon, 08 Sep 2008 03:27:46 GMT

Hi,

In last pre-release qnx 6.4, the boot process show me a message "can't locate pci server", and when try to use Photo GUI the usb mouse doesn't work. It appears to be "freeze". Are there some special parameters to be set before launch qemu with qnx 6.4?

thanks for any help

post12260: QNX on non-x86 qemu targets

Geneviève Bastien — Fri, 22 Aug 2008 16:17:16 GMT

Hi all,

I'd like to build a small test network of QNX x86 and PowerPC machines using qemu.

The wiki says that the startup for non-x86 targets is a bit different. Does anyone know how to make it work? (I am new to qemu) And is there a build file for a minimal ppc build on qemu?

Thanks

post11616: Networking with linux host

Bonnefoy Sébastien(deleted) — Mon, 11 Aug 2008 12:31:33 GMT

Hi,

I'm trying to make the network between a qnx 6.3.0 (as qemu or kvm target) and linux host to work.

I used vde2 (a virtual switch) to make the network connection and dnsmasq as dhcp server.

The host obtains an IP address but then doesn't answer ARP requests. I managed to telnet the localhost qnx target on this interface but nothing more. Tcpdump shows the DHCP request and answer, but the the host arp requests are ignored from QNX.

Does anyone have a similar experience or managed to set up a network between QNX in Qemu or kvm and the outside world? It more information is needed, just ask.

Thanks

post8074: Re: Qnx 632 can run on kvm

dragon linux — Thu, 15 May 2008 02:55:15 GMT

it is doing

1: cmp %es:108,%dx

je 1b

post8072: Re: Qnx 632 can run on kvm

dragon linux — Thu, 15 May 2008 01:58:58 GMT

Thanks Colin!

It did fix the pci-bios problem but If I use more than 1 cpu then it won't boot.

post8029: Re: Qnx 632 can run on kvm

Colin Burgess — Wed, 14 May 2008 13:04:45 GMT

There was a bug in bios.boot - attached is a new one.

Cheers,

Colin

dragon linux wrote:

>

> I tried Qnx632 x86only image on my Linux with kvm and it works. But

> just not sure why pci-bios doesn't work in the default ifs image and

> it will work I manually run it: pci-bios.

>

> I have not tried to use an image without diskboot, in theory it should

> work with pci-bios.

>

>

>

> _______________________________________________

> General

> http://community.qnx.com/sf/go/post8016

>

post8017: Re: Qnx 632 can run on kvm

dragon linux — Wed, 14 May 2008 03:50:42 GMT

If I tried smp then it will fail too with cd rom image.

post8016: Qnx 632 can run on kvm

dragon linux — Wed, 14 May 2008 03:49:22 GMT

I tried Qnx632 x86only image on my Linux with kvm and it works. But just not sure why pci-bios doesn't work in the default ifs image and it will work I manually run it: pci-bios.

I have not tried to use an image without diskboot, in theory it should work with pci-bios.

post1647: Re: Ques/Sugges-tions

Zhe Fang — Thu, 27 Sep 2007 16:10:38 GMT

> I'm honestly not sure how difficult it would be to make an nto-user mode, and

> it's probably beyond the scope of my work term here (3 months left as a co-op

> student). I wouldn't discount the possibility in the future.

I see. Let's "count" a possibility here:

The basic idea of user mode emulation in QEMU is: make a CPU cycle which can/must catch every privillaged instructions. So...IMO there're 3 key points:

1. Map the ELF binary correctly into memory (then make a thread for it, we'll monitor the thread later)

2. Handling kernel calls/ signals (a microkernel don't have much... but ABI, ABI, ABI... lots of platforms nto's support! and endian convert of course)

(till now, a simple main() program can run)

3. Special dealing with thread calls

Best Regards,

Zhe

post1641: RE: Ques/Sugges-tions

Frederic Plante — Thu, 27 Sep 2007 12:48:44 GMT

Anybody interested in writing a short tutorial on how to use QEMU to run QNX

as a target? We would post on the community home page.

post1640: Re: Ques/Sugges-tions

Sada Murugan — Thu, 27 Sep 2007 12:18:05 GMT

> Hi Sada Murugan and others,

> Have you considered to enhance QEMU to run QNX as a target? QEMU lacks a "PnP

> BIOS" which cause the PnP device drivers including network adapters

> unfunctional in QNX(as a target).

The Neutrino installer CD doesn't make a suitable test target configuration for running on QEMU because of the lack of PnP BIOS and drive space requirements.  However, since QNX is highly configurable, it's possible to set up a system which runs nicely on QEMU.  The network drivers DO work, however, they won't start properly from the default CD.  I'm quite sure that the wiki page (on the OS project under debugging) describes how to manually start pci-bios, and restart io-net to get user-mode networking after the boot sequence.

Full networking that can accept incoming connections and communicate between instances of QEMU requires a TAP interface, which isn't implemented yet for QNX.  A networking guru here is looking into it.

Currently, the best solution is to make proper buildfiles for QEMU, and set up raw disk images.  The dinit utility can be used on raw disk images to make custom test systems for QEMU - the non-PnP BIOS shouldn't be a problem once I figure this all out.

There has been some talk about writing enhancements for QEMU, like a port of kQEMU and a graphical front end - but this is longer term and not as critical right now.  There will certainly be a few active project like that in time.

> And what about nto-user? It should be very interesting to make a user mode

> emulator working under such a pure microkernel.

I'm honestly not sure how difficult it would be to make an nto-user mode, and it's probably beyond the scope of my work term here (3 months left as a co-op student).  I wouldn't discount the possibility in the future.

For now, I'm trying to find a really good setup for qemu and sort out the logistics of making bootable disk images.  Also, non-x86 targets require a kernel image separate from a disk, and I haven't had success with our kernel yet, but I'm hoping to within a few days.

As always, I will update the wiki once I have made some progress.

Regards

-SM

post1639: Ques/Sugges-tions

Zhe Fang — Thu, 27 Sep 2007 03:35:21 GMT

Hi Sada Murugan and others,

Have you considered to enhance QEMU to run QNX as a target? QEMU lacks a "PnP BIOS" which cause the PnP device drivers including network adapters unfunctional in QNX(as a target).

And what about nto-user? It should be very interesting to make a user mode emulator working under such a pure microkernel.

Best regards,

Zhe

post1416: Re: I had commit privilages, and then I lost them

Frederic Plante — Wed, 19 Sep 2007 17:51:47 GMT

I changed the privileges to match what's on other projects and by default members are not committers. Because you were in the middle of a commit, I temporarily granted you committer privileges.

post1413: I had commit privilages, and then I lost them

Sada Murugan — Wed, 19 Sep 2007 17:34:33 GMT

I was granted svn access this morning, and I was partway done committing my changes so far, but now I no longer have commit privileges.

This is what happens:

smurugan@sada:~/dev/qemu-working/qemu/trunk$ svn ci --username SMurugan@qnx.com -F ../svn-commit.8.tmp

svn: Commit failed (details follow):

svn: MKACTIVITY of '/svn/repos/qemu/!svn/act/0d93bfd0-c66e-4abb-9947-921109b93b53': 403 Forbidden (http://community.qnx.com)

I wasn't done all of my commits yet. What happened?

post1393: svn best practice

Sada Murugan — Wed, 19 Sep 2007 14:01:21 GMT

As soon as I have the proper privileges, I'll import my code into svn here.

Should I use what I currently have as a baseline, or should I just use the base 0.9.0 release?

I favour the latter, and then I will commit changes one fix at a time, so that there is a recorded explanation for why I have done certain thing that are not obvious.

I'm very new to using svn, and so far I have only modified single files and committed them back, so bear with me if I screw something up, although I'll try not to.

post1390: Welcome to QEMU

Sada Murugan — Wed, 19 Sep 2007 13:38:01 GMT

Hi all.  I'm a co-op student with QNX and have been working on our port of QEMU.

It seems that some community members know more than I do about QNX, but I haven't been working with it for very long.

Anyway.  My first question is, which port is that posted binary release?  Is that from my patch that I posted on here, or is it your old port Alex?  It seems to have all the same behaviour, buts and fixes as my current port, but I'm not sure.

We'll have to share what we have so far.

My current major issue is that the QNX installer, finstall, reads all partitions on raw images as zero in size, and refuses to install on them.  This works fine with some other image types, like qcow2, but growable images like that are significantly slower than using raw images.  I have one installer CD that works properly, but it's QNX internal.