On 8/16/22 6:15 PM, Thompson, Corey via lists.yoctoproject.org wrote:
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?

When using rel-v2022.1, we have only tested the configuration exactly as it is defined.

However, if you look at "honister-next", you should see we have reworked this. I use both tun and slirp regularly, I can't say I've tried to use tap. So if something is missing that is required for it to work, can you please open a bug on github.com/Xilinx/meta-xilinx and explain _exactly_ how you would expect to setup and use it?

(I'm hoping tomorrow I'll finally move honister-next to honister...)

I don't have much experience with a tap interface, so I'll need some guidance to try to get it to work properly.

--Mark

Thanks,
Corey





-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#5041): 
https://lists.yoctoproject.org/g/meta-xilinx/message/5041
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]]
-=-=-=-=-=-=-=-=-=-=-=-

Reply via email to