[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-users] Debugging DomU


  • To: Julien Grall <julien.grall@xxxxxxxxxx>, Ian Campbell <ian.campbell@xxxxxxxxxx>
  • From: "Chris (Christopher) Brand" <chris.brand@xxxxxxxxxxxx>
  • Date: Tue, 26 May 2015 23:35:22 +0000
  • Accept-language: en-US
  • Cc: xen-users <xen-users@xxxxxxxxxxxxx>
  • Delivery-date: Tue, 26 May 2015 23:37:06 +0000
  • List-id: Xen user discussion <xen-users.lists.xen.org>
  • Thread-index: AdCB2wWZcr9SQU3CS2ODe9QE3SnJMACfCemAAAUH66AAIWukAACjOORwACWVbwABa+9kIAAqoyMAAAGcR8AAL4ylAAEI4IqwAIsLYwAAZrncAAArZ/SAAA3FjUA=
  • Thread-topic: [Xen-users] Debugging DomU

>I confirm the CONFIG_DEBUG_LL should be disabled in Xen guest because it's not 
>portable and not supported.

Yes, that definitely seems to have been my first problem.

>You may be able to get some message before the console is effectively setup by 
>applying the patch in [1]. It will print every guest message on the Xen 
>console.

That patch is *very* useful. Thanks! I now have a backtrace for the new problem:
Unwind_backtrace
Show_stack
Dump_stack
Panic
Memblock_alloc_base
Memblock_alloc
Early_alloc_aligned
Paging_init
Setup_arch
Start_kernel
Plus an error message:
"Failed to allocate 0x2000 bytes below 0x0".

Chris


_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxx
http://lists.xen.org/xen-users


 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.