Netowrking in QEMU with xilinx-zcu102 machine

[xilinx]

Netowrking in QEMU with xilinx-zcu102 machine

[asifsid-32]

The ZynqMP SOC has 4 Ethernet MAC's. On the ZCU102 board, GEM3 is the one to use.
You'll need to connect your bridge to the GEM3 model by adding 3 -net nic command-line options.

eg.:

-net nic,model=cadence_gem -net nic,model=cadence_gem -net nic,model=cadence_gem,netdev=net0

Best regards,
Edgar

Hii Edgar,

Thanks for the input. The above command options Worked.

I am executing the qemu command as follows -

qemu-system-aarch64 -M xlnx-zcu102 -m 8G -serial mon:stdio -display none
-device loader,file=QNX-IFS.bin,cpu-num=0 \
-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

After booting the guest OS following is the output of ifconfig -

lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> mtu 33136
inet 127.0.0.1 netmask 0xff000000
inet6 ::1 prefixlen 128
inet6 fe80::1%lo0 prefixlen 64 scopeid 0x1

xzynq0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
capabilities rx=7<IP4CSUM,TCP4CSUM,UDP4CSUM>
capabilities tx=0
enabled=0
address: 00:00:00:00:00:00
media: Ethernet autoselect (1000baseT full-duplex,flowcontrol)
status: active
inet 10.0.2.15 netmask 0xffffff00 broadcast 10.0.2.255
inet6 fe80::401a:a90e:79f:a326%xzynq0 prefixlen 64 scopeid 0x11

I am able to transfer files successfully between host os linux and guest using SCP when ssh is launched.

But i am not able to ping from guest to host or host to guest. Also if i want to debug a qnx application using gdb remote debug it does not work.
Is it because of QEMU user networking(SLIRP) and it does not support other Network services ?

I tried following the steps given in the "Enabling ping in the guest, on Linux hosts" section from the link https://wiki.qemu.org/Documentation/Networking#User_Networking_.28SLIRP.29
but it did not work.

Can you please suggest what changes are required in qemu command line so that i can ping from guest to host or host to guest as this is required for remote debug.

Regards
Asif

[FaiqueAli]

Hi everyone,
I am also running into the same issue did anyone find a solution for this?
when I hit the command to create a VM, the terminal hangs with the following error...

qemu-system-aarch64: warning: hub 0 is not connected to host network

looking for further information thanks :)

[edgarigl]

The ZynqMP SOC has 4 Ethernet MAC's. On the ZCU102 board, GEM3 is the one to use.
You'll need to connect your bridge to the GEM3 model by adding 3 -net nic command-line options.

eg.:

-net nic,model=cadence_gem -net nic,model=cadence_gem -net nic,model=cadence_gem,netdev=net0

Best regards,
Edgar

[shizhuang-li]

Hello,Edgar and Asif, Your discussion is very interesting, I am also trying to build a QNX os on qemu recently, I tried Asif's method, as shown below:
qemu-system-aarch64 -M xlnx-zcu102 -m 8G -serial mon:stdio -device loader,file=/root/xlinxbsp/images/QNX-IFS,cpu-num=0 -nographic -global xlnx,zynqmp-boot.cpu-num=0 -global xlnx,zynqmp-boot.use-pmufw=true
The QNX-IFS file is the xlnx-zcu102 BSP package I downloaded from the QNX software center.When I run the above command, nothing is displayed, and the command cannot be terminated, only the kill command can be used to end the process.

I'm guessing that there may be a problem with my QNX-IFS file, but I'm not sure what the specific problem is? So I would like to ask how to solve this problem, and how did you get the QNX-IFS file?

Regards
Shizhuang.li

[codectq92]

Hello,Edgar and Asif, Your discussion is very interesting, I am also trying to build a QNX os on qemu recently, I tried Asif's method, as shown below: qemu-system-aarch64 -M xlnx-zcu102 -m 8G -serial mon:stdio -device loader,file=/root/xlinxbsp/images/QNX-IFS,cpu-num=0 -nographic -global xlnx,zynqmp-boot.cpu-num=0 -global xlnx,zynqmp-boot.use-pmufw=true The QNX-IFS file is the xlnx-zcu102 BSP package I downloaded from the QNX software center.When I run the above command, nothing is displayed, and the command cannot be terminated, only the kill command can be used to end the process. I'm guessing that there may be a problem with my QNX-IFS file, but I'm not sure what the specific problem is? So I would like to ask how to solve this problem, and how did you get the QNX-IFS file?

Regards Shizhuang.li

I have the same question, did you sloved it now?