Remove dummy kernel files
talex5 opened this issue · 10 comments
The mirage-firewall distribution includes dummy modules.img
and initramfs
files. These were needed on Qubes 3 for it to accept something as a kernel.
On Qubes 4 (according to https://www.qubes-os.org/doc/managing-vm-kernel/):
All the files besides vmlinuz are optional.
We should remove these dummy files from the build and installation instructions.
As of today on Qubes R4.0 with all updates dom0 still requires the dummy initramfs to start a mirage qube, but modules.img is not required.
Opened question of whether this is a bug or a docs issue over at qubes-issues: QubesOS/qubes-issues#5516
This is partially blocked until Qubes R4.1. Until that is released initramfs
is still required.
Since Qubes 4.0 is end of life now, IMHO it would be good to remove the initramfs file. This also means that our packaging and install instructions can be much simpler (we'll only distribute a single binary, and no need for tar
).
Does this make sense @palainp?
This should be right according to the documentation, but I was unable to boot without it some times algo :/
This is still the case, I have the following:
$ qvm-start mirage-fw
Missing file: /var/lib/qubes/vm-kernels/mirage-fw/initramfs
The existence of initramfs is checked in https://github.com/QubesOS/qubes-core-admin/blob/c177aacbe1afc35034826ef538c0e49ed40b6bc7/qubes/storage/kernels.py#L140
See: QubesOS/qubes-issues#5516
QubesOS/qubes-issues#5516 has been resolved now. This will works with the next Qubes update, and we can remove that dummy file for the next release :)
With dom0 updated we can remove initramfs (QubesOS/qubes-core-admin#586).
The PR in documentation is pending: QubesOS/qubes-doc#1402
We can release only vmlinuz
and a hashsum file now :)