Date: Sun, 24 May 2009 05:31:22 -0600 From: Scott Long <scottl@samsco.org> To: Robert Watson <rwatson@freebsd.org> Cc: Ed Schouten <ed@80386.nl>, FreeBSD Current <freebsd-current@freebsd.org>, freebsd-xen@freebsd.org Subject: Re: Default Xen PVM console? Message-ID: <4A19300A.1020906@samsco.org> In-Reply-To: <alpine.BSF.2.00.0905241043360.75344@fledge.watson.org> References: <d763ac660905232026n6542fd17k8f6c8625543be4fa@mail.gmail.com> <20090524091436.GR1271@hoeg.nl> <alpine.BSF.2.00.0905241043360.75344@fledge.watson.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Robert Watson wrote: > On Sun, 24 May 2009, Ed Schouten wrote: > >> * Adrian Chadd <adrian@freebsd.org> 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4A19300A.1020906>