From mboxrd@z Thu Jan 1 00:00:00 1970 From: tgh Subject: Re: [Patch] add XenStore viewer Date: Fri, 14 Dec 2007 14:46:38 +0800 Message-ID: <476226CE.4020709@sina.com.cn> References: <200710040326.49642.mark.williamson@cl.cam.ac.uk> <200710041335.30568.mark.williamson@cl.cam.ac.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=GB2312 Content-Transfer-Encoding: quoted-printable Return-path: In-Reply-To: <200710041335.30568.mark.williamson@cl.cam.ac.uk> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Mark Williamson , Keir Fraser , Daniel Stodden , Tim Deegan Cc: xen-devel@lists.xensource.com List-Id: xen-devel@lists.xenproject.org hi I read the code of "save"and "restore"virtual machine in the PVmode, and there are many interactions with the xenstore, it seems that when restoring virtual machine, adding the entry in xenstore will invoke some watch function to add and initiate some useful devices in the dom0 for backend, is it ? and does it even inform the guestos to add frontend ? I am not familar with python, and confused about the whole workflow for the "save" and "restore" of virtual machine, is the resume function below the major function for "restore" or not? could someone give me an explanation about the workflow about the "save" and "restore" Thanks in advance ______________________________________ def resume(self): """Resumes a domain that has come back from suspension.""" state =3D self._stateGet() if state in (DOM_STATE_SUSPENDED, DOM_STATE_HALTED): try: self._constructDomain() self._storeVmDetails() self._createDevices() self._createChannels() self._storeDomDetails() self._endRestore() ________________________________ Mark Williamson =D0=B4=B5=C0: > Now with patched attached - bonus! Thanks to those who pointed out my=20 > error ;-) > > Cheers, > Mark > > On Thursday 04 October 2007, Mark Williamson wrote: > =20 >> Hi, >> >> Rejigged my XenStore viewer to apply to unstable, use the python distu= tils >> properly, etc. >> >> What is it? A small PyQT application that displays the contents of >> XenStore graphically as a collapsible tree, making it easy to inspect = the >> contents of XenStore and manipulate its values. I've wished for somet= hing >> like this many times when trying to debug xenbus interactions. >> >> It's small chunk of code and adds useful but non-critical functionalit= y, so >> I'd propose it be merged unless anyone has objections (nobody squealed= last >> time, so I'm guessing not). >> >> I'm open to suggestions regarding other features that'd be useful but = it >> does what I want for the moment, I think. >> >> Cheers, >> Mark >> =20 > > > > =20 > -----------------------------------------------------------------------= - > > _______________________________________________ > Xen-devel mailing list > Xen-devel@lists.xensource.com > http://lists.xensource.com/xen-devel > =20