From: Ryan Harper <ryanh@us.ibm.com>
To: Jan Kiszka <jan.kiszka@siemens.com>
Cc: kvm <kvm@vger.kernel.org>, Juan Quintela <quintela@redhat.com>,
qemu-devel <qemu-devel@nongnu.org>,
Ryan Harper <ryanh@us.ibm.com>, Liran Schour <LIRANS@il.ibm.com>,
Pierre Riteau <Pierre.Riteau@irisa.fr>
Subject: [Qemu-devel] Re: Live migration of x86-64 kvm guests broken?
Date: Wed, 2 Dec 2009 13:10:29 -0600 [thread overview]
Message-ID: <20091202191029.GU27346@us.ibm.com> (raw)
In-Reply-To: <4B16B583.7010005@siemens.com>
* Jan Kiszka <jan.kiszka@siemens.com> [2009-12-02 12:45]:
> >>>
> >> So far, so consistent. Could you try kvm-kmod-2.6.32-rc7 on top of that?
> >>
> >
> > Sure, can you remind me of the kvm-kmod build magic for building that
> > branch?
> >
>
> If you want to build from git, check Wolfgang's nice README. But it
> might be easier to just download the tarball from sourceforge.
Indeed, tarball is easiest. Still working on top of qemu.git+vmstate
fixes. Here's my invocation:
Source:
sudo ./x86_64-softmmu/qemu-system-x86_64 -L pc-bios -m 512 -drive
file=/media/blackstar/images/rhel5-64.raw,if=ide -net nic,model=e1000
-monitor stdio -enable-kvm
Dest:
sudo ./x86_64-softmmu/qemu-system-x86_64 -L pc-bios -m 512 -drive
file=/media/blackstar/images/rhel5-64.raw,if=ide -net nic,model=e1000
-monitor stdio -enable-kvm -incoming tcp:0:4444
Lemme try qemu-kvm.git
--
Ryan Harper
Software Engineer; Linux Technology Center
IBM Corp., Austin, Tx
ryanh@us.ibm.com
next prev parent reply other threads:[~2009-12-02 19:11 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-02 15:24 [Qemu-devel] Live migration of x86-64 kvm guests broken? Jan Kiszka
2009-12-02 16:44 ` [Qemu-devel] " Ryan Harper
2009-12-02 18:05 ` Jan Kiszka
2009-12-02 18:10 ` Ryan Harper
2009-12-02 18:16 ` Jan Kiszka
2009-12-02 18:35 ` Ryan Harper
2009-12-02 18:44 ` Jan Kiszka
2009-12-02 19:10 ` Ryan Harper [this message]
2009-12-02 19:24 ` Ryan Harper
2009-12-02 19:26 ` Jan Kiszka
2009-12-02 18:16 ` Juan Quintela
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=20091202191029.GU27346@us.ibm.com \
--to=ryanh@us.ibm.com \
--cc=LIRANS@il.ibm.com \
--cc=Pierre.Riteau@irisa.fr \
--cc=jan.kiszka@siemens.com \
--cc=kvm@vger.kernel.org \
--cc=qemu-devel@nongnu.org \
--cc=quintela@redhat.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;
as well as URLs for NNTP newsgroup(s).