From: Keir Fraser <keir@xensource.com>
To: Edward Pilatowicz <edward.pilatowicz@sun.com>
Cc: xen-devel@lists.xensource.com, Joe Bonasera <joe.bonasera@sun.com>
Subject: Re: better console support
Date: Fri, 26 Jan 2007 09:33:55 +0000 [thread overview]
Message-ID: <C1DF7B83.7D37%keir@xensource.com> (raw)
In-Reply-To: <20070126005813.GA731934@eng.sun.com>
On 26/1/07 12:58 am, "Edward Pilatowicz" <edward.pilatowicz@sun.com> wrote:
> so does xen have any uses for serial ports other than as a console
> device? if not then we can probably use this to detect an in use
> port and switch the console to use hypervisor interfaces in this case.
You could set up a remote debug session, but that's not really a normal
usage.
> well, i don't think the xen vgakeep mode (which is essentially an
> extension of the default vga mode) really provides us with a usable
> console configuration since xen doesn't support any kind of keyboard
> input. (at least from my reading of the 3.0.3 code i think will only
> take input from a serial port.) so setting the xen to vga and vgakeep
> and then setting the dom0 console to the hypervisor would essentially
> give you a read-only console.
Our observation has been that, as long as Linux keeps the console in text
mode (doesn't switch to X for example) we can let Linux think it owns the
VGA console and things don't screw up if Xen continues to have at it also.
Again, this isn't really something we'd consider as a normal usage scenario
-- more something to try if Xen doesn't boot and you can't connect a serial
line for some reason.
Xen doesn't include a full debugger -- it has a serial gdbstub which does
its job quite nicely -- so there's nothing really to plumb keyboard input
into. The set of 'debug keys' we plan to make accessible via the xm tool.
-- Keir
next prev parent reply other threads:[~2007-01-26 9:33 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <E1HA4sG-0007vw-5h@host-192-168-0-1-bcn-london>
2007-01-25 17:00 ` better console support Joe Bonasera
2007-01-25 17:48 ` Keir Fraser
2007-01-25 18:47 ` Joe Bonasera
2007-01-25 18:55 ` Keir Fraser
2007-01-26 0:58 ` Edward Pilatowicz
2007-01-26 9:33 ` Keir Fraser [this message]
2007-01-26 10:29 ` John Levon
2007-01-26 12:54 ` Christoph Egger
2007-01-26 13:11 ` Keir Fraser
2007-01-26 13:50 ` Jan Beulich
2007-01-26 13:59 ` Keir Fraser
2007-01-26 16:01 ` Joe Bonasera
2007-01-31 22:56 ` Edward Pilatowicz
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=C1DF7B83.7D37%keir@xensource.com \
--to=keir@xensource.com \
--cc=edward.pilatowicz@sun.com \
--cc=joe.bonasera@sun.com \
--cc=xen-devel@lists.xensource.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.