Google Git
Sign in
fuchsia / fuchsia / 3338415d5071d602ba97b27cd2d6cf402dcf70d0 / . / src / proc / bin / starnix
tree: 713af821c2b4eabf14991ed9e3d6880e2d5660f9 [path history] [tgz]
  1. collections/
  2. fixtures/
  3. fs/
  4. meta/
  5. auth.rs
  6. BUILD.gn
  7. decision-log.md
  8. loader.rs
  9. logging.rs
  10. macro.rs
  11. main.rs
  12. mm.rs
  13. README.md
  14. syscall_table.rs
  15. syscalls.rs
  16. task.rs
  17. uapi.rs
  18. user_address.rs
src/proc/bin/starnix/README.md

Starnix

Starnix is a component that runs Linux binaries on Fuchsia. Currently, starnix is highly experimental and can run only trivial programs.

How to run starnix

Currently, we require a x86_64 host Linux system to run starnix.

Configure your build

In order to run starnix, we need to build //src/proc:

$ fx set core.x64 --with //src/proc,//src/proc:tests
$ fx build

Run Fuchsia

Run Fuchsia as normal, for example using fx serve and fx emu -N.

To monitor starnix, look for log messages with the starnix tag:

fx log --tag starnix

Run a Linux binary

To run a Linux binary, ask starnix to start a component that wraps the binary:

$ ffx starnix start fuchsia-pkg://fuchsia.com/hello-starnix#meta/hello_starnix.cm

If this is the first time you've used the ffx starnix command, you might need to configure ffx to enable the starnix commands. Attempting to run the start command should provide instructions for enabling the starnix commands.

If everything is working, you should see some log messages like the following:

[00064.846853][33707][33709][starnix, starnix] INFO: main
[00064.847640][33707][33709][starnix, starnix] INFO: start_component: fuchsia-pkg://fuchsia.com/hello-starnix#meta/hello_starnix.cm

Run a Linux test binary

Linux test binaries can also be run using the Starnix test runner using the standard fx test command:

$ fx test hello-starnix-test --output

You should see output like:

Running test 'fuchsia-pkg://fuchsia.com/hello-starnix-test#meta/hello_starnix_test.cm'
[RUNNING]       fuchsia-pkg://fuchsia.com/hello-starnix-test#meta/hello_starnix_test.cm
[PASSED]        fuchsia-pkg://fuchsia.com/hello-starnix-test#meta/hello_starnix_test.cm

In the device logs you should see output like:

[starnix, starnix_runner] INFO: main
[starnix, starnix_runner] INFO: start_component: fuchsia-pkg://fuchsia.com/hello-starnix-test#meta/hello_starnix_test.cm
[starnix, strace] INFO: 1(0x1, 0x35a3ca6000, 0xe, 0x0, 0x0, 0x0)
[starnix, starnix_runner::syscalls] INFO: write: hello starnix

[starnix, strace] INFO: -> 0xe
[starnix, strace] INFO: 60(0x0, 0x35a3ca6000, 0xe, 0x0, 0x0, 0x0)
[starnix, starnix_runner::syscalls] INFO: exit: error_code=0
[starnix, strace] INFO: -> 0x0

Testing

Using a locally built syscalls test binary

The syscalls_test test runs a prebuilt binary that has been built with the Android NDK. You can substitute your own prebuilt binary using the starnix_syscalls_test_label GN argument:

$ fx set core.x64 --args 'starnix_syscalls_test_label="//local/starnix/syscalls"' --with //src/proc,//src/proc:tests

Build your syscalls binary and put the file in //local/starnix/syscalls. (If you are building using the Google-internal build system, be sure to specific the --config=android_x86_64 build flag to build an NDK binary.)

You can then build and run your test as usual:

$ fx build
$ fx test syscalls_test