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

./onvm/go.sh 1,2,3 1 -s stdout -a 0x7f000000000 stop running #100

Closed
XinShuYang opened this issue Apr 12, 2019 · 9 comments · Fixed by #197
Closed

./onvm/go.sh 1,2,3 1 -s stdout -a 0x7f000000000 stop running #100

XinShuYang opened this issue Apr 12, 2019 · 9 comments · Fixed by #197
Labels

Comments

@XinShuYang
Copy link

Bug Report

Current Behavior
I try to build a mtcp container on ONVM, but the mmap function failed. I found this issue has been mentioned in mtcp onvm install guides. But when I try this go.sh command, it stops running at "APP: Stats verbosity level = 1" .(in screenshots)
Screen Shot 2019-04-12 at 10 06 19 AM

Steps to reproduce
cd /root/openNetVM
./onvm/go.sh 1,2,3 1 -s stdout -a 0x7f000000000

Environment

  • OS: Ubuntu 14.04.1 LTS (CloudLab 220g2)
  • onvm version: latest ONVM develop branch

Possible Solution
I try to add a cpu mask, and then it can work.
./onvm/go.sh 1,2,3 1 0xF8 -s stdout -a 0x7f000000000

Additional context/Screenshots
Screen Shot 2019-04-12 at 10 07 50 AM

@koolzz
Copy link
Member

koolzz commented Apr 12, 2019

To confirm, does this ./onvm/go.sh 1,2,3 1 0xF8 -s stdout -a 0x7f000000000 or even better (./onvm/go.sh 1,2,3 1 0xF8 0 -s stdout -a 0x7f000000000 ) work fine? The mtcp examples don't have the updated onvm_mgr args, the cpu mask for NFs is a required arg. I'll submit a quick pr to mtcp to fix that.

@XinShuYang
Copy link
Author

./onvm/go.sh 1,2,3 1 0xF8 0 -s stdout -a 0x7f000000000 doesn't work. I have tested the epserver in opennetvm-dev latest version and it works. (using ./onvm/go.sh 1,2,3 1 0xF8 -s stdout -a 0x7f000000000)

@koolzz
Copy link
Member

koolzz commented Apr 12, 2019

Oh sorry it should be ./onvm/go.sh 1,2,3 1 0 -s stdout -a 0x7f000000000

@koolzz
Copy link
Member

koolzz commented Apr 12, 2019

Could you verify that one, there is technically no reason to use 0xf8 as mtcp is supposed to do it's own core managing

@XinShuYang
Copy link
Author

./onvm/go.sh 1,2,3 1 0 -s stdout -a 0x7f000000000 can start the ONVM, but when I run the mtcp(epserver) it failed with " Cause: There are no cores available for this NF".
Using ./onvm/go.sh 1,2,3 1 0xF8 -s stdout -a 0x7f000000000 doesn't have this problem.

@XinShuYang
Copy link
Author

Screen Shot 2019-04-12 at 10 58 34 AM

@koolzz
Copy link
Member

koolzz commented Apr 12, 2019

As I see, yeah the standard core allocation does not make sense with this as we're not actually using the cores from the manager argument for mtcp but if there is nothing there the NF initialization complains.

Thank you for testing this! I'll add some notes regarding the issue and submit the mtcp pr

@koolzz
Copy link
Member

koolzz commented Apr 16, 2019

  • Submitted a PR for mtcp
  • Still need a README note for onvm

@kevindweb kevindweb linked a pull request Mar 22, 2020 that will close this issue
@kevindweb
Copy link
Contributor

Should have been closed with #197

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants