On 30/03/18 09:33, Ajay Garg wrote:
If you mean that there are problems because xen-on-arm isn't supported,
well, then yes, and there's no way around that except to add support.
Yep, this is the major hurdle.
Just curious, any particular reason why support for
rumprun-for-xen-on-arm isn't available (especially when support for
arm has been added into mini-os upstream)?
Is it just a matter of time, or some logical/architectural questions
still need to be figured out?
It's just a matter of someone copypasting the right bits from minios and
contributing them. Plus working out whatever else needs to be worked
out (which might be nothing). Waiting is one strategy, but it usually
fails when everyone applies the same strategy.
Rumprun doesn't really use minios, so much as a fraction of it (just the
name mini*OS* should give sufficient hint), and adds features missing
from minios. In retrospect, it would have been more efficient to start
from scratch and copypaste just the necessary bits from minios (*),
instead of starting with minios and uncopypasting the unnecessary bits.
For example, the build system for the xen side of Rumprun still isn't
skookum. Anyway, that's just a rationale for why something being
supported in "upstream" minios doesn't automatically solve every problem
here. Looking at the code (and build system) will expand on the subject.
*) or any other OS, but minios is probably the one where the necessary
bits exist and are the least tangled with everything else
