From owner-freebsd-xen@FreeBSD.ORG Sun May 24 11:31:55 2009 Return-Path: Delivered-To: freebsd-xen@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 8BC31106566C; Sun, 24 May 2009 11:31:55 +0000 (UTC) (envelope-from scottl@samsco.org) Received: from pooker.samsco.org (pooker.samsco.org [168.103.85.57]) by mx1.freebsd.org (Postfix) with ESMTP id 3C1C08FC16; Sun, 24 May 2009 11:31:55 +0000 (UTC) (envelope-from scottl@samsco.org) Received: from phobos.local (pooker.samsco.org [168.103.85.57]) by pooker.samsco.org (8.14.2/8.14.2) with ESMTP id n4OBVM9n097416; Sun, 24 May 2009 05:31:22 -0600 (MDT) (envelope-from scottl@samsco.org) Message-ID: <4A19300A.1020906@samsco.org> Date: Sun, 24 May 2009 05:31:22 -0600 From: Scott Long User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X; en-US; rv:1.8.1.13) Gecko/20080313 SeaMonkey/1.1.9 MIME-Version: 1.0 To: Robert Watson References: <20090524091436.GR1271@hoeg.nl> In-Reply-To: X-Enigmail-Version: 0.95.6 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-4.6 required=3.8 tests=ALL_TRUSTED,AWL,BAYES_00 autolearn=ham version=3.1.8 X-Spam-Checker-Version: SpamAssassin 3.1.8 (2007-02-13) on pooker.samsco.org Cc: Ed Schouten , FreeBSD Current , freebsd-xen@freebsd.org Subject: Re: Default Xen PVM console? X-BeenThere: freebsd-xen@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussion of the freebsd port to xen - implementation and usage List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 24 May 2009 11:31:56 -0000 Robert Watson wrote: > On Sun, 24 May 2009, Ed Schouten wrote: > >> * Adrian Chadd wrote: >>> * Modify the xenconsole driver to attach to ttyv0 (via a kernel >>> environment variable) so /etc/ttys doesn't need modifying (but this >>> may confuse tools that assumes /dev/ttyvX == syscons.) >> >> Please don't. Someone on IRC told me Xen also has some framebuffer >> feature. Say, someone would port syscons to Xen, the naming would >> conflict with the console device node. /dev/xc0 is good enough. I even >> think it should have been called ttyx0, not xc0. > > Given that there will be increasing levels of support for "pass-through" > hardware access in virtual machine environments and a trend in the > direction of virtualization-friendly hardware, we shouldn't preclude the > possibility of something a lot closer to syscons working inside of Xen > in the future. This means we should leave the syscons device names open > so that syscons can claim them if desired. > HVM mode already supports "pass-through" with syscons working in it. That is orthogonal to the discussion of supporting the native virtualization features of Xen. Scott