From: Marc-André Lureau <marcandre.lur...@redhat.com> Similarly to the reconnect error, this is an information message rather than an error. Use a trace event instead.
Signed-off-by: Marc-André Lureau <marcandre.lur...@redhat.com> --- qemu-char.c | 3 +-- trace-events | 1 + 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/qemu-char.c b/qemu-char.c index a944ee0..8702931 100644 --- a/qemu-char.c +++ b/qemu-char.c @@ -4434,8 +4434,7 @@ static CharDriverState *qmp_chardev_open_socket(const char *id, } s->listen_ioc = sioc; if (is_waitconnect) { - fprintf(stderr, "QEMU waiting for connection on: %s\n", - chr->filename); + trace_char_socket_waiting(chr->filename); tcp_chr_accept(QIO_CHANNEL(s->listen_ioc), G_IO_IN, chr); } qio_channel_set_blocking(QIO_CHANNEL(s->listen_ioc), false, NULL); diff --git a/trace-events b/trace-events index 19e0a05..e59c0f5 100644 --- a/trace-events +++ b/trace-events @@ -691,6 +691,7 @@ leon3_reset_irq(int intno) "Reset CPU IRQ %d" # qemu-char.c char_socket_reconnect_error(const char *label, const char *err) "Unable to connect character device %s: %s" +char_socket_waiting(const char *filename) "QEMU waiting for connection on: %s" # spice-qemu-char.c spice_vmc_write(ssize_t out, int len) "spice wrottn %zd of requested %d" -- 2.5.5