-
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
[vm-node] Deadlock happened while resetting #18
Comments
VM-NODE Output:
GDB backtrace:
|
Two running thread of vm-node: Thread 1 (main thread): it returned from node_driver.h:79 (run_node()) and is blocking at "node_driver.h:80", waiting for thread 2 to finish. The unclear part is why thread 1 returned from run_node(). It should only returned from this function if vm-node is going to finish. Also, a race condition on VMNode::vms_ is confirmed: Note: all source lines mentioned are based on b88add3. |
A deadlock of vm-node will be triggered when the reset from itself (as a result of QEMU crash) and the reset from dispatch (as a result of finishing the current target test) happen at the same time.
This deadlock will also hold dispatch, as dispatch is waiting for the communication with vm-node.
The text was updated successfully, but these errors were encountered: