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.

Sign up for GitHub

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

Jump to bottom

QMP connect with timeout #214

Open
rsbhagavatula opened this issue Nov 25, 2024 · 0 comments
Open

QMP connect with timeout #214

rsbhagavatula opened this issue Nov 25, 2024 · 0 comments

Comments

@rsbhagavatula
Copy link

In certain situations (say when a QEMU process has been SIGSTOP'ed), the QMP monitor.Connect() API gets reply blocked on the QEMU instance to respond to a QMP capabilities query. Since the QEMU instance is in a "suspended state", QMP's monitor.Connect() would unblock only after the said QEMU process has been "resumed" via a SIGCONT.

Currently there is no option to timeout the monitor.Connect() function (similar to the NewSocketMonitor() function. Any alternatives?
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@rsbhagavatula