-
Notifications
You must be signed in to change notification settings - Fork 15
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
waiting for port connection #48
Comments
Is there any indication that |
When I ran the vm-node script, the dispatch terminal displayed saying "Awaiting connection on 'ubuntu' on port '10012'. |
Thank you for the screenshot. "Awaiting connection on 'ubuntu' on port '10012'" just means that dispatch is open to new connections - not necessarily that anything is wrong. It would appear that the file I see that the mode is "distributed" - meaning Check to ensure |
There is a port and pid file existing in the /vm/1/hostfile/ directory. The situation in the screenshot is still persisting even after removing the file and restarting. |
I may have to reproduce your env, to get to the bottom of this. Can you supply the following:
|
Hi, I want to make sure that the sequences you are running it are qemu dispatch vm and then svm right? |
Thanks for sending the scripts via emails. It looks like you are not using crete-qemu-2.3-system-x86_64 which is a modified qemu by crete to run the snapshot. |
$CRETEPATH/crete-qemu-2.3-system-x86_64 $COMM_CMD -m $MEM_SIZE -loadvm test -device cirrus-vga &> qemu_log.txt |
This is the command I used to load the snapshot. |
Command looks right. Can you provide the configuration files of vm dispatch svm as well? |
Where are the output files located? Also, how to analyze them for the sample configuration file provided I just changed the binary target? |
The host OS displays "Awaiting connection on 'ubuntu' on port 10012" after the 3 files dispatch,vm-node and svm-node are run. The guest OS is also running crete-run command which displays "Waiting for port". How do I complete the port connection for the tests and traces to run?
The text was updated successfully, but these errors were encountered: