Closed yanxue-intel closed 7 months ago
I just tested with the latest source codes and found it works well. @binxing @yanxue-intel
1) Initrd built by myself
2) Image built by Xiaofeng
I can't run make
successfully under samples/quote/ and suspect it is an build environment issue.
Attached the manifest: { "aconSpecVersion": [ 1, 0 ], "layers": [ "sha384/634b27f7651fae2d50b6545ff000a82800aa8bfefff5974edefeddf43d4b3c85b8296c6660ee0999c3a0f4426492b1d9" ], "aliases": {}, "entrypoint": [ "/quote_server" ], "env": [ "PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin" ], "workingDir": "/", "uids": [], "logFDs": [], "writableFS": false, "noRestart": false, "signals": [], "maxInstances": 1, "policy": { "rejectUnaccepted": false } }
@yanxue-intel please put in the kernel versions and their behaviors with regard to this issue, and nail the "best" kernel version.
The kernel version with issues is:6.2.0-rc6-tde-20230130+ QGS can't receive messages from Acond when using this kernel. After replacing kernel with version "6.3.0-rc6-tde-20230418-00119-gdb5e84a614bb", the issue has been fixed. So I think currently best kernel version is: 6.3.0-rc6-tde-20230418-00119-gdb5e84a614bb
Is Acond using TDVMCall or vsock for communicating with QGS?
As I know, Acon uses TDVMCALL, @xiangquanliu please help double check.
Is Acond using TDVMCall or vsock for communicating with QGS?
Currently we're using TCVMCALL.
Default writableFS value is 'false' in sample/quote's manifest, which caused failure of running workload.