From owner-freebsd-virtualization@FreeBSD.ORG Sun Jan 12 19:56:14 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 EAC292F4; Sun, 12 Jan 2014 19:56:14 +0000 (UTC) Received: from vps1.elischer.org (vps1.elischer.org [204.109.63.16]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 9F20A1CDE; Sun, 12 Jan 2014 19:56:14 +0000 (UTC) Received: from Julian-MBP3.local (50-196-156-133-static.hfc.comcastbusiness.net [50.196.156.133]) (authenticated bits=0) by vps1.elischer.org (8.14.7/8.14.7) with ESMTP id s0CJu9gX055792 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO); Sun, 12 Jan 2014 11:56:12 -0800 (PST) (envelope-from julian@freebsd.org) Message-ID: <52D2F354.6050005@freebsd.org> Date: Sun, 12 Jan 2014 20:56:04 +0100 From: Julian Elischer User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:24.0) Gecko/20100101 Thunderbird/24.2.0 MIME-Version: 1.0 To: Aryeh Friedman , Craig Rodrigues Subject: Re: Remote serial console for BHyve VM? References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit 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 19:56:15 -0000 On 1/12/14, 5:13 AM, Aryeh Friedman wrote: > On Mon, Jan 6, 2014 at 5:56 PM, Craig Rodrigues wrote: > >> Hi, >> >> I am working with Sean Bruno to set up some BHyve VM's. >> >> Right now, the vmrun.sh script tells BHyve to direct >> the serial console to stdout. >> > Best solution for a permanent remote console I have heard so far is to use > screen to be able to reconnect to it. We (Dee Nixon and I) have not > actually done this, however, and are looking for a more portable solution. > > If I want to have the VM's start via an rc.d script, and >> have the VM be headless, what is the best way to have >> the VM console still be accessible? >> > A small hack to PetiteCloud (which neither me or Dee have time for but > would be very interested in if someone can do it) might be the best here > since PetiteCloud has auto start on boot -- something that is hard to do > without a lot of custom scripting if you're going with no front-end. For > example it took us over 40 hrs of work to add the auto-start capability to > PetiteCloud. (We were never able to get vmrun.sh to start on boot.) > >> Has anyone done something like use netcat >> to direct the BHyve stdio to a socket? 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. > Me and Dee spent a few weeks with something like it last summer and didn't > have much success. > > >> That way the serial console could be accessed remotely >> via telnet or ssh. >> >> Is there a better way to do this? >> >> -- >> Craig >> _______________________________________________ >> freebsd-virtualization@freebsd.org mailing list >> http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization >> To unsubscribe, send any mail to " >> freebsd-virtualization-unsubscribe@freebsd.org" >> > _______________________________________________ > freebsd-virtualization@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization > To unsubscribe, send any mail to "freebsd-virtualization-unsubscribe@freebsd.org" >