From: Marc Zyngier <marc.zyngier@arm.com>
To: ib10evp0@gmx.org
Cc: kvmarm@lists.cs.columbia.edu
Subject: Re: Status of live migration on ARMv7
Date: Tue, 14 Jun 2016 20:20:25 +0100 [thread overview]
Message-ID: <20160614202025.226dd45d@arm.com> (raw)
In-Reply-To: <trinity-d5cbcace-be15-4c67-b55c-1a70d1fb7c21-1465735240100@3capp-gmx-bs77>
On Sun, 12 Jun 2016 14:40:40 +0200
ib10evp0@gmx.org wrote:
> Hi,
>
> I was wondering what the status of live migration for ARMv7 with
> Virtualization Extensions is. I saw somebody was able to live migrate
> on ARM [1] but the repository he linked [2] has not been updated for
> 2 years. I'd like to know if live migration support for ARM is
> already in the mainstream kernel or if there are any custom patches
> required and if so if there is any newer code than [2].
Everything that's needed for a typical ARMv7 is already in mainline,
both for the kernel and qemu. And since the code is almost entirely
shared with ARMv8, it is probably in the same state. If it not working,
then it is a bug that should be addressed.
> BTW: The Migration page [3] claims the migration feature is hardware
> independent but it remains unclear if this expands to CPU
> architectures and if this applies to live migration or only offline
> migration. Some clarification in this regard would be nice to have.
We do have support for live migration (migrating the VM whilst it is
still running, tracking memory that gets dirtied).
M.
--
Jazz is not dead. It just smells funny.
next prev parent reply other threads:[~2016-06-14 19:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-12 12:40 Status of live migration on ARMv7 ib10evp0
2016-06-14 19:20 ` Marc Zyngier [this message]
2016-06-14 20:52 ` ib10evp0
2016-06-14 21:09 ` Marc Zyngier
2016-06-15 7:57 ` ib10evp0
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=20160614202025.226dd45d@arm.com \
--to=marc.zyngier@arm.com \
--cc=ib10evp0@gmx.org \
--cc=kvmarm@lists.cs.columbia.edu \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.