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

Re: [Xen-devel] Error in XendCheckpoint: failed to flush file

  • To: "Graham, Simon" <Simon.Graham@xxxxxxxxxxx>, Stefan Berger <stefanb@xxxxxxxxxx>, xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxx>
  • From: Keir Fraser <keir@xxxxxxxxxxxxx>
  • Date: Wed, 28 Feb 2007 17:17:20 +0000
  • Delivery-date: Wed, 28 Feb 2007 09:16:42 -0800
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>
  • Thread-index: AcdbBqwu6tNHM8b5Edu40AAWy6hiGQAL/KvwAAlrrsg=
  • Thread-topic: [Xen-devel] Error in XendCheckpoint: failed to flush file

On 28/2/07 16:15, "Graham, Simon" <Simon.Graham@xxxxxxxxxxx> wrote:

> Note that I thought about plumbing the live flag through to
> xc_linux_restore as is done with xc_linux_save but decided I didn't want
> to change the API... therefore I changed xc_linux_restore to figure out
> if the fd is a socket or not... hopefully this works on Solaris??? (just
> testing now).

Use of the live flag to gate the flush/sync calls is not a good idea. We can
'live save' to disc (checkpointing) and we can 'non-live migrate' via a
socket. So the live flag is not really an indicator of what the file
descriptor maps to (file vs. socket). Best to unconditionally try the
flush/sync and ignore errors.

 -- Keir

Xen-devel mailing list



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