[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] Re: [Xen-devel] Error in XendCheckpoint: failed to flush file
I'm not sure the two are related. Fsync, lseek(), fadvise() will all fail if the fd maps to a socket. The failure is harmless and the error return code is ignored. The error to xend.log is overly noisy and needs cleaning up but unfortunately the suspend/resume problems probably lie elsewhere. What failure symptoms do you see? -- Keir On 28/2/07 04:46, "Stefan Berger" <stefanb@xxxxxxxxxx> wrote: > I get these errors pretty often lately. This is on a x86-32 machine with > changes 14142. Does anyone else these this? Local migration and > suspend/resume fail quite frequently. > > [2007-02-27 23:39:56 20114] DEBUG (XendCheckpoint:236) > [xc_restore]: /usr/lib/xen/bin/xc_restore 23 262 18432 1 2 0 0 0 > [2007-02-27 23:39:56 20114] INFO (XendCheckpoint:343) xc_linux_restore > start: max_pfn = 4800 > [2007-02-27 23:39:56 20114] INFO (XendCheckpoint:343) Reloading memory > pages: 0% > [2007-02-27 23:39:56 20114] INFO (XendCheckpoint:343) Saving memory > pages: iter 1 37%ERROR Internal error: Failed to flush file: Invalid > argument (22 = Invalid argument) _______________________________________________ Xen-devel mailing list Xen-devel@xxxxxxxxxxxxxxxxxxx http://lists.xensource.com/xen-devel
|
![]() |
Lists.xenproject.org is hosted with RackSpace, monitoring our |