Re: [Qemu-devel] curses.c: "We need a terminal output" ?

[Gerd Hoffmann <kraxel@redhat.com>]

  Hi,

> Then I don't understand why it just ran fine.
> I don't expect fullscreen output to work perfectly anyway;

If you don't expect the output to actually work,
then fine, feel free to comment out that check.

I don't consider that being a sane approach though.

> just enough so I can use qemu expect-style.
> 
> Also, is qemu -curses actually using all the terminal shenanigans?
> I don't think so. If it is, it's not really needed it seems, things work
> fine.

The curses library depends on them, sure.  How else do you think the
curses UI manages to work correctly no matter how big your terminal
window is?

> > > > I can see another scenario when this is problematic: Unit testing code
> > > > that directly writes to the console. E.g. testing BIOS code, or testing
> > > > operating systems when using the serial port is not an option.
> > 
> > seabios can work with the serial console just fine, try "qemu -nographic"
> 
> Well, can you tell me how convince any *BSD to talk to seabios intead of to
> the terminal...

All boot loaders I've seen so far actually talk to seabios.  Which is
enough to enable the kernel's serial console support.  The general
approach is the same on any unix-ish guest operating system.  The
details may vary of course.

FreeBSD:
 (1) qemu-system-x86_64 -nographic -cdrom FreeBSD-11.0-RELEASE-amd64-disc1.iso
 (2) At the bootloader menu hit '3' (Escape to loader prompt).
 (3) set console=comconsole
 (4) boot

Figuring the procedure for other guests is left as an exercise to the
reader.

cheers,
  Gerd