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@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/xen-devel
>
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
|