-
Hi, Thanks for the great software, I managed vrnetlab containers manually before and found this to make network simulation way easier! :-) I can start ~5 devices at once with no issues, however if I try the same with about ~25 vQFX and vSRX devices the boot of each appliance will stall at about this point:
I don't know why this happens, as the host machine has plenty resources:
This memory usage is at the point of the lockup and there are no OOM messages in the kernel log. I found that starting the individual vrnetlab containers with a delay in between helps the lab to come up. Is such a "one by one" container startup possible with Containerlab? Of course, any ideas as to why this lockup happens would be appreciated as well! The machine is using nested virtualization using KVM, but the host machine has plenty free resources as well. |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 2 replies
-
Possible, but not automatically. You can configure |
Beta Was this translation helpful? Give feedback.
Possible, but not automatically. You can configure
startup-delay
for individual nodes.