From: Lorne Guse via pve-devel <pve-devel@lists.proxmox.com>
To: Proxmox VE development discussion <pve-devel@lists.proxmox.com>,
"m.carrara@proxmox.com" <m.carrara@proxmox.com>
Cc: Lorne Guse <boomshankerx@hotmail.com>
Subject: [pve-devel] Unable to initialize TPM storage over iSCSI - TrueNAS over iSCSI
Date: Thu, 25 Sep 2025 03:36:57 +0000 [thread overview]
Message-ID: <mailman.383.1758771460.390.pve-devel@lists.proxmox.com> (raw)
[-- Attachment #1: Type: message/rfc822, Size: 10390 bytes --]
From: Lorne Guse <boomshankerx@hotmail.com>
To: Proxmox VE development discussion <pve-devel@lists.proxmox.com>, "m.carrara@proxmox.com" <m.carrara@proxmox.com>
Subject: Unable to initialize TPM storage over iSCSI - TrueNAS over iSCSI
Date: Thu, 25 Sep 2025 03:36:57 +0000
Message-ID: <DM6PR17MB34666C79F062A17D69C5CCC5D01FA@DM6PR17MB3466.namprd17.prod.outlook.com>
When I try to start a windows VM with q35 / OVMF (UEFI) and the TPM and EFI disks configured as iSCSI LUN on TrueNAS I'm getting this error:
TrueNAS [INFO] : Connected
TrueNAS [INFO] : Authenticated
/bin/swtpm exit with status 256:
TASK ERROR: start failed: command 'swtpm_setup --tpmstate file://iscsi://10.11.11.1/iqn.2005-01.com.techgsolutions:proxmox/16 --createek --create-ek-cert --create-platform-cert --lock-nvram --config /etc/swtpm_setup.conf --runas 0 --not-overwrite --tpm2 --ecc' failed: exit code 1
Does this mean that TPM cannot be stored on an iSCSI LUN?
--
Lorne Guse
[-- Attachment #2: Type: text/plain, Size: 160 bytes --]
_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
next reply other threads:[~2025-09-25 3:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-25 3:36 Lorne Guse via pve-devel [this message]
2025-09-25 9:06 ` Fabian Grünbichler
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=mailman.383.1758771460.390.pve-devel@lists.proxmox.com \
--to=pve-devel@lists.proxmox.com \
--cc=boomshankerx@hotmail.com \
--cc=m.carrara@proxmox.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.