From: tgh <wwwwww4187@sina.com.cn>
To: Mark Williamson <mark.williamson@cl.cam.ac.uk>,
Keir Fraser <keir@xensource.com>,
Daniel Stodden <stodden@cs.tum.edu>,
Tim Deegan <Tim.Deegan@citrix.com>
Cc: xen-devel@lists.xensource.com
Subject: Re: [Patch] add XenStore viewer
Date: Fri, 14 Dec 2007 14:46:38 +0800 [thread overview]
Message-ID: <476226CE.4020709@sina.com.cn> (raw)
In-Reply-To: <200710041335.30568.mark.williamson@cl.cam.ac.uk>
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 = 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 写道:
> Now with patched attached - bonus! Thanks to those who pointed out my
> error ;-)
>
> Cheers,
> Mark
>
> On Thursday 04 October 2007, Mark Williamson wrote:
>
>> Hi,
>>
>> Rejigged my XenStore viewer to apply to unstable, use the python distutils
>> 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 something
>> like this many times when trying to debug xenbus interactions.
>>
>> It's small chunk of code and adds useful but non-critical functionality, 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
>>
>
>
>
>
> ------------------------------------------------------------------------
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel
>
prev parent reply other threads:[~2007-12-14 6:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-04 2:26 [Patch] add XenStore viewer Mark Williamson
2007-10-04 12:35 ` Mark Williamson
2007-12-14 6:46 ` tgh [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=476226CE.4020709@sina.com.cn \
--to=wwwwww4187@sina.com.cn \
--cc=Tim.Deegan@citrix.com \
--cc=keir@xensource.com \
--cc=mark.williamson@cl.cam.ac.uk \
--cc=stodden@cs.tum.edu \
--cc=xen-devel@lists.xensource.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.