On 09/12/2012 02:57 PM, Lei Li wrote: > This RFC series attempts to convert the MemCharDriver to use a circular > buffer for input and output, expose it to users by introducing QMP commands > memchar_write and memchar_read and via the command line like the other > CharDriverStates. > > Serial ports in qemu always use CharDriverStates as there backends, > Right now, all of our backends always try to write the data from the > guest to a socket or file. The concern from OpenStack is that this could > lead to unbounded disk space usage since they log the serial output. > For more detail of the background info: > https://bugs.launchpad.net/nova/+bug/832507 > > So we want to use a circular buffer in QEMU instead, and then OpenStack > can periodically read the buffer in QEMU and log it.
Can't they do it themselves? Have qemu write to a pipe, and on the other side, do whatever rate limiting is needed. -- error compiling committee.c: too many arguments to function
