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

Re: [Xen-devel] [patch]Make xend to take care of dead qemu-dm process


  • To: shawn <xiaowei.hu@xxxxxxxxxx>
  • From: Keir Fraser <keir.fraser@xxxxxxxxxxxxx>
  • Date: Wed, 21 May 2008 10:37:52 +0100
  • Cc: xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxx>
  • Delivery-date: Wed, 21 May 2008 02:38:32 -0700
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>
  • Thread-index: Aci7JlbUlV6gJCcZEd2nzwAX8io7RQ==
  • Thread-topic: [Xen-devel] [patch]Make xend to take care of dead qemu-dm process

On 21/5/08 10:10, "shawn" <xiaowei.hu@xxxxxxxxxx> wrote:

> yes,that may be a better solution.
> Do you mean just set the XendDomainInfo._stateSet(DOM_STATE_CRASHED),and
> let xend take care of the left things?

Yes. I have only a dim idea of how these things work in xend, but that's the
general idea and I expect there are existing examples of this kind of
approach already within xend.

> But I can't find ïDOM_STATE_CRASHED like constant defined,there is
> only ïDOM_STATE_HALTED,ïDOM_STATE_RUNNING,etc. So not sure this could
> work...

It's defined in XendConstants.py along with all the others!

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