...
Or if using PetaLinux on a Versal ACAP Versal Adaptive SoC project:
Code Block | ||||
---|---|---|---|---|
| ||||
petalinux-boot --qemu --prebuilt 3 --qemu-args "-net nic,netdev=eth0 -netdev user,id=eth0,hostfwd=tcp::1114-:22 -net nic" |
...
Setting the TAP network for QEMU
The TAP networking backend makes use of a TAP networking device in the host. It offers very good performance and can be configured to create virtually any type of network topology.
Unfortunately, it requires configuration of that network topology in the host which tends to be different depending on the operating system you are using. Generally speaking, it also requires that you have root privileges.[1]
Note |
---|
You might need to install |
...
Code Block | ||||
---|---|---|---|---|
| ||||
petalinux-boot --qemu --kernel --qemu-args="-net nic -net nic -net nic -net nic -net tap,ifname=tap0,script=no,downscript=no" |
Or if using Versal ACAP Versal Adaptive SoC in a PetaLinux project:
Code Block | ||||
---|---|---|---|---|
| ||||
petalinux-boot --qemu --kernel --qemu-args="-net nic -net nic -net tap,ifname=tap0,script=no,downscript=no" |
...
NFS allows us to share a directory on one device with other devices on the network. NFS only offers close-to-open cache coherence.
This means that the only guarantee provided by the protocol is that if you close a file in a client A and then open the file in another client B, client B will see client A's changes.862847290[2]
Prebuilt PetaLinux BSPs have a rootfs and a Linux kernel which are loaded with NFS options. So, no rebuilding/configuring is needed for NFS. Below are simple steps to setup NFS with QEMU on a Linux host:
...