From mboxrd@z Thu Jan 1 00:00:00 1970 From: Anthony Liguori Subject: Re: [RFC] Xend configuration option for console memory limit Date: Tue, 11 Oct 2005 14:29:29 -0500 Message-ID: <434C1299.8090502@us.ibm.com> References: <87ek6rj25k.fsf@us.ibm.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <87ek6rj25k.fsf@us.ibm.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Dan Smith Cc: Xen Developers , Ian.Pratt@cl.cam.ac.uk List-Id: xen-devel@lists.xenproject.org I think this is a reasonable solution. One thing to discuss is what the default limit should be. 4k was the old limit w/xcs and that was obviously unacceptable. Something like 1MB is probably more than enough. I'm of course wary to see there being any possibility of console data loss but this is neccessary to avoid DoS attacks. Regards, Anthony Liguori Dan Smith wrote: >Bug #296 describes the possible Out-Of-Memory outcome of a console >flood. Currently, xenconsoled has the ability to obey a limit, but >Xend does not set it, to prevent console message loss. > >I propose that a configuration option be added to xend-config.sxp that >sets the limit. That way, a user with a large console buffer >requirement can easily set it, and OOM situations can be avoided. > >I'll be happy to knock up a patch if this sounds reasonable. > >Thoughts? > > >