All of lore.kernel.org
 help / color / mirror / Atom feed
From: Christian Tramnitz <chris.ace@gmx.net>
To: xen-devel@lists.xensource.com
Subject: debugging Xen in a serial-less environment
Date: Wed, 04 Mar 2009 22:43:22 +0100	[thread overview]
Message-ID: <gomslu$14q$1@ger.gmane.org> (raw)

I'm currently trying to debug a couple of iommu issues I'm experiencing
on a X58 board with VT-d while passing through hardware into a Windows
HVM domU, but unfortunately it seems legacy hardware was deemed obsolete
and not a single serial port is provided by the board (Asus P6T Deluxe
for that matter).

Are there any alternatives to the Xen console on serial or vga?

I've got netconsole working for dom0 just to realize that Xen brings its
own console drivers...
So usbserial won't work and even PCI-based RS232 might not work (as seen
here: http://permalink.gmane.org/gmane.comp.emulators.xen.devel/53631 )

What are the long-term plans anyway for the console? I think we'll see
onboard serial disappearing more often while usb is no alternative at
all (nobody would want to have it's USB bus owned by the hypervisor
instead of a dom). The same goes for networking, so are there any
options at all?
I've seen an implementation of a syslog relay (xenlogd?) back in 2006,
but having the dom0 handle the events doesn't really help if the
hypervisor crashes, does it?


Best regards,
   Christian

             reply	other threads:[~2009-03-04 21:43 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-04 21:43 Christian Tramnitz [this message]
2009-03-04 21:50 ` debugging Xen in a serial-less environment Dugger, Donald D
2009-03-05  9:42 ` Gerd Hoffmann
2009-03-06 19:33   ` Jeremy Fitzhardinge
2009-03-07  8:50     ` Christian Tramnitz
2009-03-07  9:48       ` Jeremy Fitzhardinge

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='gomslu$14q$1@ger.gmane.org' \
    --to=chris.ace@gmx.net \
    --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.