Closed JackKuo-tw closed 3 years ago
@JackKuo-tw we updated our manager go.sh
syntax, so if you just type ./go.sh
, you will see a few options. This one should fix your problem though.
./go.sh -k 1 -n 0xF0 -m 0,1,2,3 -s stdout -c
. The manager explicitly needs more cores than usual for shared core, so this will give the manager 4 cores for example (-m 0,1,2,3
). This worked for me on a normal non-qemu environment, hopefully it helps you.
@kevindweb Thanks for your help. But another problem is that my NIC doesn't have 2 ports...
Can you take a screenshot of your dpdk setup? Do you have a port initialized? The command I sent is set for 1 port, so you might not have set up the port correctly? If you want to test without a NIC bound, just set -k 0
instead.
@kevindweb You're right. Afer with -k 0
arg, it works! Thanks a lot!
And here is the DPDK setup:
Bug Report
Current Behavior
My ONVM is running in KVM + QEMU with 2 e1000 network adaptors. Everything is fine except for the shared cores feature.
Expected behavior/code
Run the manager as normal.
Steps to reproduce
If this problem cannot be reproduced, I can provide the qcow2 image.
Environment
Possible Solution
None.
Additional context/Screenshots
Invoking manager command:
Invoking QEMU command: