FW: [Xen-devel] Xen Kernel Debug Tools

["John Anderson" <johnha@xxxxxxxxxx>]

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

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

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
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel