From mboxrd@z Thu Jan 1 00:00:00 1970 From: Glauber de Oliveira Costa Subject: [PATCH] Bogus uptime after restore Date: Wed, 18 Oct 2006 17:05:54 -0300 Message-ID: <20061018200554.GA16266@redhat.com> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="8t9RHnE3ZwKMSgU+" Return-path: Content-Disposition: inline List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: xen-devel@lists.xensource.com List-Id: xen-devel@lists.xenproject.org --8t9RHnE3ZwKMSgU+ Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Hi, besides being written to the store, the start_time field does not seem to be being grabbed back fron it upon restore. It leaves it blank, thus causing xm uptime to report bogus information. -- Glauber de Oliveira Costa Red Hat Inc. "Free as in Freedom" --8t9RHnE3ZwKMSgU+ Content-Type: text/plain; charset=us-ascii Content-Disposition: inline; filename="uptime.patch" --- xen-3.0.3-testing-11633/tools/python/build/lib.linux-x86_64-2.4/xen/xend/XendDomainInfo.py.orig 2006-09-28 18:52:38.000000000 -0400 +++ xen-3.0.3-testing-11633/tools/python/build/lib.linux-x86_64-2.4/xen/xend/XendDomainInfo.py 2006-10-18 15:16:27.000000000 -0400 @@ -392,6 +392,8 @@ def parseConfig(config): log.warn("Ignoring malformed and deprecated config option " "restart = %s", restart) + result['start_time'] = get_cfg('start_time', float) + log.debug("parseConfig: result is %s", result) return result --8t9RHnE3ZwKMSgU+ Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel --8t9RHnE3ZwKMSgU+--