Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Remove #VMs <= 256 limit #48

Open
sriramy opened this issue Aug 17, 2023 · 1 comment
Open

Remove #VMs <= 256 limit #48

sriramy opened this issue Aug 17, 2023 · 1 comment
Labels
low Low priority

Comments

@sriramy
Copy link
Collaborator

sriramy commented Aug 17, 2023

At some point the limit #VMs <= 256 may be addressed (not a limitation in my setups yet), but the limit is actually 100 since gnu screen have a max-limit of 100. Now, that can be configured ad build-time, but better to seek an alternative to screen, like a simple pipe or something

@uablrek
Copy link
Contributor

uablrek commented Aug 19, 2023

IMO this should have very low prio, and only be implemented if a real need arises.

It hits hard on the entire network setup and several (convenient) assumptions. A test that really needs >256 nodes can most likely be implemented in an ovl, albeit a pretty obscure one with hooks and things.

@sriramy sriramy added the low Low priority label Aug 19, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
low Low priority
Projects
None yet
Development

No branches or pull requests

2 participants