From owner-freebsd-virtualization@FreeBSD.ORG Tue Apr 29 21:12:42 2014 Return-Path: Delivered-To: freebsd-virtualization@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id CF0AB9F4 for ; Tue, 29 Apr 2014 21:12:42 +0000 (UTC) Received: from mail-vc0-x232.google.com (mail-vc0-x232.google.com [IPv6:2607:f8b0:400c:c03::232]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 8CF121A66 for ; Tue, 29 Apr 2014 21:12:42 +0000 (UTC) Received: by mail-vc0-f178.google.com with SMTP id hu19so1060244vcb.37 for ; Tue, 29 Apr 2014 14:12:41 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:from:date:message-id:subject:to:content-type; bh=eLjhHL/jZvsNp55eBsgyqdoxuO6NsiKsMlGUpCM4J38=; b=ITgbUzGBVtUHpW8+y66Rly6cm+6gFAEbyWB1ILwZ/utlGyYM5TKYuGV6Cpaa9z23Tb yDZ/cc26l4tVRa/aYSvbK4gw1oP5FaXMwXplL1ulO/xc5YHI585jcQwZxhcRvASaLglh glSmoKNSigk3EyAl/btivAbrKjcLgx5H0U8BA+IS2GR1xw08nuXqdWnQL3vOZDL7Cu61 EPMf/Y8+Y3nC8rFKMLQ+CYDBe7yDHGmTl5e7S1ZVSJ7QpgKvO1tcnQCTakjHFN64Uux3 A4KiOqNNWBEld2+pylJOdmXre0P+k7MQk9SfaykST2vNws0wJ6P86A0513JaCubbVHCK ojtw== X-Received: by 10.58.146.5 with SMTP id sy5mr4086veb.43.1398805961650; Tue, 29 Apr 2014 14:12:41 -0700 (PDT) MIME-Version: 1.0 Sender: cochard@gmail.com Received: by 10.58.2.225 with HTTP; Tue, 29 Apr 2014 14:12:21 -0700 (PDT) From: =?ISO-8859-1?Q?Olivier_Cochard=2DLabb=E9?= Date: Tue, 29 Apr 2014 23:12:21 +0200 X-Google-Sender-Auth: fZehJdbUqLM-g0CvrHqKUgW1TJo Message-ID: Subject: bhyve and serial port emulation problem To: freebsd-virtualization@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.17 X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.17 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: Tue, 29 Apr 2014 21:12:43 -0000 Hi, I'm using the same nanobsd image on Virtualbox and bhyve (-CURRENT r265101). The nanobsd image I'm using is configured for serial port as default console: [root@nanobsd]~# cat /boot.config -S38400 -h [root@nanobsd]~# grep ttyu0 /etc/ttys ttyu0 "/usr/libexec/getty std.38400" vt100 on secure The Virtualbox VM is configured for creating a serial pipe: VBoxManage modifyvm nanobsd --uart1 0x3F8 4 --uartmode1 server /tmp/nanobsd.serial and I connect to this guest using "socat unix-connect:/tmp/nanobsd.serial stdio,raw,echo=0,icanon=0" => And it's works without problem. The bhyve is configured with a com1 redirecting to a nmdm device: "-l com1,/dev/nmdm1" and I connect to this guest using "cu -l /dev/nmdm1B" => But this bhyve console didn't works correctly: I can't use tool like less/more (even ssh-keygen can't ask for a passphrase). If I run truss with these tools, It seems they hang for opening /dev/tty. Some differences between virtualbox and bhyve (don't know if it can help): [root@vbox_guest]~# kenv | grep console comconsole_pcidev="" comconsole_port="1016" comconsole_speed="9600" console="comconsole" [root@bhyve_guest]~# kenv | grep console console="userboot" Regards, Olivier