-
Notifications
You must be signed in to change notification settings - Fork 45
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
run_td.sh working on one machine but not another #286
Comments
Thank you for reporting us your feedback! The internal ticket has been created: https://warthogs.atlassian.net/browse/PEK-1494.
|
Hello @fwoodruff-ab - The TDX early preview isn't ready to support Xeon 6731E yet. This product is codenamed Sierra Forest, which is Xeon 6 with E-Cores. We only have support for Xeon 6 with P-Cores (codenamed: Granite Rapids) for time being. |
@bktan8 And are there any plans from Intel to support TDX on Sierra Forest / 6731E family? |
@pprincipeza We are working on delivering the support for Sierra Forest on 24.10, it should be released soon |
@hector-cao Thanks for the heads-up! Do you believe this could ever be backported to the TDX stack for 24.04? I believe customers will most likely adopt TDX in an LTS stack instead of a non-LTS (like 24.10). |
I previously followed the instructions on a Xeon 8570 machine. I am now on a Xeon 6731E machine and
run_td.sh
is no longer working. I have moved from a machine obtained for testing purposes through a private source, to a machine obtained from a small bare metal cloud provider.I SSHed into the Xeon 8570 machine with a Ubuntu 24.04 operating system already installed. I followed the instructions in
README.md
. I had direct remote access to the BIOS via a console and it looked just like what is listed in the instructions in step 4.3. I used an image generated using step 5.1 on a different machine and copied (scp
) this across. I ranrun_td.sh
without issue.I then obtained a Xeon 6731E machine through a cloud provider. I ran step 4.1 using
do-release-upgrade
, step 4.2 as stated, and step 4.3 I had to ask the cloud provider to action, since the BIOS was password protected.Running step 6 I get:
Searching for the error online I found this and not much else.
How do I run a TDX guest on this Intel TDX machine?
System report
Git ref
Operating system details
Kernel version
TDX kernel logs
TDX CPU instruction support
Model specific registers (MSRs)
CPU details
QEMU package details
Libvirt package details
OVMF package details
sgx-dcap-pccs package details
tdx-qgs package details
sgx-ra-service package details
sgx-pck-id-retrieval-tool package details
QGSD service status
PCCS service status
MPA registration logs (last 30 lines)
The text was updated successfully, but these errors were encountered: