From owner-freebsd-virtualization@FreeBSD.ORG Sun Jan 12 21:36:15 2014 Return-Path: Delivered-To: freebsd-virtualization@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 51D605A0; Sun, 12 Jan 2014 21:36:15 +0000 (UTC) Received: from mail-pb0-x230.google.com (mail-pb0-x230.google.com [IPv6:2607:f8b0:400e:c01::230]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 1B16112F7; Sun, 12 Jan 2014 21:36:15 +0000 (UTC) Received: by mail-pb0-f48.google.com with SMTP id md12so244321pbc.7 for ; Sun, 12 Jan 2014 13:36:14 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=LnQlXV601GFvLOUpa57Hn0E2tnV6dtfW8sXcJG8OzMI=; b=YKWL1oyu+uWbpZvBp0B7A4v98Y8QmNlH/1EAtPVSvYh2Pqp4UM/Qcw0PZuDchKQCQM brdkz2oHk/dbPZjPNnbHFFURDqDrgHxM+VtqkbIur7Pb8f/zsBpgorPjkU12fpaBzRNf K5ycMMGi0+TCgK5ikolM38LvABpWt7isEDFOma/u3jhyiQUDwHo4uNyuJ80dQWieypPd mMFeTgB55UW62tSGQVYoqzwriiCbaLpae4b6UEib2QvRCVHSdcPMoWMHMQnz+3QcKK1O 8GcFsQ5R5eqgNNfSMYryvzVHga2FwV/X8HsdRIejrESoPp1UIxFWnWU/oaq9fIvBMYMb nBew== MIME-Version: 1.0 X-Received: by 10.66.227.104 with SMTP id rz8mr25991629pac.74.1389562574412; Sun, 12 Jan 2014 13:36:14 -0800 (PST) Received: by 10.68.185.130 with HTTP; Sun, 12 Jan 2014 13:36:14 -0800 (PST) In-Reply-To: <52D2F354.6050005@freebsd.org> References: <52D2F354.6050005@freebsd.org> Date: Sun, 12 Jan 2014 16:36:14 -0500 Message-ID: Subject: Re: Remote serial console for BHyve VM? From: Aryeh Friedman To: Julian Elischer Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.17 Cc: "freebsd-virtualization@freebsd.org" , Peter Wemm 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: Sun, 12 Jan 2014 21:36:15 -0000 > >>> > since I think bHyve can export a socket for debugger control, I'm > surprised it cant' export a socket for the serial console.. a bit like > dcons.. In fact I'd like to see dcons work with bhyve.. > it would be neat to implement a version of the dcons code that used a > signal instead of polling.. > also it'd be nice it the gdb remote could access the machine's memory > without VM co-operation. Looking at the options available in RC4, I do not see anything in the usage statement or the man page on this. Since PetiteCloud (the bhyve front end I'm working on) is designed to work specifically with 10-RELEASE (whenever that is) we have not incorporated anything from bhyve-grub or head/ yet. Once the plans for what is 10 and what is not are 100% final we will update our support. If there is a management socket, you're right it would be a good solution. A better long term solution would be something like VNC (the idea last summer of including mouse/keyboard integration is incomplete for the remote access case of non-command line OS's)... As for the idea of allowing host access to the VM's memory without VM cooperation, why do you want that? Security wise it would be very risky. P.S. ports/185362 and ports/185361 (PetiteCloud and the unit testing framework it uses) need to be committed. Can someone please do this? -- Aryeh M. Friedman, Lead Developer, http://www.PetiteCloud.org