-
Notifications
You must be signed in to change notification settings - Fork 2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Error when booting with qemu on bare metal TDX #25
Comments
Thanks for raising this issue! No, we haven't experienced this. I can at least say for the v3 images they work in TDX using qemu. Also depends on the MACHINE target your using, but the general tdx machine or tdx-qemu should both work. Output of lscpu on our host machine for comparison
|
I checked the kernel config for v3, while |
Aha, great, thanks for responding. Can you point me to where you found that, or how i would set it? I guess i could try either adding |
You can search for the .config file of the kernel in the build/tmp folder, there aren't that many files with that name, one matches. |
Thanks. I can change the kernel configuration for
in the file I am not able to do I also tried adding: but again the build runs successfully but i can still see |
Looks like just setting that single config doesn't get applied/is blocked by some missing dependency. You can set all required configs via menuconfig and then use the diffconfig functionality (check the docs) to get all required dependencies. |
Im not sure if this is the right place to put this issue, maybe its more relevant to meta-confidential-compute repo, or maybe it is a problem my end.
I can successfully build images made using the instructions in this repo.
When booting on a TDX machine which is set up using the canonical/tdx scripts and run with qemu using their guest-tools/run_td.sh script, the boot does not complete, but hangs with the following output:
`note: cryptomgr_test[152] exited with preempt_count 1` (click to see full output with call trace)
(i added
-serial stdio
to the qemu command so i am able to see console messages when booting)It appears this issue is specifically related to TDX, because if i remove the qemu option
confidential-guest-support=tdx
(a sub-option to-machine
), the image boots successfully. It also boots successfully usingrunqemu
command from within this repo on the same machine (but again, without TDX guest). I am also able to boot the ubuntu TDX images as described in the canonical tutorial and am able to generate TDX quotes etc.I found a similar error reported on the tiny core linux forum where the solution was to remove the
CONFIG_CRYPTO_CRC32C_INTEL
kernel config option. But i cannot see that option being specifically turned on anywhere in these scripts.This happens on both the main branch of this repo, and when using the v3 branch following the instructions in the PR notes (which i understand uses a newer kernel version).
Output of lscpu on the host machine
Has anyone else seen this problem? Thanks.
The text was updated successfully, but these errors were encountered: