This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
Home Products Support Community News


RE: RE: [Xen-devel] failed in debugging Xen hypervisor with gdb stub of

To: "'kyle.ma83'" <kyle.ma83@xxxxxxxxx>
Subject: RE: RE: [Xen-devel] failed in debugging Xen hypervisor with gdb stub of xen
From: Caz Yokoyama <cazyokoyama@xxxxxxxxx>
Date: Sun, 30 Aug 2009 07:05:54 -0700
Cc: 'xen-devel' <xen-devel@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Sun, 30 Aug 2009 07:06:13 -0700
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:from:to:cc:references:subject :date:message-id:mime-version:content-type:x-mailer:thread-index :in-reply-to:x-mimeole; bh=F6FcJVPOU0djckGJN5gjkpVDN+TYxCcRqTygtsnBx/g=; b=WfqMi+MbOkUZJHCoGzp8xsb6gvddvwRMuqoW7NWVtwOnX2PhugjuDZTX8kYfzihdBh lLLKtHmoxr/MGhi5IBQAbM9dfZ3RfMTDvNiF4eZLP4zWeIMsuHdmcZHdXrJAE2mBn3zi 5cN5v9us8f+IofYzRueAC6pZ9dtcP3GfAthY4=
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=from:to:cc:references:subject:date:message-id:mime-version :content-type:x-mailer:thread-index:in-reply-to:x-mimeole; b=yGUGJs3yEIjcQeNGxNOIWEi9QP+b4FWH+DomnLEYTFem2CRafir5ntMBUIQXcIYSVi B+dpsKohYLZf6vNy2RMaAt21CDCj8wNOxoicw/yYNrme9dTP1QTvfY49hiqOcKzzZ5Vx qAOAHahBfE7PukwnoObpY2vgei1NIqJAhNIK0=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <200908302129175627729@xxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <200908301435576257404@xxxxxxxxx> <200908302129175627729@xxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: AcopdeaWBX30GahqQLW12pi4nwSfxAABAxyQ

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?



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


debugging. ):


Thanks a lot.





发件人: Caz Yokoyama

发送时间: 2009-08-30  20:40:09

收件人: 'kyle.ma83'

抄送: 'xen-devel'

主题: 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.



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:


title           xen-3.2.0

root            (hd0,0)

kernel          /boot/xen-3.2.0.gz hap com1=115200,8n1 console=com1,vga gdb=com1 sync_console

module          /boot/vmlinuz- root=/dev/sda1 ro xencons=ttyS0

module          /boot/initrd.img-



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) ******* 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) 3... 2... 1... 

(XEN) Xen is relinquishing VGA console.

(XEN) *** Serial input -> DOM0 (type 'CTRL-a' three times to switch input to Xen)

(XEN) unpasue dom0

(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.


Thanks a lot.


Kyle Ma

Xen-devel mailing list
<Prev in Thread] Current Thread [Next in Thread>