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

Re: [Xen-devel] How could Xen know a certain GuestOS have already shutdown?


  • To: xen-devel@xxxxxxxxxxxxxxxxxxx
  • From: Bruce Granger <vivagin@xxxxxxxx>
  • Date: Mon, 24 Sep 2012 06:12:59 -0700 (PDT)
  • Delivery-date: Mon, 24 Sep 2012 13:13:25 +0000
  • List-id: Xen developer discussion <xen-devel.lists.xen.org>

It's my honor to receive your answer! Thanks very much!
I have learned much more under your guidance,but I still have a little
question!
I've traced the VIRQ_DOM_EXC which  send from Xen to Dom0 and picked up by
xenstored which fires the @releaseDomain watch when a GuestOS start to
shutdown.

Here, I still have two questions.
First, I haven't found anything useful in the archives about 'releaseDomain
watch'.What is the called '@releaseDomain' ? what's the use of it?
Second,I think that VIRQ_DOM_EXC is the signal used for communicate between
hypervisor and Dom0. I talked that with my parterner, we think that when
shutdown occurs, GuestOS will first get in touch with hypervisor ,then cause
the communication between Xen and Dom0 by VIRQ_DOM_EXC,is that right? What
we also want to know is when shutdown operation occurs in GuestOS, how
GuestOS communicate with the hypervisor first? Is there any signal or
somehow event delivery?
Could you tell me more about that?

Thanks a lot!



--
View this message in context: 
http://xen.1045712.n5.nabble.com/Xen-devel-How-could-Xen-know-a-certain-GuestOS-have-already-shutdown-tp5711421p5711476.html
Sent from the Xen - Dev mailing list archive at Nabble.com.

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxx
http://lists.xen.org/xen-devel


 


Rackspace

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