From: Jim Paris <jim@jtan.com>
To: Avi Kivity <avi@qumranet.com>, Uri Lublin <uril@qumranet.com>
Cc: kvm-devel <kvm-devel@lists.sourceforge.net>
Subject: Re: [ANNOUNCE] kvm-62 release
Date: Tue, 26 Feb 2008 17:30:49 -0500 [thread overview]
Message-ID: <20080226223048.GA13028@jim.sh> (raw)
In-Reply-To: <47C42A18.9050006@qumranet.com>
Hi,
> - add file:// migration protocol (Uri Lublin)
commit 70d2a9dc3594446f3ad66b32abc94c08b74118d4
Author: Uri Lublin <uril@qumranet.com>
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..
-jim
-------------------------------------------------------------------------
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/
next prev parent reply other threads:[~2008-02-26 22:30 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-26 15:02 [ANNOUNCE] kvm-62 release Avi Kivity
2008-02-26 15:37 ` Haydn Solomon
2008-02-26 22:30 ` Jim Paris [this message]
2008-02-27 7:44 ` Avi Kivity
2008-02-27 10:29 ` Uri Lublin
2008-02-27 11:12 ` Avi Kivity
-- strict thread matches above, loose matches on Subject: below --
2008-03-05 18:09 Avi Kivity
2008-03-05 18:14 ` Alexey Eremenko
2008-03-05 18:48 ` Avi Kivity
2008-03-06 8:13 ` Alexey Eremenko
2008-03-06 8:18 ` Avi Kivity
2008-03-05 18:17 ` Avi Kivity
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20080226223048.GA13028@jim.sh \
--to=jim@jtan.com \
--cc=avi@qumranet.com \
--cc=kvm-devel@lists.sourceforge.net \
--cc=uril@qumranet.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox