From: "Michael S. Tsirkin" <mst@redhat.com>
To: Warner Losh <imp@bsdimp.com>
Cc: Michael Tokarev <mjt@tls.msk.ru>,
QEMU Developers <qemu-devel@nongnu.org>,
Markus Armbruster <armbru@redhat.com>
Subject: Re: missing boot rom: is it really a fatal error?
Date: Mon, 15 May 2023 13:46:05 -0400 [thread overview]
Message-ID: <20230515134512-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <CANCZdfqybuKuDpkb4FsftfoCvZkq8OhixA0yj8K27WVeUjLN0g@mail.gmail.com>
On Mon, May 15, 2023 at 10:02:43AM -0600, Warner Losh wrote:
>
>
> On Mon, May 8, 2023 at 5:48 AM Michael S. Tsirkin <mst@redhat.com> wrote:
>
> On Mon, May 08, 2023 at 01:42:04PM +0300, Michael Tokarev wrote:
> > 08.05.2023 13:28, Michael S. Tsirkin wrote:
> > > On Sun, May 07, 2023 at 08:56:23PM +0300, Michael Tokarev wrote:
> > ..
> >
> > > > I'm about to revert that old change on debian, to make it just a
> warning instead
> > > > of an error (the code is different now, but the same principle
> applies), - because
> > > > I dislike dependencies which are useless 99.9% of the time and are
> trivial to
> > > > install when actually needed.
> > ..
> > > I advise against it.
> > > If you boot guest on a system with boot rom not installed you will not
> > > be able to migrate to a system with boot rom installed.
> > > why not? because we don't know how big to make the rom BAR.
> > > And users will not discover until much much later after they have
> > > painted themselves into a corner.
> >
> > Yes, I know about the migration. Actually there's an old bug report open
> > against debian qemu package, - the context is similar to the old bios128
> > vs bios256 thing in qemu upstream, - boot roms might change in size too.
> >
> > In this context though, the talk is not about migration at all. The
> missing
> > dep is in Xen HVM qemu package, a xen-only build of qemu-system-i386. And
> > this one fails to start unless the boot roms are provided. It is not even
> > capable of migration to begin with :)
> >
> > Thank you for the reminder, - very useful.
> >
> > /mjt
>
> I guess we decided we'd rather not handle reports from users about net
> boot not working. It's true most users don't need net boot but then
> that's true for most qemu functionality - 99% of users
> probably need 1% of the functionality. It's just a different 1% for each
> user...
>
>
> Yea, but to every user, their 1% is the most important thing ever...
> Or so it seems some days :)
>
> Warner
Yep. So I do not think we will be reverting this change in QEMU.
--
MST
prev parent reply other threads:[~2023-05-15 17:46 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-07 17:56 missing boot rom: is it really a fatal error? Michael Tokarev
2023-05-08 10:12 ` Thomas Huth
2023-05-08 10:28 ` Michael S. Tsirkin
2023-05-08 10:37 ` Markus Armbruster
2023-05-08 10:42 ` Michael Tokarev
2023-05-08 11:47 ` Michael S. Tsirkin
2023-05-15 16:02 ` Warner Losh
2023-05-15 17:46 ` Michael S. Tsirkin [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=20230515134512-mutt-send-email-mst@kernel.org \
--to=mst@redhat.com \
--cc=armbru@redhat.com \
--cc=imp@bsdimp.com \
--cc=mjt@tls.msk.ru \
--cc=qemu-devel@nongnu.org \
/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).