qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Szymon Lukasz <noh4hss@gmail.com>
To: "Daniel P. Berrangé" <berrange@redhat.com>
Cc: lvivier@redhat.com, mst@redhat.com, amit@kernel.org,
	qemu-devel@nongnu.org, pbonzini@redhat.com,
	marcandre.lureau@redhat.com
Subject: Re: [PATCH v2 0/6] virtio-console: notify about the terminal size
Date: Thu, 25 Jun 2020 11:54:33 +0200	[thread overview]
Message-ID: <20200625095433.GB118320@aorus> (raw)
In-Reply-To: <20200624115615.GI774096@redhat.com>

On Wed, Jun 24, 2020 at 12:56:15PM +0100, Daniel P. Berrangé wrote:
> On Wed, Jun 24, 2020 at 01:26:34PM +0200, Szymon Lukasz wrote:
> > In this series resize notifications are only supported for the stdio
> > backend but I think it should be easy to add support for the vc backend.
> > Support for tty/serial backends is complicated by the fact that there is
> > no clean way to detect resizes of the underlying terminal.
> 
> In a libvirt managed scenario it is typical to have the virtio console
> connected to a UNIX socket. It would be desirable to have a way to
> deal with resizes there.
> 
> QEMU socket chardev (TCP & UNIX socket) supports a "telnet" protocol
> addition. Currently it doesn't almost nothing useful, but in theory
> we could wire up support for the telnet resize message:
> 
>    https://tools.ietf.org/html/rfc1073
> 
> 
> Another option is to allow dealing with resizes out of band, via the
> QMP monitor. ie we can introduce a qmp_chardev_winsize command that
> a client app can use to trigger the resize message to the guest OS.
> From libvirt's POV, this would be quite easy to support & useful to
> have.

I will look into that.
> 
> 
> Regards,
> Daniel
> -- 
> |: https://berrange.com      -o-    https://www.flickr.com/photos/dberrange :|
> |: https://libvirt.org         -o-            https://fstop138.berrange.com :|
> |: https://entangle-photo.org    -o-    https://www.instagram.com/dberrange :|
> 


      reply	other threads:[~2020-06-25  9:56 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-24 11:26 [PATCH v2 0/6] virtio-console: notify about the terminal size Szymon Lukasz
2020-06-24 11:26 ` [PATCH v2 1/6] main-loop: change the handling of SIGWINCH Szymon Lukasz
2020-06-24 11:26 ` [PATCH v2 2/6] chardev: add support for retrieving the terminal size Szymon Lukasz
2020-06-24 11:26 ` [PATCH v2 3/6] chardev: add support for notifying about terminal resizes Szymon Lukasz
2020-06-24 11:26 ` [PATCH v2 4/6] char-stdio: add support for the terminal size Szymon Lukasz
2020-06-24 11:26 ` [PATCH v2 5/6] virtio-serial-bus: add terminal resize messages Szymon Lukasz
2020-06-24 13:37   ` Michael S. Tsirkin
2020-06-24 11:26 ` [PATCH v2 6/6] virtio-console: notify the guest about terminal resizes Szymon Lukasz
2020-06-24 11:49 ` [PATCH v2 0/6] virtio-console: notify about the terminal size Daniel P. Berrangé
2020-06-25  9:52   ` Szymon Lukasz
2020-06-25 13:18   ` Michael S. Tsirkin
2020-06-25 13:23     ` Daniel P. Berrangé
2020-06-25 13:45       ` Michael S. Tsirkin
2020-06-24 11:56 ` Daniel P. Berrangé
2020-06-25  9:54   ` Szymon Lukasz [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20200625095433.GB118320@aorus \
    --to=noh4hss@gmail.com \
    --cc=amit@kernel.org \
    --cc=berrange@redhat.com \
    --cc=lvivier@redhat.com \
    --cc=marcandre.lureau@redhat.com \
    --cc=mst@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=qemu-devel@nongnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).