From owner-freebsd-virtualization@freebsd.org Mon Jul 11 18:01:17 2016 Return-Path: Delivered-To: freebsd-virtualization@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 0F787B92B2C for ; Mon, 11 Jul 2016 18:01:17 +0000 (UTC) (envelope-from jakub.klama@uj.edu.pl) Received: from mail1.uj.edu.pl (mail1.uj.edu.pl [149.156.89.193]) by mx1.freebsd.org (Postfix) with ESMTP id CA39711C0 for ; Mon, 11 Jul 2016 18:01:16 +0000 (UTC) (envelope-from jakub.klama@uj.edu.pl) MIME-version: 1.0 Content-type: text/plain; charset=utf-8 Received: from [192.168.0.2] ([89.70.28.46]) by mta.uoks.uj.edu.pl (Oracle Communications Messaging Server 7u4-27.01 (7.0.4.27.0) 64bit (built Aug 30 2012)) with ESMTPSA id <0OA5007GSWPW4K20@mta.uoks.uj.edu.pl> for freebsd-virtualization@freebsd.org; Mon, 11 Jul 2016 20:01:09 +0200 (CEST) Subject: Re: [Differential] D7185: Add virtio-console support to bhyve From: Jakub Klama In-reply-to: <5783D6FF.7010107@redbarn.org> Date: Mon, 11 Jul 2016 20:01:08 +0200 Cc: D7185+333+7754cf487cff2162@reviews.freebsd.org, freebsd-virtualization@freebsd.org Content-transfer-encoding: quoted-printable Message-id: References: <5783D6FF.7010107@redbarn.org> To: Paul Vixie X-Mailer: Apple Mail (2.3094) X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: "Discussion of various virtualization techniques FreeBSD supports." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 11 Jul 2016 18:01:17 -0000 > Wiadomo=C5=9B=C4=87 napisana przez Paul Vixie w = dniu 11.07.2016, o godz. 19:27: >=20 > fwiw, bhyve's existing console support is working fine for me. i use = rtty (from ports). my configuration looks like this: >=20 > [mm1.redbarn:amd64] ls -l /usr/local/rtty/dev > total 3 > lrwxr-xr-x 1 root wheel 11 May 18 2014 family@ -> /dev/nmdm2A > lrwxr-xr-x 1 root wheel 11 May 17 2014 guests@ -> /dev/nmdm0A > lrwxr-xr-x 1 root wheel 11 Nov 16 2014 pbx@ -> /dev/nmdm5A > lrwxr-xr-x 1 root wheel 11 Jun 1 2014 sleipnir@ -> /dev/nmdm3A > lrwxr-xr-x 1 root wheel 11 May 18 2014 util@ -> /dev/nmdm1A > lrwxr-xr-x 1 root wheel 11 May 1 2015 yeti-dns@ -> /dev/nmdm7A >=20 > the bhyve processes are using the corresponding "B" devices. rtty = keeps logs: >=20 > [mm1.redbarn:amd64] ls -l /usr/local/rtty/log/ > total 164401 > -rw-r----- 1 root wheel 2132344 Jul 10 07:18 family > -rw-r----- 1 root wheel 1176529 Jul 10 03:58 guests > -rw-r----- 1 root wheel 1964961 Jul 11 06:23 pbx > -rw-r----- 1 root wheel 133664527 Jul 11 17:25 sleipnir > -rw-r----- 1 root wheel 17943116 Jul 11 17:06 util > -rw-r----- 1 root wheel 11042436 Jul 11 17:11 yeti-dns >=20 > so i can find out why something crashed even if i wasn't watching at = the time. >=20 > so, i'm having trouble understanding the need for virtio-console to be = able to open a host-side unix-domain socket in the file system? >=20 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). 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. Jakub=