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 +0000, 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 serial device 'stdio': No such file or directory > >> > >-serial stdio on its own is broken for me (qemu from git). The error > >is a little bit different, so I don't think this is the same bug: > > > > chardev: opening backend "stdio" failed > > qemu: could not open serial device 'stdio': Invalid argument > > > >The full command line is: > > > >$qemudir/x86_64-softmmu/qemu-system-x86_64 \ > > -L $qemudir/pc-bios \ > > -drive file=/tmp/test.img,cache=off,if=ide \ > > -m 500 \ > > -no-reboot \ > > -nographic \ > > -serial stdio \ > > > > This is redundant. -nographic implies -serial stdio.
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 surprises eg this should work as you'd expect it qemu -nodefaults -nographic -serial stdio Regards, Daniel -- |: Red Hat, Engineering, London -o- http://people.redhat.com/berrange/ :| |: http://libvirt.org -o- http://virt-manager.org -o- http://ovirt.org :| |: http://autobuild.org -o- http://search.cpan.org/~danberr/ :| |: GnuPG: 7D3B9505 -o- F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 :|
