You are not logged in.
Maybe it is possible to keep hyper-v enabled, but change some settings for libgrypt not to use some hardware features with /etc/gcrypt/hwf.deny
| alias CUTF='LANG=en_XX.UTF-8@POSIX ' |
Offline
I ran into this same problem running inside hardware-accelerated-QEMU on macOS (-accel hvf), where I was previously having trouble with rdtsc (and had to specify "-cpu host,-rdtscp" to get the system to boot at all).
I noticed that dmesg contained a complaint about the clocksource being unstable and needing to switch to hpet. Rebooting with clocksource=hpet fixed it and I'm able to verify signatures now. I wonder if that will work for Hyper-V too.
Offline
I am currently facing the same issue installing on Virtualbox 6.1.12 with Hyper-V enabled. I cannot disable Hyper-V and downgrade virtualbox because I am currently using WSL2, which requires support for Hyper-V.
I have tried every other solution for invalid pgp keys I could find but none of them work. I was able to get into a usable arch linux installation by disabling pgp checking, but this can not be a permanent solution and the issue is still very irritating.
Offline
I have the exact same problem. Windows 10 Pro and Virtual box. Is there any fix for it yet?
Offline