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

simplify using custom kernel [module] installation by installing PV Grub related packages by default #1738

Closed
adrelanos opened this Issue Feb 10, 2016 · 2 comments

Comments

Projects
None yet
2 participants
@adrelanos
Member

adrelanos commented Feb 10, 2016

The current documentation on custom kernel usage is quite long.
https://www.qubes-os.org/doc/managing-vm-kernel/

It could be made shorter and simpler by installing the related PV Grub (#1354) packages by default inside the templates. Installing custom kernels and custom kernel modules is somewhat a basic feature that is usually simple. Requiring to install extra packages to make that work first is a unpleasant surprise. By installing these packages by default, the required extra template size is justified and we are adhering the principle of least surprise better, thereby improving usability.

packages to be installed by default...

dom 0

  • qubes-kernel-vm-support
  • grub2-xen

fedora:

  • qubes-kernel-vm-support
  • grub2-tools

debian:

  • qubes-kernel-vm-support
  • grub2-common

This can wait until the PV Grub approach is considered stable. Or at least until these packages flow into Qubes stable repositories. Or at least the likelihood the the mere installation of these packages will not break Qubes for users who do not require this.

Long term this feature would be useful for Qubes-Whonix also. Would simplify installation instructions for grsecurity kernels and usage of grsecurity-installer.

@marmarek

This comment has been minimized.

Show comment
Hide comment
@marmarek

marmarek Feb 11, 2016

Member

Generally moving to PV Grub by default would make some things easier. For example system installed in the template will be much closer to baremetal installation, so all the kernel-related upstream instructions will apply.
I think some (not so strict, but still) requirement is getting rid of / upstreaming u2mfn module - the only custom module needed in VM. Otherwise every installation would require compiling that module for whatever kernel is used there (dkms do that automatically, but still it's some inconvenience). See #1654 for details.

Member

marmarek commented Feb 11, 2016

Generally moving to PV Grub by default would make some things easier. For example system installed in the template will be much closer to baremetal installation, so all the kernel-related upstream instructions will apply.
I think some (not so strict, but still) requirement is getting rid of / upstreaming u2mfn module - the only custom module needed in VM. Otherwise every installation would require compiling that module for whatever kernel is used there (dkms do that automatically, but still it's some inconvenience). See #1654 for details.

@marmarek marmarek added this to the Release 4.0 milestone Feb 11, 2016

andrewdavidwong added a commit that referenced this issue May 31, 2016

@marmarek

This comment has been minimized.

Show comment
Hide comment
@marmarek

marmarek Jul 13, 2017

Member

Templates for Qubes 4.0 have grub installed by default.

Member

marmarek commented Jul 13, 2017

Templates for Qubes 4.0 have grub installed by default.

@marmarek marmarek closed this Jul 13, 2017

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment