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

Re: [Xen-devel] libxl: error when destroying domain on NetBSD



On Fri, 2011-12-02 at 10:10 +0000, Roger Pau Monnà wrote:
> 2011/12/2 Ian Campbell <Ian.Campbell@xxxxxxxxxx>:
> > It's normal I think. handle_domain_death() is there to deal with
> > graceful shutdown and reboot scenarios e.g. to clear up after the domain
> > and restart as necessary.
> >
> > xl destroy is explictly the command which shoots the domain in the head
> > and so it also calls destroy. If you want graceful you should use "xl
> > shutdown".
> >
> > Although handle_domain_death also picks up on the destroy it shouldn't
> > be doing too much in that case since the interesting work has already
> > happened. The interesting logs will be the xl -vvv destroy ones I think.
> 
> Devices doesn't get disconnected, or at least they don't get to state
> '6' until xl exits, maybe I should modify libxl_domain_destroy to
> search xenstore and try to manually execute hotplug scripts for
> devices that are still connected after calling
> 'libxl__devices_destroy'.

libxl_destroy_domain should be called with force = 1 in the main_destroy
case, I suspect. Does that cause the scripts to be run?

>   Using xl -vvv destroy <domid>' doesn't
> print any debug message, only:
> 
> xc: debug: hypercall buffer: total allocations:131 total releases:131
> xc: debug: hypercall buffer: current allocations:0 maximum allocations:2
> xc: debug: hypercall buffer: cache current size:2
> xc: debug: hypercall buffer: cache hits:128 misses:2 toobig:1
> 
> Thanks, Roger.



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