Date: Mon, 11 Jul 2016 11:18:38 -0700 From: Paul Vixie <paul@redbarn.org> To: Jakub Klama <jakub.klama@uj.edu.pl> Cc: D7185+333+7754cf487cff2162@reviews.freebsd.org, freebsd-virtualization@freebsd.org Subject: Re: [Differential] D7185: Add virtio-console support to bhyve Message-ID: <5783E2FE.1040309@redbarn.org> In-Reply-To: <FCF5C7E6-2BCF-4729-BC2B-788E1FE74BCE@uj.edu.pl> References: <differential-rev-PHID-DREV-h346qsj6dfo524z3qnfy-req@FreeBSD.org> <5783D6FF.7010107@redbarn.org> <FCF5C7E6-2BCF-4729-BC2B-788E1FE74BCE@uj.edu.pl>
next in thread | previous in thread | raw e-mail | index | archive | help
Jakub Klama wrote: > The purpose of virtio-console is to create arbitrary bidirectional, host-to-guest communication > channels that bypass guest's network stack (don't require working networking in the guest). thanks. i had no idea that the existing console support required a networking stack; it works for the loader and i can watch the kernel load and initialize, so i always assumed it bypassed "networking". > But even for using it as the system console, it's a bit better than emulated serial port, because > the protocol supports passing console resize events from host to guest. 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? 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. -- P Vixie
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?5783E2FE.1040309>