Date: Mon, 11 Jul 2016 14:52:16 -0700 From: Peter Grehan <grehan@freebsd.org> To: Jakub Klama <jakub.klama@uj.edu.pl>, Paul Vixie <paul@redbarn.org> Cc: freebsd-virtualization@freebsd.org Subject: Re: [Differential] D7185: Add virtio-console support to bhyve Message-ID: <18630e8f-6576-b613-1eae-07a00eca7b91@freebsd.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
Hi Jakub,
> 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).
Could virtio-vsock be a better solution for this ? Docker's hyperkit
has an implementation, though it appears Linux guest support is very recent.
https://github.com/docker/hyperkit/blob/af-vsock/src/pci_virtio_sock.c
> 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.
It makes for an excellent serial port since it uses descriptor rings
for data transfer, but the lack of a simple polled-mode operation
(unless the emergency support is used) isn't the best for a system console.
later,
Peter.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?18630e8f-6576-b613-1eae-07a00eca7b91>