Add native arm64 support and cross-compilation for kernels #170
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
mtardy
force-pushed
the
pr/mtardy/arm64-support
branch
from
df82d20 to
b7c852d
Compare
|
I added some PRs in cilium/little-vm-helper-images:
I just need a last PR for the copy of the kernel modules in the image and then we should be able to run some tests on arm64 using the kind image. |
mtardy
commented
Mar 4, 2024
mtardy
force-pushed
the
pr/mtardy/arm64-support
branch
from
b7c852d to
9703c0a
Compare
Signed-off-by: Mahe Tardy <[email protected]>
Signed-off-by: Mahe Tardy <[email protected]>
Signed-off-by: Mahe Tardy <[email protected]>
Signed-off-by: Mahe Tardy <[email protected]>
To make kvm work on arm64, the default x86_64 kvm64 cpu type needed to be changed. Signed-off-by: Mahe Tardy <[email protected]>
Previously, all images were by default bootable. This adds an option in the image conf to specify if the output image should be bootable or not. It keeps retro-compatibility with previous configurations by treating omited option as true using a boolean pointer. Signed-off-by: Mahe Tardy <[email protected]>
Signed-off-by: Mahe Tardy <[email protected]>
mtardy
force-pushed
the
pr/mtardy/arm64-support
branch
3 times, most recently
from
3f80da9 to
9590475
Compare
mtardy
force-pushed
the
pr/mtardy/arm64-support
branch
from
9590475 to
a564dda
Compare
mtardy
changed the title
For example, on amd64, if the 'gcc-aarch64-linux-gnu' package is installed, LVH can cross compile an arm64 kernel on amd64. On arm64, if the 'gcc-x86-64-linux-gnu' package is install, LVH can cross compile an amd64 kernel on arm64. Signed-off-by: Mahe Tardy <[email protected]>
mtardy
force-pushed
the
pr/mtardy/arm64-support
branch
from
a564dda to
7e43e94
Compare
Signed-off-by: Mahe Tardy <[email protected]>
Commit 9e7539f modified our use of the dir-pkg target because it wasn't supported in 4.19. This updates the README along the arch specific target changes. Signed-off-by: Mahe Tardy <[email protected]>
kkourt
approved these changes
Mar 13, 2024
There was a problem hiding this comment.
LGTM, thanks.
minor nit: I would prefered to have the an arch variable (initialized to runtime.GOARCH) passed to the various helper functions rather than using GOARCH everywhere. I think this would made it easier to run an ARM vm in an x86 machine or vice-versa. We can do it in a later PR if needed.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixes #56.
With this update, you can:
You cannot build an arm64 image on amd64 because of libguestfs tools limitations, unfortunately,
mmdebstrapworks perfectly fine with emulation but libguestfs tools rely on Qemu to start the VMs to modify the images and it's not set up for emulation.Also, this introduces a new
bootablefield in the image conf since with this patch. For now, we can only build non-bootable images for arm64 as I haven't taken the time to investigate the bootloader part that we could use (since extlinux used here is x86_64 only). So the default is that images are bootable by default on x86_64 and non-bootable by default on arm64. You can use the new field to be precise.This might not be the ideal setup as I haven't taken the time to look into the kernel config specific for arm64 to we should change. It seems to work ok at least, maybe we are not very optimized but...