I can confirm I’m running the 16k kernel but it seems that 6.7.3-200 isn’t available:
~> dnf updateinfo list
Last metadata expiration check: 0:07:21 ago on Thu 22 Feb 2024 12:29:28 PM -03.
allow_vendor_change is disabled. This option is currently not supported for downgrade and distro-sync commands
FEDORA-2024-2116a8468b Unknown/Sec. kernel-headers-6.7.3-200.fc39.aarch64
~> uname -r
6.6.3-413.asahi.fc39.aarch64+16k
~> arch
aarch64
The kernel version is different inside a VM:
↪ uname -r
6.7.5-200.fc39.aarch64
root at elevatus in ~
↪
Here are the questions:
do I need to stick with the kernel-16k?
since host and guest are sharing the same architecture, what would be the best way to keep the host up-to-date?
aside from kernel-16k, the unique difference is that I performed a distro upgrade in the VM (fedora 38 → fedora 39), but would that be enough to justify the difference on packages?
is there anything else I need to check on yum/dnf to make sure I won’t be preventing any packages from receiving updates?
Yes you need a special kernel, dont do something crazy. The regular Fedora kernel is quicker with updates, thats okay.
No idea what you are doing. You use Asahi and have a qemu VM also with Fedora Asahi? Does that also use aarch64? I am not sure if x86_64 VMs work, which would explain the difference.
Is your Asahi still on 38, it asahi even that old? cat /etc/fedora-release You should upgrade, follow official instructions
Just do sudo dnf update -y and see for error messages. Yum is not used anymore normally, dont even know if it is still installed.
alright, I didn’t remember if I installed it or it came with the distro and the logs don’t lie here (hence I messed it up at some point)
~> dnf history list kernel-16k
allow_vendor_change is disabled. This option is currently not supported for downgrade and distro-sync commands
ID | Command line | Date and time | Action(s) | Altered
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
113 | reinstall kernel-16k* | 2024-02-01 17:55 | R | 30 EE
112 | reinstall kernel-16k-6.6.3-413.asahi.fc39.aarch64 | 2024-02-01 17:53 | R | 2
111 | reinstall kernel-16k-6.6.3-413.asahi.fc39.aarch64 | 2024-02-01 17:52 | R | 2
110 | upgrade --refresh | 2024-02-01 17:52 | I, U | 10
109 | remove kernel-16k-6.6.3-413.asahi.fc39.aarch64 | 2024-02-01 13:21 | C, E | 2 <
107 | update | 2024-02-01 12:38 | C, E, I, U | 12 ><
42 | update | 2023-12-19 17:43 | C, E, I, U | 13 ><
38 | update | 2023-12-18 12:13 | C, E, I, U | 13 ><
35 | update | 2023-12-17 14:49 | C, E, I, U | 16 ><
11 | update | 2023-12-15 10:23 | Install | 5 ><
5 | update | 2023-12-14 17:17 | I, U | 255 ><
2 | --config /kiwi_oin9ebar -y --releasever=39 --exclude=@dial-up --exclude=@guest-desktop-agents --exclude=dracut-config-rescue --exclude=generic-logos* --exclude=generic-release | 2023-11-26 13:05 | Install | 1781 >E
~>
2 & 3. I have installed Fedora 39 Asahi on the latop, and the VM was installed with Fedora 38 (the one available on virt-builder for aarch64), which I performed a distro upgrade; I’m pretty sure x86_64 won’t work, and the two main points are the difference at least on kernel version numbers, as it looks like the VM has a more up-to-date kernel than the host itself (6.7.5 vs 6.6.3), and why dnf updateinfo list reports kernel headers for 6.7.3 that cannot be installed
4. thank you so much, I need to forget about yum
I think the newest kernel headers cannot be installed due to conflicts with running 16k kernel, and now it leads me to another question: how can I ensure the running 16k kernel has all patches?
The other point is: if both host and VMs are aarch64, then why do I have different kernel versions? The Asahi remix installed on host, opposed to Fedora server on VM, would be enough to justify this difference?