From: Andrew Cooper <andrew.cooper3@citrix.com>
To: Vijay Kilari <vijay.kilari@gmail.com>
Cc: "xen-devel@lists.xen.org" <xen-devel@lists.xen.org>,
Ian Campbell <Ian.Campbell@citrix.com>,
Stefano Stabellini <stefano.stabellini@eu.citrix.com>
Subject: Re: VM Migration on ARM
Date: Wed, 11 Mar 2015 10:51:53 +0000 [thread overview]
Message-ID: <55001E49.4040502@citrix.com> (raw)
In-Reply-To: <CALicx6u3_8NXBBR_NG4BZaytFu2YgA+0b+a7OsJVNrugfDF0Xg@mail.gmail.com>
On 11/03/15 05:32, Vijay Kilari wrote:
> Hi Andrew,
>
> From Ian & Stefano, I came to know that you have introduced
> Migration framework v2
> under below patch series
>
> http://marc.info/?l=xen-devel&m=141036915311145
>
> I have few queries:
>
> 1) Is there any plans/timeline to support for ARM32/ARM64?.
I will not personally be doing any ARM migration support, not even as
part of getting migration v2 accepted upstream.
> 2) Also does the Domain Image format specification for ARM is complete?
The spec has certain sentinel values for ARM already where it made sense
to just include them while writing.
It has no specific thought to ARM migration, but an ARM virtual machine
is exactly like an x86 HVM domain (from the toolstacks point of view),
other than the Qemu record. With any luck, no new additions to the spec
will be needed, but the spec is trivially extendible if required.
~Andrew
next prev parent reply other threads:[~2015-03-11 10:51 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-11 5:32 VM Migration on ARM Vijay Kilari
2015-03-11 10:51 ` Andrew Cooper [this message]
2015-03-11 11:04 ` Julien Grall
2015-03-11 11:47 ` Ian Campbell
2015-03-20 12:17 ` Vijay Kilari
2015-03-25 16:02 ` Andrew Cooper
2015-03-27 13:32 ` Vijay Kilari
2015-03-27 13:47 ` Andrew Cooper
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=55001E49.4040502@citrix.com \
--to=andrew.cooper3@citrix.com \
--cc=Ian.Campbell@citrix.com \
--cc=stefano.stabellini@eu.citrix.com \
--cc=vijay.kilari@gmail.com \
--cc=xen-devel@lists.xen.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 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.