From: Fiona Ebner <f.ebner@proxmox.com>
To: Proxmox VE development discussion <pve-devel@lists.proxmox.com>,
Anton Iacobaeus <anton.iacobaeus@canarybit.eu>
Subject: Re: [pve-devel] [PATCH qemu-server v2 3/3] Add support for Intel TDX
Date: Mon, 13 Oct 2025 11:30:45 +0200 [thread overview]
Message-ID: <9f98346e-9a41-4060-ac06-84cc355cf4ca@proxmox.com> (raw)
In-Reply-To: <f09d7c47-2a31-4762-8cfb-edbad89f2341@proxmox.com>
Am 08.10.25 um 12:21 PM schrieb Fiona Ebner:
> Am 04.10.25 um 3:23 PM schrieb Anton Iacobaeus:
>> From: Philipp Giersfeld <philipp.giersfeld@canarybit.eu>
>>
>> This commit adds support for setting up an Intel TDX VM. A Intel TDX VM
>> can be setup similar to AMD SEV but uses a different firmware image.
>>
>> Signed-off-by: Philipp Giersfeld <philipp.giersfeld@canarybit.eu>
>> Signed-off-by: Anton Iacobaeus <anton.iacobaeus@canarybit.eu>
>
> Apart from a few nits, see below:
> Reviewed-by: Fiona Ebner <f.ebner@proxmox.com>
>> @@ -3965,6 +3978,10 @@ sub config_to_command {
>> if ($conf->{'amd-sev'}) {
>> push @$devices, '-object', get_amd_sev_object($conf->{'amd-sev'}, $conf->{bios});
>> push @$machineFlags, 'confidential-guest-support=sev0';
>> + } elsif ($conf->{'intel-tdx'}) {
>> + push @$devices, '-object', get_intel_tdx_object($conf->{'intel-tdx'}, $conf->{bios});
>> + push @$machineFlags, 'confidential-guest-support=tdx0';
>> + push @$machineFlags, 'kernel_irqchip=split';
One more thing I noticed/remembered:
Don't we also need something like
-device vhost-vsock-pci,guest-cid=3
for communication between QGS and TD VM like described in the docs:
https://cc-enabling.trustedservices.intel.com/intel-tdx-enabling-guide/05/host_os_setup/#setup-communication-path-between-qgs-and-td
?
>
> Nit: would be nice to have a comment describing the rationale behind the
> kernel_irqchip option and/or a sentence in the commit message.
>
>> }
>>
>> PVE::QemuServer::Virtiofs::config($conf, $vmid, $devices);
_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
next prev parent reply other threads:[~2025-10-13 9:31 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-01 15:11 [pve-devel] [PATCH edk2-firmware/manager/qemu-server v2 0/7] " Anton Iacobaeus
2025-10-01 15:11 ` [pve-devel] [PATCH edk2-firmware v2 1/3] Change name of SEV-related OVMF files Anton Iacobaeus
2025-10-07 15:24 ` Fiona Ebner
2025-10-01 15:11 ` [pve-devel] [PATCH edk2-firmware v2 2/3] Add firmware target for TDFV Anton Iacobaeus
2025-10-07 15:24 ` Fiona Ebner
2025-10-13 14:02 ` Anton Iacobaeus
2025-10-01 15:11 ` [pve-devel] [PATCH edk2-firmware v2 3/3] Add SCSI in NCCFV for TD guest Anton Iacobaeus
2025-10-07 15:24 ` Fiona Ebner
2025-10-13 14:02 ` Anton Iacobaeus
2025-10-14 7:50 ` Fiona Ebner
2025-10-01 15:11 ` [pve-devel] [PATCH manager v2 1/1] Add support for Intel TDX Anton Iacobaeus
2025-10-01 15:11 ` [pve-devel] [PATCH qemu-server v2 1/3] Adapt AMD SEV code for compatibility with other platforms Anton Iacobaeus
2025-10-07 15:24 ` Fiona Ebner
2025-10-01 15:11 ` [pve-devel] [PATCH qemu-server v2 2/3] Add check for TDX support Anton Iacobaeus
2025-10-08 10:06 ` Fiona Ebner
2025-10-01 15:11 ` [pve-devel] [PATCH qemu-server v2 3/3] Add support for Intel TDX Anton Iacobaeus
2025-10-08 10:21 ` Fiona Ebner
2025-10-13 9:30 ` Fiona Ebner [this message]
2025-10-13 14:25 ` Anton Iacobaeus
2025-10-14 7:50 ` Fiona Ebner
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=9f98346e-9a41-4060-ac06-84cc355cf4ca@proxmox.com \
--to=f.ebner@proxmox.com \
--cc=anton.iacobaeus@canarybit.eu \
--cc=pve-devel@lists.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox