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

[Xen-devel] xm list triggers shutdown refreshing

To: xen-devel@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-devel] xm list triggers shutdown refreshing
From: John Levon <levon@xxxxxxxxxxxxxxxxx>
Date: Thu, 4 Jan 2007 19:30:42 +0000
Delivery-date: Thu, 04 Jan 2007 11:29:00 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
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>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mutt/1.5.9i
xm list -> XendDomain:list_sorted() -> XendDomain:list() ->
XendDomain:_refresh() -> XendDomainInfo:update(refresh = True)

Surely such non-modifying commands should not be altering state? Why
aren't we passing in refresh = False in these cases?

This is a nasty problem if (say) dumpCore fails: every time we try to xm
list, then it will 'notice' that the domain is in the crashed state, try
to dump core, fail and plop that error back to 'xm list'.

regards
john

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel

<Prev in Thread] Current Thread [Next in Thread>