Date: Mon, 11 Jul 2016 11:32:43 -0700 From: Paul Vixie <paul@redbarn.org> To: Jakub Klama <jakub.klama@uj.edu.pl> Cc: freebsd-virtualization@freebsd.org Subject: Re: [Differential] D7185: Add virtio-console support to bhyve Message-ID: <5783E64B.9010608@redbarn.org> In-Reply-To: <EDFB1E4C-755F-4D2F-808C-E45A31C3EE2C@uj.edu.pl> References: <differential-rev-PHID-DREV-h346qsj6dfo524z3qnfy-req@FreeBSD.org> <5783D6FF.7010107@redbarn.org> <FCF5C7E6-2BCF-4729-BC2B-788E1FE74BCE@uj.edu.pl> <5783E2FE.1040309@redbarn.org> <EDFB1E4C-755F-4D2F-808C-E45A31C3EE2C@uj.edu.pl>
next in thread | previous in thread | raw e-mail | index | archive | help
Jakub Klama wrote: > ... What I meant is that virtio-console can be used as a > replacement for TCP/IP communication between host and guest (at least in > some applications). For example, it can be used by the "guest additions" > code to talk to the host. so, kermit? :-) >> nmdm could theoretically (as pty and pts both do) support >> TIOCGWINSZ and SIGWINCH, though? or perhaps bhyve's virtio_console >> device could offer pts(4) support? > > Yeah, virtio_console totally deserves support for binding virtual > console to a pty/pts. layering wise, adding TIOCGWINSZ and SIGWINCH support to nmdm makes more sense than inventing another host-side protocol. as does adding pts(4) support to the virtio_console driver. are those things hard? >> is the protocol spoken over the virtio_console socket documented >> online? i'd like to add support to rtty. currently i've been >> running the "resize" command at the guest shell, which feels very >> primitive. > > Right now the socket just speaks raw data. It would need some > multiplexing or ideally an IPC mechanism to send the resize events. yikes. so you've got to reinvent what TIOCPKT does, but differently? -- P Vixie
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?5783E64B.9010608>