From: Edward Pilatowicz <edward.pilatowicz@sun.com>
To: Joe Bonasera <joe.bonasera@sun.com>
Cc: xen-devel@lists.xensource.com
Subject: Re: better console support
Date: Wed, 31 Jan 2007 14:56:37 -0800 [thread overview]
Message-ID: <20070131225637.GB184259@eng.sun.com> (raw)
In-Reply-To: <45BA25E4.7070607@sun.com>
so it seems that some people are at least interested in accessing
the xen debugger on the local vga console keyboard.
so what would be any requirements for local console debugger support on
xen?
- would it be good to have access to vga/keyboard devices while xen is
loading? i guess this would depend on if xen currently support dropping
to it's interactive debugger while it is booting up? or only after the
host os is booted?
- would it be sufficient to only be able to access the xen debugger
via a vga/keyboard device after the dom0 os has started up? if
so would this be needed very early on in the dom0's boot or
later on after the dom0 has had more time to bring itself up.
i'm really haven't had a huge amount of experience using the xen debugger
so i'm not sure what the most common use cases in the past have been.
answers to the questions above from people who have used the xen
debugger more extensively would be enlightening.
ed
On Fri, Jan 26, 2007 at 08:01:40AM -0800, Joe Bonasera wrote:
> Keir Fraser wrote:
> >On 26/1/07 12:54 pm, "Christoph Egger" <Christoph.Egger@amd.com> wrote:
> >
> >>>>Xen doesn't include a full debugger
> >>>There is one out there though... maybe Christopher has thought about
> >>>this?
> >>I have a working one. Is there a chance to get the patches into Xen 3.0.6
> >>?
> >
> >Why would anyone want to debug over a low-res unscrollable VGA console? If
> >you have a serial line connected then you can already debug via gdb, which
> >surely provides a nicer environment?
> >
>
> It's not so much a choice of wanting to, as having to. Many classes of x86
> computers no longer have serial ports. They're next to impossible to find
> on new
> laptops and rapidly getting that way with desktops and workstations.
> The people defining "platforms" have been killing off "legacy" devices like
> serial ports in favor of USB. It's a lot easier to do a little VGA
> debugging than
> to convince someone to go out and shop around for some sort of add in card
> to get a serial port.
>
> Joe
>
prev parent reply other threads:[~2007-01-31 22:56 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
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 [this message]
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=20070131225637.GB184259@eng.sun.com \
--to=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.