qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Thomas Mueller <thomas@chaschperli.ch>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] Re: [5694] Reintroduce migrate-to-exec: support (Charles	Duffy)
Date: Thu, 13 Nov 2008 09:53:26 +0000 (UTC)	[thread overview]
Message-ID: <gfgtem$q3m$1@ger.gmane.org> (raw)
In-Reply-To: E1KzwNt-00014u-TS@cvs.savannah.gnu.org

On Tue, 11 Nov 2008 16:46:33 +0000, Anthony Liguori wrote:

> Revision: 5694
>           http://svn.sv.gnu.org/viewvc/?view=rev&root=qemu&revision=5694
> Author:   aliguori
> Date:     2008-11-11 16:46:33 +0000 (Tue, 11 Nov 2008)
> 
> Log Message:
> -----------
> Reintroduce migrate-to-exec: support (Charles Duffy)
> 
> KVM's live migration support included support for exec: URLs, allowing
> system state to be written or received via an arbitrary popen()ed
> subprocess. This provides a convenient way to pipe state through a
> compression algorithm or an arbitrary network transport on its way to
> its destination, and a convenient way to write state to disk; libvirt's
> qemu driver currently uses migration to exec: targets for this latter
> purpose.
> 
> This version of the patch refactors now-common code from migrate-tcp.c
> into migrate.c.


i applied this patch to the kvm-79 qemu.  

save and restore works with "migration exec:cat >/tmp/vm.state"/"-
incoming exec:cat /tmp/vm.state", altough there is an segfault logged to 
syslog:

[265193.983381] kvm[15017]: segfault at 0 ip 0 sp 7fffb85ecaa8 error 14 
in kvm[400000+1af000]

my system:
Intel E5420, debian etch, kernel 2.6.26

- Thomas

      reply	other threads:[~2008-11-13 10:00 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-11 16:46 [Qemu-devel] [5694] Reintroduce migrate-to-exec: support (Charles Duffy) Anthony Liguori
2008-11-13  9:53 ` Thomas Mueller [this message]

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='gfgtem$q3m$1@ger.gmane.org' \
    --to=thomas@chaschperli.ch \
    --cc=qemu-devel@nongnu.org \
    /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;
as well as URLs for NNTP newsgroup(s).