Re: [pve-devel] [PATCH edk2-firmware v2 3/3] Add SCSI in NCCFV for TD guest

From: Fiona Ebner <f.ebner@proxmox.com>
To: Anton Iacobaeus <anton.iacobaeus@canarybit.eu>,
	Proxmox VE development discussion <pve-devel@lists.proxmox.com>
Cc: Philipp Giersfeld <philipp.giersfeld@canarybit.eu>
Subject: Re: [pve-devel] [PATCH edk2-firmware v2 3/3] Add SCSI in NCCFV for TD guest
Date: Tue, 14 Oct 2025 09:50:51 +0200	[thread overview]
Message-ID: <20afb5f5-caba-4e7b-ae98-be92498b199b@proxmox.com> (raw)
In-Reply-To: <8c2d3d17-4664-43fe-b777-885ac92ed0d4@canarybit.eu>

Am 13.10.25 um 4:01 PM schrieb Anton Iacobaeus:
> On 10/7/25 17:24, Fiona Ebner wrote:
>> Am 04.10.25 um 3:23 PM schrieb Anton Iacobaeus:
>>> From: Philipp Giersfeld <philipp.giersfeld@canarybit.eu>
>>>
>>> The FV in `IntelTdx/IntelTdxX64.fdf` was split into two FVs, one for a
>>> TD guest and one for non-cc guest. The SCSI driver was moved to the
>>> non-cc NCCFV. In order for PVE to use an image with SCSI include the
>>> SCSI driver in the FV for TD guest.
>>
>> Did you already ask upstream whether they would be willing to include
>> SCSI for the TD guest or is there no interest? Some of it is already
>> guarded via _ENABLE flags anyways. I'm fine with going with this, but
>> it's always nice to have no more diff than necessary to upstream.
>>
> 
> We asked upstream and they said that there is no architecture issue with
> the SCSI driver, but it is a matter of validation. As of now there are
> no plans to include it, but an official request for it could be made.
> The process will likely be lengthy however and they also mentioned that
> including the driver manually is a good option.

Good to know! The patch is rather straight-forward, so let's just go
with including it manually.

_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel