run kernel in chroot #34
Merged
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
chantra
force-pushed
the
alternative_chroot
branch
2 times, most recently
from
a5eb528
to
205d78e
Compare
chantra
force-pushed
the
alternative_chroot
branch
from
205d78e
to
11233bc
Compare
Merged
danobi
approved these changes
Nov 1, 2023
Insteads of mounting the local FS'root, we can do the same but in a chroot.
The main benefit would be to be able to run a kernel/artifacts in a guest FS
which may be different then the host FS. For instance when collecting CI artifacts
and trying to reproduce locally.
CI may run in say Ubuntu 22.04 , while my host may be Fedora 38.
This also opens up for a next diff where we can run againdt a foreign architecture
provided that the chrrot is for that arch.
```
$ cat /etc/debian_version && RUST_LOG=debug cargo run -- -k $KERNEL_REPO/arch/x86_64/boot/bzImage -r debian 'cat /etc/debian_version'
trixie/sid
Compiling vmtest v0.8.3 (/home/chantra/devel/danobi-vmtest)
Finished dev [unoptimized + debuginfo] target(s) in 8.11s
Running `target/debug/vmtest -k /home/chantra/devel/bpf-next//arch/x86_64/boot/bzImage -r debian 'cat /etc/debian_version'`
=> bzImage
===> Booting
===> Setting up VM
===> Running command
11.5
bash: line 1: cd: /home/chantra/devel/danobi-vmtest: No such file or directory
```
Also tested that it would work when configured in `vmtest.toml`
```
$ RUST_LOG=debug cargo run --
Compiling vmtest v0.8.3 (/home/chantra/devel/danobi-vmtest)
Finished dev [unoptimized + debuginfo] target(s) in 2.50s
Running `target/debug/vmtest`
=> Alt RootFS
===> Booting
===> Setting up VM
===> Running command
11.5
bash: line 1: cd: /home/chantra: No such file or directory
=> Standard RootFS
===> Booting
===> Setting up VM
===> Running command
trixie/sid
$ cat vmtest.toml
[[target]]
name = "Alt RootFS"
kernel = "/home/chantra/devel/bpf-next//arch/x86_64/boot/bzImage"
command = "cat /etc/debian_version"
rootfs = "debian"
[[target]]
name = "Standard RootFS"
kernel = "/home/chantra/devel/bpf-next//arch/x86_64/boot/bzImage"
command = "cat /etc/debian_version"
```
Signed-off-by: Manu Bretelle <[email protected]>
Signed-off-by: Manu Bretelle <[email protected]>
…path) If this is not the case, the guest is not going to be able to find the init file we pass as a parameter of `init=`. We better error out than having a VM that fails to boot properly. Signed-off-by: Manu Bretelle <[email protected]>
chantra
force-pushed
the
alternative_chroot
branch
from
11233bc
to
472cce8
Compare
I added them as separate commits. |
|
the failed test seems to be environmental more than anything. |
|
I wonder if GH changed something today. The EPERM error looks kinda similar to the large runner thing you have to do: https://github.com/danobi/vmtest-action/blob/fed44e099e1e7b79251780393453929ab20d107e/vmtest.js#L48-L62 |
yeah, they may start presenting /dev/kvm and because no permission is checked it tries to enable kvm while it does not have access. |
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.
Insteads of mounting the local FS'root, we can do the same but in a chroot. The main benefit would be to be able to run a kernel/artifacts in a guest FS which may be different then the host FS. For instance when collecting CI artifacts and trying to reproduce locally.
CI may run in say Ubuntu 22.04 , while my host may be Fedora 38. This also opens up for a next diff where we can run againdt a foreign architecture provided that the chrrot is for that arch.
Also tested that it would work when configured in
vmtest.toml