Skip to content

docs,dev-docs: document firmware upgrades and change of PIID - #2590

Open
sespiros wants to merge 2 commits into
mainfrom
sse/bare-metal-runner-fw-update
Open

docs,dev-docs: document firmware upgrades and change of PIID#2590
sespiros wants to merge 2 commits into
mainfrom
sse/bare-metal-runner-fw-update

Conversation

@sespiros

Copy link
Copy Markdown
Collaborator

No description provided.

The values in dev-docs/e2e/<host>/manifest.json read as one-time setup, but
a firmware update invalidates them. It regenerates the platform's SGX keys,
which changes the PIID and leaves the host unable to produce quotes until
it's registered with Intel again, and swapping the TDX module changes
MrSeam.

Signed-off-by: Spyros Seimenis <sse@edgeless.systems>
Updating platform firmware can regenerate a TDX host's SGX provisioning
keys. The platform then has a new PPID, QE ID and PIID, Intel won't issue
PCK certificates for it until it's registered again, and the host can't
produce quotes at all until then. MrSeam and AllowedPIIDs both go stale.

Nothing in the docs said so, and it isn't obvious from the failure: the
host boots normally, TDX initialises, and only quote generation breaks.
@sespiros
sespiros requested a review from charludo August 17, 2026 14:40
@sespiros sespiros added no changelog PRs not listed in the release notes documentation Improvements for user docs and removed no changelog PRs not listed in the release notes labels Aug 17, 2026
@github-actions

Copy link
Copy Markdown

Do the documentation changes need to be backported?

Changes to /docs/docs won't be visible until the next release.
If you are fixing something in the docs that should be immediately visible, the changes needs to be made to both /docs/docs and /docs/versioned_docs/version-X.Y, where X.Y is the version of the latest minor release.
This can be done in this same PR.

  • Yes, this should be backported to the current version of the docs.
  • No, the PR only contains docs changes relevant for future versions.

@charludo charludo left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

(approved, pending the discussions with Thomas in the wiki)

:::warning

The `PIID` is derived from the platform's SGX provisioning keys.
Updating the platform firmware can regenerate those keys, which changes the `PIID` and requires the platform to be registered with Intel again.

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
Updating the platform firmware can regenerate those keys, which changes the `PIID` and requires the platform to be registered with Intel again.
Updating the platform firmware can regenerate those keys, which changes the `PIID` and requires the platform to be re-registered with Intel.


The `PIID` is derived from the platform's SGX provisioning keys.
Updating the platform firmware can regenerate those keys, which changes the `PIID` and requires the platform to be registered with Intel again.
Until it's registered, Intel doesn't issue PCK certificates for the platform, so it can't produce quotes at all.

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
Until it's registered, Intel doesn't issue PCK certificates for the platform, so it can't produce quotes at all.
Until the re-registration is completed, Intel doesn't issue PCK certificates for the platform, which therefore can't produce quotes at all.

Nit: too many it's :D

@linear-code

linear-code Bot commented Aug 18, 2026

Copy link
Copy Markdown

CON-305

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

documentation Improvements for user docs

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants