|
|
|
|
|
|
|
|
|
|
xen-devel
RE: [Xen-devel] Domain save/migrate issue
>Suspend does more than just canonicalize the p2m, it also provides
callbacks for all of the devices so that they can canonicalize their own
page references and set them self up to reinitialize upon resume.
>While the save code can access the p2m table, it has no way of knowing
the device information so just pausing isn't really an option (also, you
could do bad things like checkpoint before a storage operation was
committed or something like that).
>Regards,
>Anthony Liguori
Ok. So pause ALONE is not possible. But I didn't mean I'd do only a
pause:
Suspend writes all the info you just mentioned. And the save code just
writes the info that suspend left for it.
So, lets tackle the problem in xen and/or the host.
If a change was entered into the suspend code, say, a special mode,
"pseudoSuspend" was added, in which the function writes all that same
info
Into that very same place it wrote to before (or any other cozy spot we
can access from the save function), but does NOT actually suspend the
domain
(Ideally, it would suspend nothing. But, if necessary, it can resume
everything instead of calling the actual shutdown code).
The save function doesn't need to know anything now that it didn't know
before...
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
|
|
|
|
|