Hello Kyle,
No, I don’t think the
debugging process is no so much different on 3.2.0 and unstable. However, I
have never installed 3.2.0. I installed 3.4.1 and unstable which is 3.5.
Therefore, I can’t say something sure for 3.2.0.
Are you able to install
3.4.1 to know how to set up gdb and xen?
-caz
From: kyle.ma83
[mailto:kyle.ma83@xxxxxxxxx]
Sent: Sunday, August 30, 2009 6:29
AM
To: Caz Yokoyama
Subject: Re: RE: [Xen-devel]
failed in debugging Xen hypervisor with gdb stub of xen
Thanks for your reply.Caz .
I
modified Xen based on xen-3.2.0, so I think I could not change into unstable.
Is the debugging process very different between 3.2.0 and unstable?
Could
you please show me the details about the debugging method of unstable tree
? I am really confused after woking so long and much on the
发送时间：
2009-08-30 20:40:09
主题：
RE: [Xen-devel] failed in debugging Xen hypervisor with gdb stub of xen
Hello Kyle,
Do you have to use xen-3.2.0?
Are you able to use xen-unstable? A couple of weeks ago, xen-unstable is able
to accept break point, step and continue command. If you can use xen-unstable,
I can guide you to set up for debugging Xen include those commands.
-caz
From:
xen-devel-bounces@xxxxxxxxxxxxxxxxxxx [mailto:xen-devel-bounces@xxxxxxxxxxxxxxxxxxx]
On Behalf Of kyle.ma83
Sent: Saturday, August 29, 2009
11:36 PM
To: xen-devel
Subject: [Xen-devel] failed in
debugging Xen hypervisor with gdb stub of xen
I recently want to debug Xen, and I just follow the
xen-3.2/docs/misc/crashdb.txt. I use two machines (one linux host and one xen
target)and can get the
xen booting message with serial to a remote linux
host,I set debug=y in Config.mk and
set crash_debug=y in xen/Rules.mk when make install xen and
arrange to pass gdb=com1 as a hypervisor command line argument,
my grub is as followed:
kernel /boot/xen-3.2.0.gz hap com1=115200,8n1 console=com1,vga gdb=com1 sync_console
module /boot/vmlinuz-2.6.18.8-xen root=/dev/sda1 ro xencons=ttyS0
module /boot/initrd.img-2.6.18.8-xen
I get the output infomation of Xen and Domain0, but
the crashdb.txt says
give the escape character (^A by default) three times
to talk to Xen (Xen prints `(XEN) *** Serial input -> Xen...'),
so I follow the instrucions. When I
press ctrl-A three times as soon as I see:
(XEN) **********************************************
(XEN) ******* WARNING: CONSOLE OUTPUT IS SYNCHRONOUS
(XEN) ******* This option is intended to aid debugging of Xen by ensuring
(XEN) ******* that all output is synchronously delivered on the serial line.
(XEN) ******* However it can introduce SIGNIFICANT latencies and affect
(XEN) ******* timekeeping. It is NOT recommended for production use!
(XEN) **********************************************
(XEN) Xen is relinquishing VGA console.
(XEN) *** Serial input -> DOM0 (type 'CTRL-a' three times to switch input to Xen)
(XEN) Freed 92kB init memory.
but nothing happened, there is no infomation like
"waiting for GDB attached...." or something else,
and at last get the "login
as: " info , did I miss something or what should I do?
Could anyone give some more details and suggestions
about it or how to debug Xen ? I 'd appreciated it much.
2009-08-30
|
