neonvm-kernel: Switch to version 6.6.63 #1170
Conversation
There was a problem hiding this comment.
Seems fair enough, but I'll leave it to Misha to give a more proper review.
One question, one request.
Question: What's the thinking between upgrading to latest 6.1.x vs 6.6.x ?
Request: Due to changes in upgrade instructions — if you haven't already, could you double-check that going through the upgrade steps for the current version produces an empty diff? (and if not, let's separate that into its own PR?)
I ask in part because there may be some changes due to #1159, and if there's a bunch it'd be good to isolate those out so they can be ignored.
| ``` | ||
|
|
||
| Afterwards, it's probably also good to do a search-and-replace repo-wide to update all places that | ||
| mention the old kernel version. | ||
|
|
||
| ### On arm64 (aarch64 ARM) | ||
|
|
||
| Note: you need to run this on ARM64 machine. It worked on my MacBook M2, but didn't on x64. |
There was a problem hiding this comment.
That's weird... @mikhail-sakhnov any ideas what's needed to avoid this?
(broader context: I think it's risky to have kernel upgrade steps that depend on dev access to particular hardware, because it makes updating quite complex).
Not much, just noticed that on kernel bugzilla it was a common suggestion to switch major version in similar cases:
|
fair enough, makes sense! |
I've splitted this into #1172. There is some diff for arm config, let's go there for discussion. |
|
There is a new kernel version, so I opened a new PR to upgrade to 6.6.64 |
This commit updates the kernel and switches from 6.1.x to 6.6.x LTS branch.
As of 2024-12-06, www.kernel.org says this is the most recent version of the 6.6.x LTS branch.
Basically just followed the instructions in neonvm-kernel/README.md, copying in linux-config-ARCH-6.6.63 as .config, and .config back to /host once done with menuconfig. Fixed the instruction for amd64/arm64 along the way.
Trying this as a possible solution to https://github.com/neondatabase/cloud/issues/20195