You are not logged in.
I may have missed this before but I did a system update, rebooted and this was this first line of the boot
Jul 04 17:49:15 archlinux kernel: virt/tdx: TDX not supported by the host platformDo I need to worry? Does it need something to make it happy?
Full log: https://pastewala.com/FiIqH4ZS
Last edited by SimonJ (2026-07-04 19:38:09)
Rlu: 222126
Offline
A quick search suggests that this is related to Intel Trust Domain Extensions, which appears to be a feature exclusive to Intel CPUs. Corroborating this, I'm seeing this after upgrading to linux 7.1.2.arch3-1 on a PC with an AMD chip.
Not sure why this would present as an error in the journal, however; frankly even a warning-level message feels like overkill
Offline
Hi!
You probably just updated from linux-zen 7.0.14 to 7.1.2. Now TDX is evaluated automatically on every single boot via subsys_initcall(tdx_enable) (https://github.com/torvalds/linux/commi … 6b111dd2c5).
Most of consumer CPUs do not support this enterprise server feature, so your system is fine, but it clutters the logs. Upstream developers have already pointed out that this is annoying on consumer machines, and a patch is on the way (https://patchew.org/linux/2026070204320 … ernel.org/)
For now, you can just ignore it.
Last edited by twig (2026-07-04 16:55:04)
Offline
Hi!
You probably just updated from linux-zen 7.0.14 to 7.1.2. Now TDX is evaluated automatically on every single boot via subsys_initcall(tdx_enable) (https://github.com/torvalds/linux/commi … 6b111dd2c5).
Most of consumer CPUs do not support this enterprise server feature, so your system is fine, but it clutters the logs. Upstream developers have already pointed out that this is annoying on consumer machines, and a patch is on the way (https://patchew.org/linux/2026070204320 … ernel.org/)
For now, you can just ignore it.
Yes I did exactly that update, thank you.
Rlu: 222126
Offline
Happens also with stock linux kernel on my ryzen system.
Thanks for the info, twig.
Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.
clean chroot building not flexible enough ?
Try clean chroot manager by graysky
Offline
To me it doesn't make any sense to see this warning, My rig is full AMD, the kernel shouldn't even bother to load any intel code.
Offline
To me it doesn't make any sense to see this warning, My rig is full AMD, the kernel shouldn't even bother to load any intel code.
I see that warning on Intel platforms as well.
This trend becomes annoying. If something is not supported but not required for normal function, it shouldn't be a warning. Debug log level at most.
On one of machines I saw the error "kvm_amd: CPU N isn't AMD or Hygon". Yes, I know that my CPU isn't AMD or Hygon, why this is an error?. Had to suppress it with "initcall_blacklist=svm_init".
Last edited by dimich (2026-07-14 11:19:56)
Online