You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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 VMcd /host/linux && make module_install
. However, having the explicit kmods param would make the LVH runner easier to use.The text was updated successfully, but these errors were encountered: