-
Notifications
You must be signed in to change notification settings - Fork 18
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Issues are for discussion #1
Comments
Hello, I am new to Linux kernel. I am currently using ubuntu 14.04 and trying to simulate the unikernels that you are talking about. I can build the unikernels for mysql, php and nginx. Only one of them stays up when started without the macvtap patch. I am not quite clear how the patch should be applied. Do i need to download the 4.1.3 Linux kernel in order to fix this or can I get away with building loadable kernel module (macvtap.ko) for macvtap alone. I tried to build the Linux kernel for 4.1.3 without success. Any details on this patch would be helpful to simulate this. Thank you. |
Hi Murty, |
Hi Martin, Thank you very much for the feedback. That is very helpful. I would try Murty On Wed, Jan 6, 2016 at 4:11 AM, Martin Lucina [email protected]
Murty |
@mato Do you know if the macvtap issue is being addressed upstream? |
@danehans Not at the moment. We're working on a way of getting equivalent functionality without the need for macvtap, which will work without the need to upgrade the kernel on existing systems. Having said that, the lack of proper namespace support in macvtap is a legit issue, so feel free to take it up with upstream. |
Hi, I have a question. This approach allow me to run a tiny VM with unikernel inside a container, right? |
We'll use the issue tracker here for discussion and questions about the code in the demo.
Since this was presented as a 'cool hack' [1], we're not expecting to push any new commits to this codebase, so any feedback will make it's way into our future work.
Thanks!
[1] http://unikernel.org/blog/2015/contain-your-unikernels/
The text was updated successfully, but these errors were encountered: