From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1NSrXU-0004DT-TB for qemu-devel@nongnu.org; Thu, 07 Jan 2010 07:32:33 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1NSrXQ-00046s-NJ for qemu-devel@nongnu.org; Thu, 07 Jan 2010 07:32:32 -0500 Received: from [199.232.76.173] (port=45419 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1NSrXQ-00046k-Jj for qemu-devel@nongnu.org; Thu, 07 Jan 2010 07:32:28 -0500 Received: from mx1.redhat.com ([209.132.183.28]:49638) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1NSrXQ-0007OB-2e for qemu-devel@nongnu.org; Thu, 07 Jan 2010 07:32:28 -0500 Message-ID: <4B45D449.1050600@redhat.com> Date: Thu, 07 Jan 2010 13:32:09 +0100 From: Gerd Hoffmann MIME-Version: 1.0 Subject: Re: [Qemu-devel] -serial stdio broken References: <20100107115505.GA18269@amd.home.annexia.org> <20100107121011.GB18269@amd.home.annexia.org> In-Reply-To: <20100107121011.GB18269@amd.home.annexia.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: "Richard W.M. Jones" Cc: Blue Swirl , qemu-devel Hi, > So what seems to be happening here is there is an implicit monitor > being set up which grabs stdio. Because: > > #define STDIO_MAX_CLIENTS 1 > > my own -serial stdio option subsequently fails. This is a regression > over previous behaviour. I didn't specify a monitor device, because I > don't want one, and previous versions of qemu didn't give me one in > nographic mode. They gave you a monitor too. Try typing 'Ctrl-A c' on stdio, and you'll see. qemu tries to be more clever than you. Which sucks IMHO. But getting rid of that without adding regressions seems to be really hard ... Easiest way to workaround this is to simply not specify '-serial stdio'. It is the default anyway for -nographic, so you don't have to. cheers, Gerd