Hello. At my organization, we would prefer to use QEMU with a bridged tap network backend rather than the user-mode SLIRP backend because this allows us to dial into the VM from the host. I had written a bbclass in our layer to extend qemuboot-xilinx.bbclass and edit the qemuboot.conf file to make this change, and this had worked for us in rel-v2021.2.
Now I am migrating us to rel-v2022.1 and this no longer works because the qemu-oe-bridge-helper native binary is not compiled. I found a change with commit hash dc2f1f19a5e8d3e88e49b168bad8290f7c871dc5 which, among other things, suppresses he compilation of the qemu-oe-bridge-helper tool and only compiles a tunctl utility. I'm scratching my head trying to figure out how I should deal with this, and what was the intention? Am I to take it that using QEMU network backends other than what's hard-coded by Xilinx recipes is simply not supported by Xilinx Yocto layers? Or if it is, what would be the recommended approach to enable the bridged tap backend? Thanks, Corey
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#5040): https://lists.yoctoproject.org/g/meta-xilinx/message/5040 Mute This Topic: https://lists.yoctoproject.org/mt/93070424/21656 Group Owner: [email protected] Unsubscribe: https://lists.yoctoproject.org/g/meta-xilinx/unsub [[email protected]] -=-=-=-=-=-=-=-=-=-=-=-
