From: Mukesh Rathor <mukesh.rathor@oracle.com>
To: yujiageng734 <yujiageng734@126.com>
Cc: xen-devel@lists.xensource.com
Subject: Re: Questions on gdbsx
Date: Wed, 25 Feb 2009 18:36:53 -0800 [thread overview]
Message-ID: <49A60045.8080406@oracle.com> (raw)
In-Reply-To: <32832343.231441235544321617.JavaMail.coremail@bj126app95.126.com>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset=x-gbk; format=flowed, Size: 1118 bytes --]
yujiageng734 wrote:
> Hi,
>
> I am trying to use your gdbsx. But I don't know how to make a 32bit
> dom0 running on 64bit hypervisor. Can you explain this for me? I'm
> extremely grateful to you.
Hmm.. good question. I don't know, it's always done for me here. One
option would be to just download OVM from edelivery.oracle.com, it's
free, and should ahve both binary and sources. You could look at spec
file to see how they do it.
> By the way, could you give me some tools to debug hypervisor and
> monitor the process of hypervisor start. Any thought will be thankful.
To debug hypervisor, you'll need kdb. You could get that from OVM (xen
3.1.4) also, or http://xenbits.xensource.com/ext/debuggers.hg for
unstable. See README-dbg. If you put earlykdb in xen kernel line in
grub.conf, it would break into kdb during boot very early. Then you can
single step, set breakpoints, etc...
Mukesh
> Yu Jiageng,
> China.
>
> ------------------------------------------------------------------------
> ÍøÒ×ÓÊÏ䣬ÖйúµÚÒ»´óµç×ÓÓʼþ·þÎñÉÌ <http://www.yeah.net>
next parent reply other threads:[~2009-02-26 2:36 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <32832343.231441235544321617.JavaMail.coremail@bj126app95.126.com>
2009-02-26 2:36 ` Mukesh Rathor [this message]
2009-03-03 15:35 ` How expensive is a VM EXIT? Emre Can Sezer
2009-03-03 16:34 ` Keir Fraser
2009-03-04 0:15 ` NAHieu
2009-03-04 8:45 ` Keir Fraser
2009-03-04 18:39 ` Nadolski, Ed
2009-03-04 18:49 ` Keir Fraser
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=49A60045.8080406@oracle.com \
--to=mukesh.rathor@oracle.com \
--cc=xen-devel@lists.xensource.com \
--cc=yujiageng734@126.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.