Sorry for the lag. New Year's got in the way of my planned hacking sessions
:)
After my last email I continued to investigate my problems building
rumprun-xen and have some new info to share.
Summary: The combination of grsec's anti-exploit protections and musl libc
were responsible for the issues I was experiencing. I've been able to get
rumprun.sh, rumprun-posix, and rumprun-xen to all work without error once I
installed Ubuntu 14.04 w/Xen 4.4.1.
Details:
1) Not installing alpine-sdk did cause some of the errors I was seeing but
I believe they were spurious errors and not the actual root cause of my
problems.
2) I tried building rumprun-posix thinking this would be an easier path to
a working environment. Building the code was a fairly smooth process but
all rumpremote_listcmds would hang and never return.
3) At this point I began to suspect there was something systemically wrong
with my environment. To verify this was the case I built a fresh checkout
of buildrump.sh and ran the tests. init was the only test which worked. The
filesystem and network tests were killed by the OS which I thought was
pretty odd behavior. I recompiled with debug info and attached gdb to the
filesystem tests. Turns out they were dying with SIGILL which had me
puzzled for a bit.
4) Alpine Linux uses the grsec patchset (https://grsecurity.net) to harden
the kernel so I did some research on how it works. After some reading I
began to suspect it's anti-exploit mechanisms were tripping me up. I
re-imaged my dev box using Ubuntu 14.04 and was able to run code from
buildrump.sh, rumprun-posix, and rumprun-xen repos per the relevant READMEs
without any errors or problems.
Thanks to Antti & Martin for their help and patience. Hopefully this info
will be useful for future users. I'm excited to start playing with the code
now that I'm past my setup woes!
--Kevin
On Wed, Dec 31, 2014 at 12:18 PM, Antti Kantee <[email protected]> wrote:
> On 30/12/14 20:51, Kevin Smith wrote:
> > Good news, if slightly embarrassing :)
> >
> > Turns out Alpine Linux packages up items like libc headers and such into
> a
> > meta-package named 'alpine-sdk'. Installing it has made compilation much
> > happier.
>
> It's not obvious to me why not installing alpine-sdk would lead to the
> failure mode your described. I assume it has something to do with being
> unable to build the toolchain, but it really shouldn't fail that way. I
> like it when things fail in an obvious way (or better yet, not at all),
> so maybe we can still figure out how to make the failure better for
> people who try buildxen.sh in a similar scenario?
>
>
> ------------------------------------------------------------------------------
> Dive into the World of Parallel Programming! The Go Parallel Website,
> sponsored by Intel and developed in partnership with Slashdot Media, is
> your
> hub for all things parallel software development, from weekly thought
> leadership blogs to news, videos, case studies, tutorials and more. Take a
> look and join the conversation now. http://goparallel.sourceforge.net
> _______________________________________________
> rumpkernel-users mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/rumpkernel-users
>
------------------------------------------------------------------------------
Dive into the World of Parallel Programming! The Go Parallel Website,
sponsored by Intel and developed in partnership with Slashdot Media, is your
hub for all things parallel software development, from weekly thought
leadership blogs to news, videos, case studies, tutorials and more. Take a
look and join the conversation now. http://goparallel.sourceforge.net
_______________________________________________
rumpkernel-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/rumpkernel-users
