-
Notifications
You must be signed in to change notification settings - Fork 277
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
SONiC VM with vrnetlab does not come up healthy #2365
Comments
Did you check docker logs for sonic node? |
Due to some issue with config or other, VM gets shutdown after few syncd/swss restart I think. However, there isn't any log captured outside of the VM to see what went wrong. Is that something containerlab can capture? root@sonic-1:/# ps -ef |
Upon qemu exit (for whatever reason, yet to troubleshoot whats wrong with config or sonic) root@sonic:~#' clab docker continues to run with above message.. its keep printing above.. |
maybe first thing to try is to remove any startup config and see if the node comes up |
yeah. tried removing startup config as well.. vm doesnt stay up beyond 7-10 minutes.. it comes up fine and even bgp peers are established (if startup config given).. but it disappears (entire vm) after sometime...... same image runs fine with sonic-mgmt env.... to confirm, there is no issue with image and ofcourse, no config at all. |
in my case, issue is due to memory.
4GB isn't enough.. Not just in topo config, launch.py (in vrnetlab as well)
Also, self.num_nics is set to 10 explains why max ethernet interfaces works till eth10.. and not beyond that.. |
Build: 20241224.7
Commit: ea4ccc0377
Version: 202405
Issue:
Waited over 10 minutes and nothing happens, Also when I console in there is nothing running inside sonic-vrnet container
Step-1: Built SONiC image
The text was updated successfully, but these errors were encountered: