Support mounting rootfs from virtio-blk via initrd #81
Conversation
This file contains hidden or 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
jserv
reviewed
Jun 1, 2025
jserv
reviewed
Jun 1, 2025
jserv
reviewed
Jun 1, 2025
shengwen-tw
force-pushed
the
switch_root
branch
2 times, most recently
from
df27770 to
5d4ca98
Compare
Can you refine the testing procedures? I expect to run |
ChinYikMing
reviewed
Jun 3, 2025
|
I've updated |
|
I plan to merge #82 prior to this pull request, so that we can validate Linux v6.12 (another LTS kernel). |
jserv
reviewed
Jun 4, 2025
scripts/build-image.sh
Outdated
Comment on lines
31
to
43
| if [ ! -f buildroot/.config ]; then | ||
| echo "Copying buildroot.config -> buildroot/.config" | ||
| cp -f configs/buildroot.config buildroot/.config | ||
| else | ||
| echo "buildroot/.config already exists, skipping copy" | ||
| fi | ||
|
|
||
| if [ ! -f buildroot/busybox.config ]; then | ||
| echo "Copying busybox.config -> buildroot/busybox.config" | ||
| cp -f configs/busybox.config buildroot/busybox.config | ||
| else | ||
| echo "buildroot/busybox.config already exists, skipping copy" | ||
| fi |
There was a problem hiding this comment.
Create bash function to avoid duplication.
|
Rebase the latest |
shengwen-tw
force-pushed
the
switch_root
branch
2 times, most recently
from
0794981 to
00a1cf7
Compare
Due to the 1 GiB kernel space limit on RV32-Linux, embedding large root filesystems in the kernel image can be impractical for certain testing scenarios. This commit introduces a script to generate a mountable ext4 rootfs image and modifies the init script to support switching the root filesystem to a virtio-blk device. During boot, the init script checks whether /dev/vda contains a valid rootfs. If so, it switches the root to the virtio-blk device. Otherwise, it falls back to the default initramfs.
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.
Overview
Due to the 1 GiB kernel space limit on RV32-Linux, embedding large root filesystems in the kernel image can be impractical for certain testing scenarios.
This commit introduces a script to generate a mountable ext4 rootfs image and modifies the init script to support switching the root filesystem to a virtio-blk device.
During boot, the init script checks whether
/dev/vdacontains a valid rootfs. If so, it switches the root to the virtio-blk device. Otherwise, it falls back to the default initramfs.Testing Procedures
1. Build Linux kernel and rootfs CPIO
2. Generate external rootfs image
3. Launch the simulator
Expected Output
The console output should indicate that the root filesystem was successfully mounted from
/dev/vda:References