From: Charles Duffy <Charles_Duffy@messageone.com>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] Re: migrate
Date: Wed, 12 Nov 2008 16:32:26 -0600 [thread overview]
Message-ID: <gfflhr$av6$1@ger.gmane.org> (raw)
In-Reply-To: <0003255756625f029f045b753902@google.com>
kknapp@gmail.com wrote:
> Ok, in the qemu monitor screen I see the option for migration of an
> image but I've not been able to find any references on how to start up
> the receiving qemu session that where not for KVM. I searched the man
> page, the website, the wiki, and Google does the migration work in
> non-KVM qemu or not? If it does can someone give me the command line option.
On the receiving end:
receiving_host$ qemu-system-i386 ${YOUR_NORMAL_ARGS} -incoming
tcp:0.0.0.0:1234
On the sending end:
migrate tcp:receiving_host:1234
That said, I've heard of bugs with live migration of systems with USB
enabled; if you have problems, you might consider disabling it.
prev parent reply other threads:[~2008-11-12 22:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-12 3:02 [Qemu-devel] migrate kknapp
2008-11-12 22:32 ` Charles Duffy [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='gfflhr$av6$1@ger.gmane.org' \
--to=charles_duffy@messageone.com \
--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).