Firobe
commented
1 day ago Hi Sebastian! I'll let the urunc devs answer as well but this is probably not the approach you want to take. The easiest way to have native MirageOS support in urunc would probably be to try to adapt the Rumprun support for MirageOS, since both use solo5-hvt/spt. But this is non-trivial work, especially since MirageOS doesn't have established conventions for storage/networking.
What you're trying to do is using the virtio target with the unikraft support of urunc, which you will have a hard time making work. Mirage's virtio target is quite limited and here urunc is trying to pass devices and command-line arguments in a way that MirageOS doesn't understand (e.g. the netdev.ip=.... is Unikraft-specific).
The best way to run MirageOS with urunc is currently the in-development qemu target for MirageOS, which relies on Unikraft and so works well with urunc. That target is not yet released but we're making a tool that'll automate that process and produce urunc-compatible images from MirageOS applications.
cmainas
I have been trying to run a unikernel created using MirageOS and run it with the help of urunc. I am aware that urunc isn't made to work with MirageOS unikernels in mind, but it would help me a lot if you could give me some pointers for the problems that I came across.
System Info
As mentioned above, I tried 2 unikernels, they are both used as examples in the mirageOS-skeleton. The guide on how they work can be found on the getting started page (Step1:Hello World! and Step 4: Networking) of mirageOS.
Before I get to the problems found with the networking unikernel, I would like first to show the errors with the hello world example found at Step1: Hello World! in the same getting started guide.
The steps I took to build the unikernel are:
mirage configure -t virtio(Similar erros or different ones appear if I build the unikernel for different VMM's)make dependsdune buildRunning the unikernel simply with
/usr/bin/qemu-system-x86_64 -m 256M -cpu host -enable-kvm -nographic -vga none -kernel dist/hello.virtiowill result in the correct behaviour, which is to display hello 4 times.After this, I tried to build a docker image with this unikernel with the following files: Dockerfile:
To deploy the image, I made a unikernel.yaml:
And the final result is:
The command that was given to qemu to launch this unikernel was:
Now, seeing this error led me to believe that this could be caused by a network component missing from my unikernel. To try and resolve this I tried building the network unikernel found in the mirageOS starting guide Step4: Networking.
The building process of the unikernel is similar:
mirage configure -t virtiomake dependsdune buildI used this command to start the unikernel:
/usr/bin/qemu-system-x86_64 -m 256M -cpu host -enable-kvm -nographic -vga none -kernel dist/network.virtioPerhaps I am missing some arguments since this is the result:
I was hoping that urunc would solve the networking issues so I prepared a docker image to use. Dockerfile:
urunc.json:
unikernel.yaml:
And the final result found in the logs of the created pod is:
Removing the "dummy" word from the commandline in the dockerfile/urunc.json results in the same error.
I am hoping you could guide me where to look in order to find what is missing in my approach. Thank you in advance!