[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] Re: [Xen-devel] xm list d flag?
Ewan Mellor wrote: One thing to consider is having the drivers destroy the backend devices on a @releaseDomain watch instead of on the front-end path disappearing.A "dying" domain is one that completed shutdown (be it a halt, reboot, crash, or suspend) and that Xen is trying to destroy. If it cannot destroy it, then that means that someone is holding references to pages that belong to it. For example, if a driver backend fails to die, then the domain will stay around (probably indefinitely). Such an occurrence is a bug. @releaseDomain wasn't available when the drivers were first written so it wasn't an option then. This means that Xend does not have to be involved at all in device tear-down (except for the higher level stuff when the domain goes away completely). This should more or less solve the zombie domain problem for good. Thoughts? Regards, Anthony Liguori Ewan. _______________________________________________ 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
|
Lists.xenproject.org is hosted with RackSpace, monitoring our |