Jim Paris wrote:
> Hi,
>
>   
>> - add file:// migration protocol (Uri Lublin)
>>     
>
> commit 70d2a9dc3594446f3ad66b32abc94c08b74118d4
> Author: Uri Lublin <[EMAIL PROTECTED]>
> Date:   Thu Feb 21 15:00:50 2008 +0200
>
>     kvm: qemu: migration: added file:// migration protocol
>     
>     Instead of writing into a file with fork+exec, just open the file and
>     write the data. This solves a bug that sometimes not all the data was
>     kept in the state-file.
>
> I haven't tested it yet, but this sounds like the problems I've always
> had with migration.  It seems this is just a new way to work around
> it, rather than an actual fix for the bug though -- won't exec: still
> have the same problem even when not writing to a file?  Was this
> ever tracked down any further?  Or is there a known reason why 
> "exec:dd" is expected to be broken?  I never had any luck finding it..
>
>   

IIRC it was signal handling related, the exec'ed process receives a 
signal and is prematurely terminated.


-- 
Do not meddle in the internals of kernels, for they are subtle and quick to 
panic.


-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
kvm-devel mailing list
kvm-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/kvm-devel

Reply via email to