Hello All,

Thanks for the inputs.

I have tried following steps as per the suggestions given -

1) As Berto suggested to use -  *tcpdump -e -i virbr0 ether host
00:0a:35:02:78:10 * while pinging from host to guest (Not able to ping
guest from host or host from guest)

Output ->  tcpdump: verbose output suppressed, use -v or -vv for full
protocol decode
  listening on virbr0, link-type EN10MB (Ethernet), capture size 262144
bytes
  ^C
  0 packets captured
  0 packets received by filter
  0 packets dropped by kernel

2) When used the Tap interface with following qemu command line -


* qemu-system-aarch64 -M xlnx-zcu102 -m 8G -serial mon:stdio -display none
-device loader,file=/home/asif/qemu_aarch64/ifs/aarch64/QNX_IFS,cpu-num=0
-nic
type=tap,id=net0,script="./qemu-tap-up.sh",downscript="./qemu-tap-down.sh"
-nographic *
Please find attached the qemu-tap-up.sh and qemu-tap-down.sh.

I can see in my HostOS tap0 connected to virbr0 when checked brctl show -

$* brctl show*
bridge name bridge id STP enabled interfaces
virbr0 8000.52540021de01 yes tap0
virbr0-nic

I observed following warning before Guest kernel loads -

qemu-system-aarch64: warning: nic cadence_gem.1 has no peer
qemu-system-aarch64: warning: nic cadence_gem.2 has no peer
qemu-system-aarch64: warning: nic cadence_gem.3 has no peer

And in GuestOS if i do ifconfig -

# *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
address: 00:0a:35:02:78:10
media: Ethernet 100baseTX full-duplex
status: active
inet 192.168.122.2 netmask 0xffffff00 broadcast 192.168.122.255
inet6 fe80::20a:35ff:fe02:7810%xzynq0 prefixlen 64 scopeid 0x11

But i am not able to ping guest from host.

Also if use following qemu command line with virtio-net device -

* qemu-system-aarch64 -M xlnx-zcu102 -m 8G -serial mon:stdio -display none
-device
loader,file=/home/asif/qemu_aarch64/ifs/aarch64/QNX_IFS.bin,cpu-num=0
                -nic
type=tap,id=net0,script="./qemu-tap-up.sh",downscript="./qemu-tap-down.sh"
-device virtio-net-device,netdev=net0,mac=$MACADDR -nographic *

I am getting following error -

qemu-system-aarch64: -device
virtio-net-device,netdev=net0,mac=52:54:00:d0:be:9a: No 'virtio-bus' bus
found for device 'virtio-net-device'

Can you please suggest if any change in the qemu command line is needed to
enable networking between host and guest ?


Regards
Asif





On Wed, Jun 9, 2021 at 3:17 PM Peter Maydell <peter.mayd...@linaro.org>
wrote:

> On Wed, 9 Jun 2021 at 08:41, Thomas Huth <th...@redhat.com> wrote:
> > Thus you might want to try "-nic" instead of "-netdev", but as far as I
> can
> > see, the xlnx-zcu102 does not have any NIC on board by default?
>
> It should do -- the xlnx-zcu102 board uses a TYPE_XLNX_ZYNQMP
> SoC object, which creates four TYPE_CADENCE_GEM NIC objects.
>
> I can never remember the new syntax to use to connect board-created
> network devices to the net backend options...
>
> thanks
> -- PMM
>

Attachment: qemu-tap-down.sh
Description: application/shellscript

Attachment: qemu-tap-up.sh
Description: application/shellscript

Reply via email to