Intel TDX Azure instances are segfaulting due to an error in glibc.
The glibc error is fixed with this patch [1]
[TEST CASE]
Test case requires an azure TDX instance.
Testing instructions from [2] being
getconf -a | grep CACHE
showing non-zero entries for the cache values
[REGRESSION POTENTIAL]
Compatibility impact on applications which invoke CPUID directly.
(they might have to be patched in ways similar to glibc). But at least the glibc patch appears to be working.
[IMPACT]
This is a continuation of the lp # 2011421
Intel TDX Azure instances are segfaulting due to an error in glibc.
The glibc error is fixed with this patch [1]
[TEST CASE]
Test case requires an azure TDX instance.
Testing instructions from [2] being
getconf -a | grep CACHE
showing non-zero entries for the cache values
[REGRESSION POTENTIAL]
Compatibility impact on applications which invoke CPUID directly.
(they might have to be patched in ways similar to glibc). But at least the glibc patch appears to be working.
[OTHER]
This will affect Mantic, Jammy, Focal
[0] https:/ /azure. microsoft. com/en- us/blog/ azure-confident ial-computing- on-4th- gen-intel- xeon-scalable- processors- with-intel- tdx/ /sourceware. org/git/ gitweb. cgi?p=glibc. git;h=1493622f4 f9048ffede3fbed b64695efa49d662 a /sourceware. org/bugzilla/ show_bug. cgi?id= 30643#c12
[1] https:/
[2] https:/