[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: [Xen-devel] Domain save/migrate issue

  • To: "Anthony Liguori" <aliguori@xxxxxxxxxx>
  • From: "Noam Taich" <noam.taich@xxxxxxxxxxxx>
  • Date: Wed, 15 Feb 2006 08:42:38 -0800
  • Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
  • Delivery-date: Wed, 15 Feb 2006 16:55:07 +0000
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>
  • Thread-index: AcYyTJ57BZu+BG+oSdygWCxiDG2/kwAACDMg
  • Thread-topic: [Xen-devel] Domain save/migrate issue

Noam Taich wrote:
> 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 
Why exactly would this be better than just making domain's

All it would take is some hypervisor plumbing...


Anthony Liguori

Better? I don't know, I hold judgment as to whether or not domains
should be made unsuspendable, I just offer to add an option.
If there is no other need for domain suspension, it can replace the old

About the hypervisor plumbing issue, isn't it just a matter of going
over all the smaller suspend functions the main suspend function calls
and make the changes there? Making sure nothing else gets suspended, 
and changing the code that goes over the drivers and handles the
So far, I haven't seen anything that would indicate it would entail
in the far reaches of hypervisor space...

Then again... am I wrong? 

Xen-devel mailing list



Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.