From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1NSraq-00077k-0X for qemu-devel@nongnu.org; Thu, 07 Jan 2010 07:36:00 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1NSrak-00073t-JA for qemu-devel@nongnu.org; Thu, 07 Jan 2010 07:35:58 -0500 Received: from [199.232.76.173] (port=35357 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1NSrak-00073q-8G for qemu-devel@nongnu.org; Thu, 07 Jan 2010 07:35:54 -0500 Received: from mail-qy0-f194.google.com ([209.85.221.194]:43759) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1NSraj-0008UP-V7 for qemu-devel@nongnu.org; Thu, 07 Jan 2010 07:35:54 -0500 Received: by qyk32 with SMTP id 32so70321qyk.4 for ; Thu, 07 Jan 2010 04:35:53 -0800 (PST) Message-ID: <4B45D523.3040102@codemonkey.ws> Date: Thu, 07 Jan 2010 06:35:47 -0600 From: Anthony Liguori 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 , Gerd Hoffmann , qemu-devel On 01/07/2010 06:10 AM, Richard W.M. Jones wrote: > On Thu, Jan 07, 2010 at 11:55:05AM +0000, Richard W.M. Jones wrote: > >> chardev: opening backend "stdio" failed >> qemu: could not open serial device 'stdio': Invalid argument >> > Or sometimes: > > chardev: opening backend "stdio" failed > qemu: could not open serial device 'stdio': Success > > (!) > > 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. > Your old invocation was technically incorrect but it happened to work. It now throws an error. It's a tough call about whether such things are regressions but in this case, I really don't think it is because the old behaviour wasn't self-consistent. Regards, Anthony Liguori