From mboxrd@z Thu Jan 1 00:00:00 1970 From: David F Barrera Subject: Re: Unab[l]e to create guest domain on PAE enabled SLES 9 SP2 box, 4GB RAM Date: Tue, 20 Sep 2005 08:56:21 -0500 Message-ID: <1127224581.3688.6.camel@dbarrera_tp> References: <1126712294.4617.7.camel@dbarrera_tp> <553e670b3de3ca3b7c5fb915071a0ccb@cl.cam.ac.uk> <1126716137.6342.7.camel@dbarrera_tp> <1126717891.6339.11.camel@dbarrera_tp> <1126727542.6339.18.camel@dbarrera_tp> <0970586e5f495c3f2b160259176305f9@cl.cam.ac.uk> <1126730875.6338.23.camel@dbarrera_tp> <94516ca190937482ba2d254d7014fbe2@cl.cam.ac.uk> <1126732239.6342.25.camel@dbarrera_tp> <1126797997.6024.10.camel@dbarrera_tp> <5ddf5c5eae96aedf3fe67a9d18f4bdcd@cl.cam.ac.uk> <1127134180.3629.7.camel@dbarrera_tp> <3ac696df12644d5134cfaed6c49cdc7b@cl.cam.ac.uk> <1127155518.5463.0.camel@dbarrera_tp> Mime-Version: 1.0 Content-Type: text/plain Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Keir Fraser Cc: Ian Pratt , xen-devel List-Id: xen-devel@lists.xenproject.org On Tue, 2005-09-20 at 09:44 +0100, Keir Fraser wrote: > On 19 Sep 2005, at 19:45, David F Barrera wrote: > > > (gdb) bt > > #0 0xc02523bd in xencons_ring_send () > > #1 0xc124a7f8 in ?? () > > #2 0x00000001 in ?? () > > #3 0x00000004 in ?? () > > #4 0x00000002 in ?? () > > This isn't a debug build of domain0 -- you need to enable frame > pointers under 'kernel hacking' in the kernel configurator, as > described in the gdb/README file. I followed exactly what the README detailed: DomU GDB server for 32-bit (PAE and non-PAE) systems ---------------------------------------------------- Lines marked below with [*] are optional, if you want full source-level debugging of your kernel image. To build the GDB server: 1. Run ./gdbbuild from within this directory. 2. Copy ./gdb-6.2.1-linux-i386-xen/gdb/gdbserver/gdbserver-xen to your test machine. To build a debuggable guest kernel image: 1. cd linux-2.6.12-xenU 2. ARCH=xen make menuconfig 3. From within the configurator, enable the following options: # Kernel hacking -> Compile the kernel with debug info [*] -> Compile the kernel with frame pointers 4. (Re)build and (re)install your xenU kernel image. To debug a running guest: 1. Use 'xm list' to discover its domain id ($domid). 2. Run 'gdbserver-xen 127.0.0.1:9999 --attach $domid' 3. Run 'gdb /path/to/vmlinux-syms-2.6.xx-xenU' 4. From within the gdb client session: # directory /path/to/linux-2.6.xx-xenU [*] # target remote 127.0.0.1:9999 # bt # disass > > However, I think the problem here doesn;t require you to collect a > proper backtrace. It looks like the domU is spinning waiting to send > console data to xenconsoled. My guess is that either xenconsoled isn;t > running, or it's got itself stuck somehow. > > Worth doing a 'ps auxw' in domain0 and see if the console daemon is > actually running... > > -- Keir > > > _______________________________________________ > Xen-devel mailing list > Xen-devel@lists.xensource.com > http://lists.xensource.com/xen-devel > -- Regards, David F Barrera Linux Technology Center Systems and Technology Group, IBM "The wisest men follow their own direction. " Euripides