You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Mar 2, 2022. It is now read-only.
What I'm having in mind is to just support running Lego OS components on virtual machines separately and each of them talks to others using an Eth driver like e1000e and then throughout the virt-io in the host. For example in a 1P-1M-1S config we work like pcomponent -> eth -> virt-io -> host -> virt-io -> eth -> mem-component or storage-component
Do you think this is something we can achieve with some minimal implementation effort?
Thanks,
Alireza
The text was updated successfully, but these errors were encountered:
After enabling e1000 driver, I think you could use socket directly via lwip (/net/lwip/api/sockets.c). I've tested this long time ago. So I can't guarantee that with the current master version it still works. But you can first try this instead of building your own network stack.
Yiying
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Hello @lastweek
I'm interested to replace IB with Eth.
What I'm having in mind is to just support running Lego OS components on virtual machines separately and each of them talks to others using an Eth driver like e1000e and then throughout the virt-io in the host. For example in a
1P-1M-1S
config we work likepcomponent -> eth -> virt-io -> host -> virt-io -> eth -> mem-component or storage-component
Do you think this is something we can achieve with some minimal implementation effort?
Thanks,
Alireza
The text was updated successfully, but these errors were encountered: