Re: [Qemu-devel] -serial stdio broken

2010-01-07 Thread Anthony Liguori
On 01/07/2010 07:25 AM, Richard W.M. Jones wrote: On Thu, Jan 07, 2010 at 01:32:09PM +0100, Gerd Hoffmann wrote: 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

Re: [Qemu-devel] -serial stdio broken

2010-01-07 Thread Richard W.M. Jones
On Thu, Jan 07, 2010 at 12:44:17PM +, Daniel P. Berrange wrote: > On Thu, Jan 07, 2010 at 06:34:13AM -0600, Anthony Liguori wrote: > > On 01/07/2010 05:55 AM, Richard W.M. Jones wrote: > > >On Sun, Dec 13, 2009 at 08:24:54AM +, Blue Swirl wrote: > > > > > >>I guess e1c09175bc00dd8dfb2ad1

Re: [Qemu-devel] -serial stdio broken

2010-01-07 Thread Richard W.M. Jones
On Thu, Jan 07, 2010 at 01:32:09PM +0100, Gerd Hoffmann wrote: > 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 regressio

Re: [Qemu-devel] -serial stdio broken

2010-01-07 Thread Anthony Liguori
On 01/07/2010 06:44 AM, Daniel P. Berrange wrote: NB, QEMU 0.12 introduces a new flag '-nodefaults' that can be used to get rid of this imlied 'serial stdio', and all other implied devices. It is well worth using this new -nodefaults flag if you're managing qemu from an app to avoid these surpris

Re: [Qemu-devel] -serial stdio broken

2010-01-07 Thread Daniel P. Berrange
On Thu, Jan 07, 2010 at 06:34:13AM -0600, Anthony Liguori wrote: > On 01/07/2010 05:55 AM, Richard W.M. Jones wrote: > >On Sun, Dec 13, 2009 at 08:24:54AM +, Blue Swirl wrote: > > > >>I guess e1c09175bc00dd8dfb2ad1b26e1858dcdc109b59 or > >>998bbd74b9d813b14a3a3b5009a5d5a48c7dce51 broke -seri

Re: [Qemu-devel] -serial stdio broken

2010-01-07 Thread Anthony Liguori
On 01/07/2010 06:10 AM, Richard W.M. Jones wrote: On Thu, Jan 07, 2010 at 11:55:05AM +, 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:

Re: [Qemu-devel] -serial stdio broken

2010-01-07 Thread Anthony Liguori
On 01/07/2010 05:55 AM, Richard W.M. Jones wrote: On Sun, Dec 13, 2009 at 08:24:54AM +, Blue Swirl wrote: I guess e1c09175bc00dd8dfb2ad1b26e1858dcdc109b59 or 998bbd74b9d813b14a3a3b5009a5d5a48c7dce51 broke -serial stdio for all targets: qemu -serial stdio -monitor stdio chardev: opening b

Re: [Qemu-devel] -serial stdio broken

2010-01-07 Thread Gerd Hoffmann
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 w

Re: [Qemu-devel] -serial stdio broken

2010-01-07 Thread Richard W.M. Jones
On Thu, Jan 07, 2010 at 11:55:05AM +, 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

Re: [Qemu-devel] -serial stdio broken

2010-01-07 Thread Richard W.M. Jones
On Sun, Dec 13, 2009 at 08:24:54AM +, Blue Swirl wrote: > I guess e1c09175bc00dd8dfb2ad1b26e1858dcdc109b59 or > 998bbd74b9d813b14a3a3b5009a5d5a48c7dce51 broke -serial stdio for all > targets: > qemu -serial stdio -monitor stdio > chardev: opening backend "stdio" failed > qemu: could not open se

[Qemu-devel] -serial stdio broken

2009-12-13 Thread Blue Swirl
I guess e1c09175bc00dd8dfb2ad1b26e1858dcdc109b59 or 998bbd74b9d813b14a3a3b5009a5d5a48c7dce51 broke -serial stdio for all targets: qemu -serial stdio -monitor stdio chardev: opening backend "stdio" failed qemu: could not open serial device 'stdio': No such file or directory