-
Notifications
You must be signed in to change notification settings - Fork 90
Open
Description
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?
Metadata
Metadata
Assignees
Labels
No labels