From mboxrd@z Thu Jan 1 00:00:00 1970 From: Avi Kivity Subject: Re: [ANNOUNCE] kvm-62 release Date: Wed, 27 Feb 2008 09:44:56 +0200 Message-ID: <47C514F8.4000305@qumranet.com> References: <47C42A18.9050006@qumranet.com> <20080226223048.GA13028@jim.sh> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Cc: kvm-devel , Uri Lublin To: Jim Paris Return-path: In-Reply-To: <20080226223048.GA13028@jim.sh> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: kvm-devel-bounces@lists.sourceforge.net Errors-To: kvm-devel-bounces@lists.sourceforge.net List-Id: kvm.vger.kernel.org Jim Paris wrote: > Hi, > > >> - add file:// migration protocol (Uri Lublin) >> > > commit 70d2a9dc3594446f3ad66b32abc94c08b74118d4 > Author: Uri Lublin > 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/