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


FW: [Xen-devel] Xen Kernel Debug Tools

To: <xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject: FW: [Xen-devel] Xen Kernel Debug Tools
From: "John Anderson" <johnha@xxxxxxxxxx>
Date: Tue, 25 Sep 2007 15:05:38 -0700
Delivery-date: Tue, 25 Sep 2007 15:07:38 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
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/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: Acf/sxtA46kyqMJxSvSGvgxm/B8NUQAB7SZQAADw8QAAAGTkYA==
Thread-topic: [Xen-devel] Xen Kernel Debug Tools
>This is pretty surprising. When a domU is actually running, dom0 isn't
>really involved (other than for IO), so its surprising grsec makes a

>Do you get any console output from the guest before it crashes? I'm
>wandering if its actually been built incorrectly by the domain builder
>running in dom0.

I don't get any output from the guest console at all.  If I do something
like 'xm create -c test-domu' I get 'Started domain test-domu', followed
by a newline, and then Dom0's command prompt. 'xm list' then shows the
domain as crashed.  

Does the domain builder reside in the Dom0 kernel or is it a separate
user space program?  If it is a separate user space program, does it
'borrow' any code or interfaces from the kernel source or xen-sparse
tree?  The grsecurity patches modify this code, and the non-grsec Dom0
referenced earlier was built from a non-patched Xen tree.

>Are you using a debug build of Xen? You may get some more helpful

I'm not using a debug build.  Do I just enable kernel debugging in the
kernel .config or do I need to build Xen with options so the hypervisor
itself gets debug info?  Like CFLAGS='-DDEBUG' make world? 

Thanks for taking an interest,

John A.

Xen-devel mailing list

<Prev in Thread] Current Thread [Next in Thread>