From: Fabrice Bellard <fabrice@bellard.org>
To: aliguori@cs.utexas.edu
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [RFC] QEMU Live Migration
Date: Wed, 24 Jan 2007 21:51:12 +0100 [thread overview]
Message-ID: <45B7C6C0.2020003@bellard.org> (raw)
In-Reply-To: <45B42BF9.6020604@cs.utexas.edu>
I looked at your patch and it is OK for me. The 'ssh:' implementation is
a nice trick. In order to be usable on win32, it is still needed to
implement a more portable system with a TCP connection.
The dirty flag 0x04 is unfortunately used by kqemu - I should have
documented it ! You can use 0x08 for the live migration.
Regards,
Fabrice.
Anthony Liguori wrote:
> Howdy,
>
> I wanted to post a draft of my QEMU live migration patch. I think
> there's a lingering memory allocation problem. I also need to implement
> ARP forwarding and a TCP transport stream.
>
> However, I thought I'd post an initial version in case anyone wants to
> play around with it.
>
> Once you apply the patch, make sure you've got it on both machines. For
> my setup, I've got a common NFS share mounted in /mnt. Then I run:
>
> qemu -hda /mnt/win2k.img -monitor telnet:0.0.0.0:1025,server,nowait -vnc :2
>
> Then, I connect to the monitor and execute:
>
> (qemu) migrate ssh://woolly
>
> When the migration completes, the monitor command will finish and then I
> can connect to the machine on woolly:2.
>
> The ssh command will be derived from argc/argv so it's important to
> ensure that the -hda path is valid on both machines.
>
> All three patches are required and should be applied in order of:
> qemu-apic-save-restore.diff qemu-file.diff qemu-migration.diff
>
> Regards,
>
> Anthony Liguori
prev parent reply other threads:[~2007-01-24 21:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-22 3:14 [Qemu-devel] [RFC] QEMU Live Migration Anthony Liguori
[not found] ` <64F9B87B6B770947A9F8391472E0321603496B19@ehost011-8.exch011.intermedia.net>
2007-01-24 16:49 ` [Qemu-devel] QEMU Live Migration: arp-like packet patch Uri Lublin
2007-03-26 9:53 ` Uri Lublin
2007-01-24 20:51 ` Fabrice Bellard [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=45B7C6C0.2020003@bellard.org \
--to=fabrice@bellard.org \
--cc=aliguori@cs.utexas.edu \
--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).