From: Ian Campbell <Ian.Campbell@citrix.com>
To: Sagun Garg <sagun@nexchanges.com>
Cc: xen-devel@lists.xen.org
Subject: Re: Install Xen on ARM in a bare metal fashion on a Nexus Phone/Tablet or an ARM emulator
Date: Fri, 5 Dec 2014 09:32:20 +0000 [thread overview]
Message-ID: <1417771940.22808.39.camel@citrix.com> (raw)
In-Reply-To: <CALwCXQCd-RKXPcLuP+uEa_-g-wmjTm5-2n9YB2oA6RSyJLii4g@mail.gmail.com>
Please don't top post.
On Fri, 2014-12-05 at 14:51 +0530, Sagun Garg wrote:
> Thanks Ian for helping me with the links,
>
>
> FYI, I found following link :
> https://blog.xenproject.org/2014/04/01/virtualization-on-arm-with-xen/
> (Here it suggests using Foundation Model and Linaro, basically an
> emulator to get started) though the advanced emulators offered by ARM
> are paid ones)
>
>
> Would it be possible to install these ARM emulators on say AWS
> Amazon / Digital Ocean with the free subscription to try and test
> these out ?
Those emulators will run on any x86 system, whether it is virtualised by
Amazon/DO or not. They are quite CPU intensive though.
> Amazon uses Xen as the underlying virtualization technology and it
> also uses custom kernels since last 2 years so coincidentally it might
> just work though the question is how (I read this somewhere on a blog,
> but I can't point a link to it as I don't remember it, but would you
> know of such a tuturial / link where someone else has pursued the
> same ?)
Amazon offers x86 Xen, not ARM Xen. Xen does not do any kind of
cross-architecture virtualisation (i.e. running ARM OSes on X86, or vice
versa). So the fact that Amazon happens to run x86 Xen is of no use when
you want to run ARM Xen.
> or would you know of any "RISC as a Service with ARM processors" that
> can be provisioned on demand like AWS where we can install XEN on ARM
> directly ? Any cloud offering that can be used would be of great help.
I'm not aware of any cloud service offering ARM at the moment.
> Also I was wondering what are the risks / or rather shortcomings in
> trying directly on the device Nexus / or any other ARM phone which has
> been tested for the same.
Not sure what sorts of risks you mean, I don't think there is anything
Xen specific here, just the usual stuff with running an untested OS on
any new platform.
I don't know if Nexus devices are brickable, but if so then that might
be an issue with trying any untested OS on them.
Phones and the like aren't typically very good debug platforms (i.e. no
serial, no JTAG etc) so running an untested OS on them can end up being
hard (but not impossible) to debug if it doesn't work, that's why
platforms such as the Arndale exist -- they are mobile phones with all
the extra useful debug stuff brought out to headers.
Ian.
next prev parent reply other threads:[~2014-12-05 9:32 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-04 10:14 Install Xen on ARM in a bare metal fashion on a Nexus Phone/Tablet or an ARM emulator Sagun Garg
2014-12-04 10:29 ` Ian Campbell
2014-12-05 9:21 ` Sagun Garg
2014-12-05 9:32 ` Ian Campbell [this message]
2014-12-05 11:16 ` Julien Grall
2014-12-06 8:58 ` Sagun Garg
2014-12-08 12:43 ` Ian Campbell
[not found] ` <CALwCXQBxLZnX1JX10JDEtA7whUZohFSb2jutNghU33SEwZ3gJQ@mail.gmail.com>
2014-12-08 12:47 ` Ian Campbell
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=1417771940.22808.39.camel@citrix.com \
--to=ian.campbell@citrix.com \
--cc=sagun@nexchanges.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.