All of lore.kernel.org
 help / color / mirror / Atom feed
From: Wei Liu <liuw@liuw.name>
To: Daniel Castro <evil.dani@gmail.com>
Cc: xen-devel@lists.xensource.com
Subject: Re: Help debugging domain builder, qemu upstream and hvmloader
Date: Wed, 27 Jul 2011 15:44:12 +0800	[thread overview]
Message-ID: <1311752652.1800.3.camel@limbo> (raw)
In-Reply-To: <CAP2B85_uVRvCEoaD2yGCQqGO0SaDTyNPJ0K=bqNuMTdYRoaW=Q@mail.gmail.com>

On Wed, 2011-07-27 at 12:53 +0900, Daniel Castro wrote:
> Hello All,
> 
> I run into this problem when I modify seabios.
> (XEN) hvm.c:1131:d13 Triple fault on VCPU 0 - invoking HVM system reset.
> 
> Since there is no fault handlers in the early stages of guest boot I
> am in the need to debug the domain builder, upstream qemu and/or
> hvmloader to see where exactly the fault is being generated.
> 
> I have no experience on debugging and this seems like a good time to start.

Ian Campbell once mentioned his trick to debug QEMU (following
paragraphs quoted from his email):

=====================================================================
When I have an issue with qemu I often specify the device model in my
guest configuration as a script containing:
       echo $@ > /tmp/qemu-dm
       sleep 1h

Then immediately after running "xl create" I can examine /tmp/qemu-dm
and run the qemu by hand in the foreground, or under gdb etc. (there is
a timeout in xl waiting for qemu to announce itself so you need to be
reasonably prompt...)
=====================================================================

Wei.

  parent reply	other threads:[~2011-07-27  7:44 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-27  3:53 Help debugging domain builder, qemu upstream and hvmloader Daniel Castro
2011-07-27  7:15 ` Keir Fraser
2011-07-27  7:44 ` Wei Liu [this message]
     [not found]   ` <CAP2B858WotB2ggGqj=4uANCOrdFiZ7KfE+QsuBjm0fU9BgZ7iA@mail.gmail.com>
2011-07-27 10:11     ` Wei Liu

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=1311752652.1800.3.camel@limbo \
    --to=liuw@liuw.name \
    --cc=evil.dani@gmail.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.