-
Notifications
You must be signed in to change notification settings - Fork 63
how to build a local kernel #352
Comments
@telala yes that is the right way. And it depends on hyperd to build the kernel. If you do not have that installed locally, you can change |
@bergwolf got a lot of errors while compiling the kernel while running "make kernel-local". I changed the dockerfile.x86_64 a little as following: FROM centos:latest RUN yum install -y gcc ncurses-devel make openssl-devel bc perl ENV KERNEL_VERSION 4.12.4 ENV KBUILD_BUILD_USER dev RUN mkdir /root/build/ && mkdir /root/build/result/ #RUN cd /root/build/linux-${KERNEL_VERSION}/ && for patch in /root/build/kernel_patch/*.patch; do patch -p1 <$patch || exit 1; done _following is the compiling errors: ��{standard input}: �hAssembler messages: there are a lot of compiling errors besides the above. |
@telala it looks like gcc got oom-killed. Are you using |
@bergwolf after replace hyperctl to docker I can build the kernel and initrd successfully. I noticed that a modules.tar file is created too. How to use the modules.tar? |
@telala |
@bergwolf when using the built local kernel to start a container got error: any advice? |
@telala are you able to run with the kernel and initrd in hyperstart w/o modification? If you can, I'd suspect your kernel config options. |
@bergwolf yes. I just tried to use the original initrd and kernel to start runv it worked. |
@telala There are certain kernel config options required for the hyperstart guest to boot. Please try to use the kernel config in hyperstart and enable other options you need in your kernel. |
@bergwolf I tried to use the default kernel 4.12.4 in the Dockerfile and it worked. The local kernel can be started successfully by runv. |
I am using runv and need to use my own kernel for the vm rather than the default one of hyperstart.
Then I tried to build my own kernel using hyperstart.
Is this the right way to build local kernel?
The text was updated successfully, but these errors were encountered: