public inbox for pve-devel@lists.proxmox.com
 help / color / mirror / Atom feed
From: Anton Iacobaeus <anton.iacobaeus@canarybit.eu>
To: Fiona Ebner <f.ebner@proxmox.com>,
	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: Mon, 13 Oct 2025 16:02:09 +0200	[thread overview]
Message-ID: <8c2d3d17-4664-43fe-b777-885ac92ed0d4@canarybit.eu> (raw)
In-Reply-To: <7fc5b715-23c8-4245-b65c-5760c5958d2f@proxmox.com>

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.

>> Signed-off-by: Philipp Giersfeld <philipp.giersfeld@canarybit.eu>
>> Signed-off-by: Anton Iacobaeus <anton.iacobaeus@canarybit.eu>
> 
> Reviewed-by: Fiona Ebner <f.ebner@proxmox.com>
> 
> Unfortunately, mailman ate the special line endings in the diff below,
> so it's necessary to fix them up locally to be able to build the
> package. Should there be another version of the series, please use
> --transfer-encoding=base64 when sending the message with git.
> 

Thank you for the review! I will clean up some things and make a v3.

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


  reply	other threads:[~2025-10-13 14:02 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] Add support for Intel TDX 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 [this message]
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
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=8c2d3d17-4664-43fe-b777-885ac92ed0d4@canarybit.eu \
    --to=anton.iacobaeus@canarybit.eu \
    --cc=f.ebner@proxmox.com \
    --cc=philipp.giersfeld@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
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal