Re: [libvirt] Seeking for advice on 'virsh console' problems debugging

On Fri, Mar 07, 2014 at 06:15:24PM +0400, Roman Bogorodskiy wrote: > Daniel P. Berrange wrote: > > > All those mangled messages are being printed out by libvirt client > > code, and it is totally expected that log messages libvirt prints > > are mangled in this way for the console. > > > > What's more important is what data coming from the guest looks > > like. > > All those spaces come from the stream as well. For example, I've added > the following debugging to daemonStreamHandleRead() into > daemon/stream.c: > > 732 ret = virStreamRecv(stream->st, buffer, bufferLen); > 733 VIR_ERROR("buffer = [%s]", buffer); > > And it prints stuff like: > > 2014-03-07 13:29:34.060+0000: 34489787392: error : > daemonStreamHandleRead:733 : buffer = [ File "/usr/bin/cloud raise > DataSourceNotFoundException(msg) > ] > 2014-03-07 13:29:34.060+0000: 34489787392: error : > daemonStreamHandleRead:733 : buffer = [ > ] > 2014-03-07 13:29:34.061+0000: 34489787392: error : > daemonStreamHandleRead:733 : buffer = [ > ] > 2014-03-07 13:29:34.061+0000: 34489787392: error : > daemonStreamHandleRead:733 : buffer = [ > ] The debug logs are *always* going to be strange when you have the terminal in raw mode. If you're debugging the console support you really must not try to use stderr for debug logs - you'll never get sane results. Set libvirt to log to a file or syslog instead.