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


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

To: "xen-devel" <xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject: [Xen-devel] failed in debugging Xen hypervisor with gdb stub of xen
From: "kyle.ma83" <kyle.ma83@xxxxxxxxx>
Date: Sun, 30 Aug 2009 14:36:00 +0800
Delivery-date: Sat, 29 Aug 2009 23:36:36 -0700
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:date:from:to:subject :message-id:x-mailer:mime-version:content-type; bh=yV9S+kcpYL15BvkO7eJkBX0hQPCkAmkvohqFxyEX0SA=; b=Hj1oli7pIqYYGrwkBXYbls1DLVm09hQ/YP6vuUIDjr/dA0Fr02Yd6EEk6yF0X0heqH MG7/7PHFeOcQo09SlpwygBzrH1GkfUaM29VB9I/Eo0+qU9tFBiBDm3oD2RR2k0dvO5Lk oFmgjqKC6gylwMAQzQrPTSnWwi3v+1/1d6awg=
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=date:from:to:subject:message-id:x-mailer:mime-version:content-type; b=Ce3fw9cUpYM0tHWvBAnT5m4wZC/dDuWUHJvfd/JIRhlZSmdB8Eg+lOQHsSBx34tsqB jVOKwV4vFGpJhaTSNRDOYwVKj8VMRBWcbJogJ40aX1rRmYUigL25VOCbq+O/Nr4Z1Ncj Krk60h3nSdrn4Vwcdt9QjjmAypeX6TlTBUTeA=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
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>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
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>