WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

Re: [Xen-devel] yanked share problem

To: mark.williamson@xxxxxxxxxxxx
Subject: Re: [Xen-devel] yanked share problem
From: Anthony Liguori <aliguori@xxxxxxxxxx>
Date: Wed, 14 Dec 2005 21:09:08 -0600
Cc: "Tian, Kevin" <kevin.tian@xxxxxxxxx>, NAHieu <nahieu@xxxxxxxxx>, xen-devel@xxxxxxxxxxxxxxxxxxx, "King, Steven R" <steven.r.king@xxxxxxxxx>
Delivery-date: Thu, 15 Dec 2005 03:11:06 +0000
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <Prayer.1.0.16.0512150159540.3713@xxxxxxxxxxxxxxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <571ACEFD467F7749BC50E0A98C17CDD802C06AB8@pdsmsx403> <Prayer.1.0.16.0512150159540.3713@xxxxxxxxxxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mozilla Thunderbird 1.0.7 (X11/20051013)
M.A. Williamson wrote:

Yes, that's the desired way in most cases, as long as domain crash event can be notified to xenstore and then watches upon specific node can work for this purpose. Normal shutdown command issued from user can follow this process due to driver code aware to send traffic on xenbus. But abnormal crash may not go to such branch. Maybe we need a heartbeat check between xenstore and hooked domains? ;-)


When a domain dies (for any reason), a VIRQ_DOM_EXC will be sent to dom0, telling it that something "exceptional" (like being shutdown, or crashing) has happened to a domain. This causes some entity (currently still Xend, AFAIK) to go check the state of all the domains - the store will get updated appropriately as a result of this.

Actually, now the VIRQ_DOM_EXC is delivered to xenstored which results in watches on @releaseDomain to be triggered. Xend set watches on @releaseDomain and does the appropriate action.

This should work even for crashes - in the current world, this mechanism also ensures it's possible to restart domains, clean up their devices, etc if they die unexpectedly.

If you're really concerned about the backend freeing it's resources, the most reliable approach (albiet somewhat hacky) is to have the backend periodically make a getdomaininfo() call and check to see if shutdown, crashed, or dying bits are set and cleanup automatically.

So watching the store ought to be fine in all cases, so long as dom0 stays up (which is another problem ;-)

Until we can kexec() dom0 in place :-)

Regards,

Anthony Liguori

Cheers,
Mark

_______________________________________________
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