From: Gerd Hoffmann <kraxel@redhat.com>
To: Claudio Fontana <cfontana@suse.de>
Cc: "Philippe Mathieu-Daudé" <f4bug@amsat.org>,
"Jason Wang" <jasowang@redhat.com>,
"Richard Henderson" <richard.henderson@linaro.org>,
"Paolo Bonzini" <pbonzini@redhat.com>,
"Vasiliy Ulyanov" <vasily.ulyanov@suse.com>,
qemu-devel@nongnu.org
Subject: Re: Adjusting the default ROM option for SEV guests
Date: Thu, 7 Jul 2022 08:53:18 +0200 [thread overview]
Message-ID: <20220707065318.b5kleuqxmxuz6h5w@sirius.home.kraxel.org> (raw)
In-Reply-To: <eaea4711-0290-2087-5abf-f65e6328247d@suse.de>
On Wed, Jul 06, 2022 at 04:57:40PM +0200, Claudio Fontana wrote:
> Hello all
>
> any comment on this one? It seems it would make sense to disable option roms for SEV by default in QEMU, any feedback anyone?
>
> Thanks,
>
> Claudio
>
> On 5/11/22 13:30, Vasily Ulyanov wrote:
> > Hello QEMU devs,
> >
> > Currently to launch an SEV guest there are certain requirements for the VM
> > configuration. One such is that ROM option needs to be disabled for virtio-net
> > devices [1].
Should be easy to fix on the firmware side. TDX has the same
requirement and the code is already there, so this should be a
one-liner in OvmfPkg/IncompatiblePciDeviceSupportDxe
Independent from that we might consider switching virtio to
pxe-virtio.rom (i.e. bios-only instead of bios+uefi) for everyone
because the uefi firmware comes with a virtio-net driver included.
take care,
Gerd
prev parent reply other threads:[~2022-07-07 6:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-11 11:30 Adjusting the default ROM option for SEV guests Vasily Ulyanov
2022-07-06 14:57 ` Claudio Fontana
2022-07-07 6:53 ` Gerd Hoffmann [this message]
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=20220707065318.b5kleuqxmxuz6h5w@sirius.home.kraxel.org \
--to=kraxel@redhat.com \
--cc=cfontana@suse.de \
--cc=f4bug@amsat.org \
--cc=jasowang@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=richard.henderson@linaro.org \
--cc=vasily.ulyanov@suse.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;
as well as URLs for NNTP newsgroup(s).