The message talks about "resumed" state, which is a bit confusing. While we have a "resumed" event, the corresponding state is called "running". Signed-off-by: Jiri Denemark <jdenemar(a)redhat.com&gt; --- src/qemu/qemu_process.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/qemu/qemu_process.c b/src/qemu/qemu_process.c index 59ca7cd333..4e93b2d741 100644 --- a/src/qemu/qemu_process.c +++ b/src/qemu/qemu_process.c @@ -721,7 +721,7 @@ qemuProcessHandleResume(qemuMonitorPtr mon ATTRIBUTE_UNUSED, if (virDomainObjGetState(vm, NULL) != VIR_DOMAIN_RUNNING) { eventDetail = qemuDomainRunningReasonToResumeEvent(reason); - VIR_DEBUG("Transitioned guest %s out of paused into resumed state, " + VIR_DEBUG("Transitioned guest %s out of paused into running state, " "reason '%s', event detail %d", vm->def->name, virDomainRunningReasonTypeToString(reason), eventDetail); -- 2.19.1