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

Re: [Xen-devel] Unplugging a dom0 vcpu and domain destruction


  • To: Jeremy Fitzhardinge <jeremy@xxxxxxxx>, "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>
  • From: George Dunlap <dunlapg@xxxxxxxxx>
  • Date: Tue, 24 Feb 2009 17:26:37 +0000
  • Cc:
  • Delivery-date: Tue, 24 Feb 2009 09:27:34 -0800
  • Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:content-type :content-transfer-encoding; b=xhhZof+uNVBVl3nU7hDjmoo6jTdoB1qKWSqdSOx2FWBaBAiNG9lwIqccFIqgj6dkmM Xf0qp46WL+IQfdFSqvOW7z63kjBtq1cfW4NMl8CHJrSFQtF6M5vbQsnB4N4+zBe1fwE2 e/SUksS6T7PNAG1XC2WeW+mmpFd06vBJVr2SI=
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>

Gah... a real, proper clean-up and build from scratch and the problem
disappears. Who knows what it was, but it's more a bug with
dependencies / build system than a bug in the code proper. I'm done
chasing it, anyway.

-George

2009/2/24 Keir Fraser <keir.fraser@xxxxxxxxxxxxx>:
> On 24/02/2009 01:07, "George Dunlap" <George.Dunlap@xxxxxxxxxxxxx> wrote:
>
>> Is there a good way to trigger a Linux stack dump from within Xen?
>> Even crashing dom0 would be OK if it will get a good stack dump. :-)
>> If I could see how we got to the final unmap_vma(), I might be able to
>> track things down easier...
>
> do_guest_trap(TRAP_gp_fault, regs, 0) ?
>
>  -- Keir
>
>
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/xen-devel
>

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel


 


Rackspace

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