On 04/19/2017 05:22 PM, Marek Marczykowski-Górecki wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA256 > > On Wed, Apr 19, 2017 at 03:20:59PM -0600, Reg Tiangha wrote: >> OK, I may have spoken too soon about 4.9 not working on PVGRUB VMs. In >> my case, it really was dkms not compiling the u2mfn module properly, and >> that's why I wasn't getting the green light. My post mortem is here: >> >> https://github.com/QubesOS/qubes-issues/issues/2762 >> >> So I go back to my original opinion that there's no technical reason >> that Qubes couldn't run a 4.9 kernel in dom0 or in VMs. >> >> However, I do think it should be an opt-in thing that users can do with >> a meta-package that can help manage the upgrade (similar to how Ubuntu >> users can choose to opt into newer kernels in LTS releases by explicitly >> installing an Hardware Enablement package). >> >> I really do think that Qubes needs to do it by metapackage because the >> version of u2mfn that ships with the original R3.2 iso does *not* >> support kernels higher than 4.8. And in order for things to work >> correctly, u2mfn 3.2.4 must be installed first so that dkms doesn't fail >> to compile that module when the kernel is upgraded. > This particular thing is not a problem for having kernel 4.9 in Qubes > repository by default, because it already contains u2mfn module in it - > you don't need to compile anything when installing it. > Are there any other reasons why this should be opt-in? I'm asking > because currently we don't have a mechanism for doing it. Only an > opt-out (you can change kernel version in VM properties, and also choose > different default option for dom0 kernel in bootloader settings). So, if > new kernel is for example incompatible with your hardware, you always > have option to rollback. And I think (until convinced otherwise) > inventing/implementing opt-in mechanism for this isn't justified. > > -----END PGP SIGNATURE----- > Well, if it's all bundled in, then I guess that's fine. My biggest concern was ensuring that the u2mfn module was compiled and included since that's the main pain point I've encountered in my adventures with the kernel stuff. But if the package scripts do that at build time and not at install time in dom0, then I don't foresee any issues.
So yeah, if the upgrade is smooth then I see no reason for it to be opt-in either and it could probably be safely pushed out. -- You received this message because you are subscribed to the Google Groups "qubes-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-devel/od8ss0%24j60%241%40blaine.gmane.org. For more options, visit https://groups.google.com/d/optout.
