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

Re: [Xen-devel] domains not shutting down properly - theproblemisback again


  • To: James Harper <james.harper@xxxxxxxxxxxxxxxx>, <xen-devel@xxxxxxxxxxxxxxxxxxx>
  • From: Keir Fraser <keir.fraser@xxxxxxxxxxxxx>
  • Date: Fri, 02 Jan 2009 10:41:56 +0000
  • Cc:
  • Delivery-date: Fri, 02 Jan 2009 02:42:17 -0800
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>
  • Thread-index: AclsEUiDJwnrGfQLQ6G5Bsw4GM+wzgAAL2RgAAIdJkkAHEzXYAAA9a8QAAD1UUAACaHcAAABmirxAAEexXAAAH2McA==
  • Thread-topic: [Xen-devel] domains not shutting down properly - theproblemisback again

On 02/01/2009 10:28, "James Harper" <james.harper@xxxxxxxxxxxxxxxx> wrote:

>> Xenstored is supposed to receive a VIRQ_DOM_EXC when a domain is
> killed
>> (see xen/common/domain.c:domain_kill()
> 
> Just added some more logging - domain_kill is never called either until
> I explicitly say 'xm destroy'

That's expected. But you don't expect a domain to disappear until you do 'xm
destroy', unless you have on_{poweroff,destroy,crash} = destroy in your
domain config file. In which case the call to domain_kill() should be made
automatically by xend.

Your problem is the domain doesn't disappear even after explicitly doing 'xm
destroy', right? That's the first thing to track down.

 -- Keir



_______________________________________________
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®.