On Mon, 18 Dec 2023 at 23:56, Dave Blanchard wrote:
>
> > Hmm. Well, we do put the terminal into raw mode (so that we
> > get stuff like ^C), but that is supposed to be reset when
> > QEMU exits.
>
> Can you please direct me to where in the source code this happens?
It happens in different places
> Hmm. Well, we do put the terminal into raw mode (so that we
> get stuff like ^C), but that is supposed to be reset when
> QEMU exits.
Can you please direct me to where in the source code this happens? I found two
or three instances where tcsetattr() is being called, and tried disabling those
c
On Mon, 18 Dec 2023 at 13:36, Dave Blanchard wrote:
>
>
> > If you're directing a guest's terminal to the console then things
> > like line wrapping are entirely up to the guest -- QEMU is
> > providing the equivalent of a piece of hardware like a serial
> > terminal, and how the guest chooses to
> If you're directing a guest's terminal to the console then things
> like line wrapping are entirely up to the guest -- QEMU is
> providing the equivalent of a piece of hardware like a serial
> terminal, and how the guest chooses to write to it is up to
> the guest's serial drivers and TTY layer
On Sun, 17 Dec 2023 at 22:49, Dave Blanchard wrote:
>
> One particularly annoying trait of Qemu is how it nukes my terminal settings.
> This is especially infuriating when booting Linux where the VM console is
> redirected to the serial port, which is then displayed on the host console.
> Among
One particularly annoying trait of Qemu is how it nukes my terminal settings.
This is especially infuriating when booting Linux where the VM console is
redirected to the serial port, which is then displayed on the host console.
Among other things line wrapping is disabled, so compiler output for
