The focus of this session will be on porting new libraries to Unikraft and preparing them for upstreaming to the main organization’s GitHub.

Being a library operating system, the unikernels created using Unikraft are mainly a collection of internal and external libraries, alongside the ported application. As a consequence, a large library pool is mandatory in order to make this project compatible with as many applications as possible.


From earlier sessions, we saw that we can add an external library as a dependency for an application by appending it to the $LIBS variable in the application’s Makefile:

LIBS := $(UK_LIBS)/my_lib

Having done that, we can then select it in the menuconfig interface in order for the library to be included in the build process.

Running an unikernel built for kvm can be done using the qemu command as follows:

$ qemu-system-x86_64 -kernel unikraft_unikernel -nographic

The -nographic argument redirects the output generated by the unikernel to the console.

In Session 02: Behind the Scenes we saw that there are two types of libraries:

  • internal, which are generally part of the kernel / core (schedulers, file systems, etc.);
  • external: which mostly provide user space-level functionalities

The external libraries should be placed in the $UK_LIBS folder, which is by default $UK_WORKDIR/libs, and the applications should be placed in the $UK_APPS folder, which is by default $UK_WORKDIR/apps.

The default working directory structure looks like this:

|-- apps - This is where you would normally place existing app builds
|-- archs - Here we place our custom arch's files
|-- libs - This is where the build system looks for external library pool sources
|-- plats - The files for our custom plats are placed here
`-- unikraft - The core source code of the Unikraft Unikernel

and the relevant environment variables regarding the working directories are:

Environment Variable Purpouse Default
UK_WORKDIR The root directory, where all unikraft components are stored ———————-
UK_ROOT The directory for Unikraft’s core source code $UK_WORKDIR/unikraft
UK_LIBS The directory of all the external Unikraft libraries $UK_WORKDIR/libs
UK_APPS The directory of all the template applications $UK_WORKDIR/apps


Support Files

Session support files are available in the repository. If you already cloned the repository, update it and enter the session directory:

$ cd path/to/repository/clone

$ git pull --rebase

$ cd content/en/community/hackathons/sessions/contributing-to-unikraft/

$ ls -F  work/ sol/ content/

If you haven’t cloned the repository yet, clone it and enter the session directory:

$ git clone

$ cd docs/content/en/community/hackathons/sessions/contributing-to-unikraft/

$ ls -F  work/ sol/ content/

Git Structure

The organization’s GitHub contains the main Unikraft repository and separate repositories for external libraries, as well as already ported apps. In the previous sessions, we saw that the Unikraft repository consists of internal libraries, platform code and architecture code. The Unikraft code doesn’t have any external dependencies, in contrast to the external libraries or applications, which can have external dependencies.

External libraries can have more specific purposes. So, we can port a library even just for a single application. The process of adding new internal libraries is almost the same as for external ones, so further we will focus on porting an external library.

Also, the main repository has open issues to which you can contribute. In general, this process is done by solving the issue on your personal fork of the project, and after that making a pull request (PR) with your solution. For more specific details about creating a PR while following the comunity guidelines, check the Contributing page on the Unikraft documentation website.

Example of External Library

Let’s focus for now on an already ported library: lib-libhogweed. Let’s examine its core components. Go to the work/01-tut-porting/libs/libhogweed/ directory and follow the bookmarks marked with USOC_X, where X is the index of the item in the list, from the files specified in the sections below.

Glue Code

In some cases, not all the dependencies of an external library are already present in the Unikraft project, so the solution is to add them manually, as glue code, to the library’s sources.

Another situation when we need glue code is when the ported library comes with test modules, used for testing the library’s functionalities. The goal, in this case, is to wrap all the test modules into one single function. In this way, we can check the library integrity if we want so by just a single function call. Moreover, we can create a test framework which can periodically check all of the ported libraries, useful especially for detecting if a new library will interfere with an already ported one.

Moving back to libhogweed, a practical example of the second case is the run_all_libhogweed_tests(int v) function from libhogweed/testutils_glue.c #674, which calls every selected test module (we will see later how we can make selectable config variables) and returns EXIT_SUCCESS only if it passes over all the tests. For exposing this API, we should also make a header file with all of the test modules, as well as our wrapper function. The header can be found at libhogweed/include/testutils_glue.h.

The file stores all the config variables, which will be visible in make menuconfig. These variables can be accessed from or even from C sources, by including "uk/config.h", using the prefix CONFIG_.

Moving to the source code, libhogweed/, we have:

  1. The main variable of the library which acts as an identifier for it:

    menuconfig LIBHOGWEED
    	bool "libhogweed - Public-key algorithms"
    	default n
  2. We can also set another library’s main variable, in this case newlib, which involves including it in the build process:

    select LIBNEWLIBC
  3. Creating an auxiliary menu, containing all the test cases:

    config TESTSUITE
    		bool "testsuite - tests for libhogweed"
    		default n
    		if TESTSUITE
    			config TEST_X
    				bool "test x functionality"
    				default y

    Each test case has its own variable in order to allow testing just some functions from the whole suite.

The libhogweed/ file is used to:

  1. Register the library to Unikraft’s build system:

    $(eval $(call addlib_s,libhogweed,$(CONFIG_LIBHOGWEED)))

    As you can see, we are registering the library to Unikraft’s build system only if the main library’s config variable, LIBHOGWEED, is set.

  2. Set the URL from where the library will be automatically downloaded at build time:

  3. Declare helper variables for the most used paths:


    There are some useful default variables, for example:

    • $LIBNAME_ORIGIN: represents the path where the original library is downloaded and extracted during the build process;
    • $LIBNAME_BASE: represents the path of the ported library sources(the path appended to the $LIBS variable).
  4. Set the locations where the headers are searched:

    // including the path of the glue header added by us

    You should include the directories with the default library’s headers as well as the directories with the glue headers created by you, if it’s the case.

  5. Add compile flags, used, generally, for suppressing some compile warnings and making the build process neater:

    LIBHOGWEED_SUPPRESS_FLAGS += -Wno-unused-parameter \
            -Wno-unused-variable -Wno-unused-value -Wno-unused-function \
            -Wno-missing-field-initializers -Wno-implicit-fallthrough \
            -Wno-pointer-to-int-cast -Wno-int-to-pointer-cast
  6. Register the library’s sources:

  7. Register the library’s tests:

    LIBHOGWEED_SRCS-y += $(LIBHOGWEED_EXTRACTED)/testsuite/rsa-compute-root-test.c
    LIBHOGWEED_RSA-COMPUTE-ROOT-TEST_FLAGS-y += -Dtest_main=rsa_compute_root_test

    There are situations when the test cases each have their own main() function. In order to wrap all the tests into one single main function, we have to modify their main function name by using preprocessing symbols.

    Note: A good practice is to include a test only if the config variable corresponding to that test is set.

  8. This step is very customizable, being like a script executed before starting to compile the unikernel.

    In most cases, and in this case too, the libraries build their own config file through a provided executable, usually named configure:

    	$(call verbose_cmd,CONFIG,libhogweed: $(notdir [email protected]), \
            cd $(LIBHOGWEED_EXTRACTED) && ./configure --enable-mini-gmp \

    We can also do things like generating headers using the original building system, modify sources, etc.


Let’s check the integrity of this library using its test suite through the exposed wrapper function.

For this task, you have to move the library in the $UK_LIBS folder and the work/01-tut-porting/apps/app-libhogweed application in the $UK_APPS folder. You can also keep the current directory structure and clone the Unikraft core repository in the work/0x-task-name directory, basically changing the UK_WORKDIR to work/0x-task-name, as described above. Fill the TODO lines from the application code: add the libhogweed library as a dependency in its Makefile and call the function exposed by the library for running the test suite from main.c. Remember to include the library header file.

Disable some tests, rebuild, and run the checker application again.

Note: The libhogweed library depends on newlib.

Note: Remember to select the test suite from menuconfig. You can also check the library’s for additional information.

Hint: The order of the libhogweed and newlib libraries in the Makefile matters.


We need a large library pool in order to make the Unikraft project compatible with as many applications as possible.

There are also many ways in which you can contribute to the Unikraft project, and you can find them in the issues section of the main repository.

Practical Work

Moving to a more hands-on experience, let’s port a new library.

Support Files

Session support files are available in the repository. If you already cloned the repository, update it and enter the session directory:

$ cd path/to/repository/clone

$ git pull --rebase

$ cd content/en/community/hackathons/sessions/contributing-to-unikraft/

$ ls -F  work/

If you haven’t cloned the repository yet, clone it and enter the session directory:

$ git clone

$ cd docs/content/en/community/hackathons/sessions/contributing-to-unikraft/

$ ls -F  work/

00. Prepare

Let’s suppose that we need kd tree support and that we found a C library, kdtree, that does what we need. After downloading and inspecting this library, we can see that it also has a set of examples, which can be used by us to test if we ported this library properly. Move the skeleton of this library, work/02-task-porting/src/libs/kdtree/, in the $UK_LIBS directory and complete the porting process by following the TODO lines. For all the work items you can (and should) use the files from the tutorial as reference.

01. Declare Library Identifier

Let’s start by declaring a new config variable in the file. As stated before, this variable will represent the library’s identifier.

02. Register it to the Build System

For the next steps, the working file will be from the library’s skeleton. Let’s use the previously declared variable: register the library to the build system only if the variable is set.

03. Set its URL

Having the library registered, set the URL from where it will be downloaded at build time, and explicitly fetch it. Also set a variable for the library version. Get the latest version number from the library website.

04. Helper Variables

Make a variable with the path of the default directory obtained by extracting the original library’s archive.

05. Headers Location

Add the directory which contains the library’s header.


06. Add Sources

Add the library’s C sources.


07. Additional Requirements

Check the original library’s README to see if it needs to be configured first, and add the proper rule if so.

Note: Make sure to also check the library file for aditional dependencies.

Hint: As in most ported libraries, a configuration step is required and it consists in simply running a script.

08. Intermediary Check

Until now we have registered the library and its sources, and we should be able to compile an unikernel with it if it doesn’t have any more unresolved dependencies. Move the work/02-task-porting/src/apps/app-kdtree application in the $UK_APPS directory, fill its Makefile, and use it to build an unikernel with our ported library as a dependency!

If needed, provide additional flags in order to suppress the compile warnings generated by this library.

Note: You can leave the application’s main() function empty for now, the resulted unikernel will just print the Unikraft banner.

Hint: Check the tutorial for adding dependencies.

09. Add Test Config Variables

Now let’s make a wrapper for the test cases provided as examples. Uncomment lines #7-#15 from the library’s and complete TODO_9 by adding new config variables for each test case.

10. Register Test Sources

Moving back to the library’s, register the tests sources to the build system.

Note: Inspect the functions from the tests.

Hint: Use preprocessing symbols to rename the tests main functions, in order to use them later.

11. Wrapper Glue

Integrate all the test functions into a glue main. Also, update the library’s include/test_suite_glue.h header accordingly.

Note: You can use test_suite_glue.c from the library’s skeleton.

12. Register Glue Code

Register both the glue test wrapper source and its header in

13. Final Verification

Test the resulted library by calling the test function from the app-kdtree application. If you did everything correctly, the output of the application should look something like this:

SeaBIOS (version 1.13.0-1ubuntu1.1)
Booting from ROM...
Powered by
o.   .o       _ _               __ _
Oo   Oo  ___ (_) | __ __  __ _ ' _) :_
oO   oO ' _ `| | |/ /  _)' _` | |_|  _)
oOo oOO| | | | |   (| | | (_) |  _) :_
 OoOoO ._, ._:_:_,\_._,  .__,_:_, \___)
                   Phoebe 0.10.0~3a997c1
Running test y ....................
inserting 10 random vectors... 0.000 sec
range query returned 0 items in 0.00000 sec
Running test z ....................
found 5 results:
node at (-3.463, -2.934, 7.719) is 8.108 away and has data=i
node at (-5.316, 2.205, 5.781) is 7.482 away and has data=f
node at (2.210, 3.937, -5.407) is 7.837 away and has data=h
node at (1.810, 8.039, -4.218) is 9.753 away and has data=g
node at (-2.347, -3.641, -7.053) is 9.144 away and has data=e
Total tests : 2
Total errors: 0

Note: Don’t forget to include the updated library header in the main application file.


If you reached this far, please do a 5 minutes tour through this quiz to assess your current understanding of the session.

Give Us Feedback

We want to know how to make the next sessions better. For this we need your feedback. Thank you!

Further Reading

You can get more in-depth information for the contributing process from the main documentation.