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

[Boot]: Support for initrd_path #208

Closed
andreeaflorescu opened this issue Apr 3, 2018 · 7 comments · Fixed by #1246
Closed

[Boot]: Support for initrd_path #208

andreeaflorescu opened this issue Apr 3, 2018 · 7 comments · Fixed by #1246
Labels
Roadmap: Tracked Items tracked on the roadmap project.

Comments

@andreeaflorescu
Copy link
Member

andreeaflorescu commented Apr 3, 2018

With the initial API when specifying a kernel path, you could also specify the path of the initrd file.
For now this feature is not mandatory.
Acceptance Criteria: Decide if this feature is needed for other use cases.

@andreeaflorescu andreeaflorescu added this to the Customer 2 Production milestone Jun 7, 2018
@andreeaflorescu
Copy link
Member Author

andreeaflorescu commented Jun 14, 2018

There is a topic in our FAQ related to this issue. Before closing it, please update the file.

@andreeaflorescu andreeaflorescu modified the milestones: Customer 2 Production, v1.0 Jun 20, 2018
@andreeaflorescu
Copy link
Member Author

The support is added in PR #428

@raduweiss raduweiss removed this from the v1.0 milestone Nov 20, 2018
@andreeaflorescu andreeaflorescu added the Priority: Low Indicates that an issue or pull request should be resolved behind issues or pull requests labelled ` label Nov 22, 2018
@rgooch
Copy link

rgooch commented Jan 9, 2019

I would like to see this feature added. It would allow replacing QEMU with Firecracker for a significant fraction of VMs.

@cpaelzer
Copy link

Yeah just like @rgooch I'd think for a more direct conversion of some qemu based workloads having initrd support would be great.

@tv42
Copy link

tv42 commented Jan 30, 2019

I feel like this is worth mentioning: people often want keep their initramfs separate from the kernel image to keep their lawyers happy.

This has the memory efficiency advantages of initramfs (no ramdisk block device) but the separate packaging of initrd (which is nice if you have non-GPL code you'd like to run from initramfs, without conflating it with the GPL licensed Linux kernel binary).

https://www.kernel.org/doc/Documentation/filesystems/ramfs-rootfs-initramfs.txt

Then again, given that you'll likely need a special kernel build for these microVMs anyway (no SATA disk etc), I'm not sure one would have such a pressing need for an initramfs. They're usually used just to load the relevant kernel modules to be able to continue the boot, but in these use cases you should be able to build all that in.

I've ran plenty of VMs that only had an initramfs and no block storage at all, and in that scenario the license separation makes a lot of sense.

@tv42
Copy link

tv42 commented Jan 30, 2019

The FAQ has a typo: "You can track issue #228 for news on this topic." while the link leads to here, issue 208.

@luxas
Copy link

luxas commented Jun 4, 2019

I think this would make a lot of sense, in order to be able to boot e.g. the stock Ubuntu/CentOS/Debian kernels, that all set CONFIG_VIRTIO_BLK=m and CONFIG_VIRTIO_NET=m. Hope to see this in the roadmap too #1104

@raduweiss raduweiss added this to Contributions Welcome in [WIP] Roadmap Jul 15, 2019
@raduweiss raduweiss changed the title Discussion about adding support for initrd_path Add Support for initrd_path Jul 15, 2019
@raduweiss raduweiss added Roadmap: Tracked Items tracked on the roadmap project. and removed Roadmap: New Request labels Jul 15, 2019
@andreeaflorescu andreeaflorescu moved this from Contributions Welcome to In Development in [WIP] Roadmap Nov 19, 2019
@raduweiss raduweiss moved this from In Development to Preview in [WIP] Roadmap Feb 20, 2020
@raduweiss raduweiss moved this from Preview to Shipped in [WIP] Roadmap Feb 20, 2020
@raduweiss raduweiss changed the title Add Support for initrd_path [Boot]: Support for initrd_path Sep 18, 2020
@raduweiss raduweiss changed the title [Boot]: Support for initrd_path [Boot]: Support for initrd_path Sep 18, 2020
@raduweiss raduweiss removed the Priority: Low Indicates that an issue or pull request should be resolved behind issues or pull requests labelled ` label Sep 20, 2020
@JonathanWoollett-Light JonathanWoollett-Light removed this from Shipped in [WIP] Roadmap Dec 11, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Roadmap: Tracked Items tracked on the roadmap project.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

7 participants