Skip to content
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

Feature: allow users to specify kernel modules directory when running with custom kernel #117

Open
brb opened this issue Sep 27, 2023 · 0 comments
Labels
good first issue Good for newcomers help wanted Extra attention is needed

Comments

@brb
Copy link
Member

brb commented Sep 27, 2023

At the time of writing, the LVH runner allows users to use a custom kernel path (to bzImage) via --kernel cmdline param. Unfortunately, it doesn't allow users to specify kernel modules directory. The pre-installed kmods in a VM image usually cannot be used with the custom kernel.

One workaround is to mount linux dir via --host-mount, and then from the VM cd /host/linux && make module_install. However, having the explicit kmods param would make the LVH runner easier to use.

@brb brb added good first issue Good for newcomers help wanted Extra attention is needed labels Sep 27, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
good first issue Good for newcomers help wanted Extra attention is needed
Projects
Status: No status
Development

No branches or pull requests

1 participant