Make TCP interfaces compatible. #3
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
It can surely silence the compiler complaint. But it may not work with multiple vCPU threads at one node. Do you boot GiantVM successfully? |
|
No. Although I am not sure if I am booting the system correctly. I currently have only two nodes, with one VCPU per node.
As it can be seen, both machines connect. However, the Qemus do not make any further progress. Everything freezes. Runing dmesg on another terminal, I get this output related to kvm. On the master machine: On the remote machine: |
|
I don't know what's going wrong for your code. But you need to make sure the commands work well for vanilla QEMU-KVM (without -local-cpu). There's a variable kvm_dsm_debug_verbose in dsm.c which enables more log. And I can share you with my script: |
|
Hi, |
|
You can deploy GiantVM on the same machine with different port numbers (hard-coded) or different machines. |
|
Can you show me how to hard-code different port numbers? |
|
Okay. I think I figured it out. The ports are hard-coded in QEMU's code (ports 40000 and 40001). I have setup both ports to same ip address (127.0.0.1 == localhost) and run the two QEMUs. I am getting the following error: |
|
What do you mean by 'setup both ports to the same ip addr'? The error message is generated after the failure of |
|
Sorry for the bad phrasing... By that I mean I have set NODE0_IP and NODE1_IP to the same value: Qemu code will then automatically assign diffrent ports for each qemu: |
|
I guess it's caused by busy ports. E.g., previous QEMU doesn't exit normally. |
|
Good news, I am able to boot GiantVM (with both Qemus on the same machine). The "io-router problem was due to a misconfiguration of my shell script. However, now I am hitting a bug further in the execution. There are two kernel Oops produced by the kernel. The full log is as follow: |
|
It looks like the guest OS has executed quite a few code successfully. The assertion failure at |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is a proposed patch to get the TCP working. It simply redefines the "struct tx_add" to "extent_t":