qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Alexander Graf <agraf@suse.de>
To: Paul Brook <paul@codesourcery.com>
Cc: Kevin O'Connor <kevin@koconnor.net>,
	qemu-devel@nongnu.org, Gerd Hoffmann <kraxel@redhat.com>
Subject: Re: [Qemu-devel] [PATCH 0/2] extboot reloaded.
Date: Tue, 17 Nov 2009 15:23:38 +0100	[thread overview]
Message-ID: <4B02B1EA.5060000@suse.de> (raw)
In-Reply-To: <200911171335.22727.paul@codesourcery.com>

Paul Brook wrote:
> On Tuesday 17 November 2009, Gerd Hoffmann wrote:
>   
>> On 11/17/09 13:36, Paul Brook wrote:
>>     
>>>>> In fact I'd much prefer to see extboot rewritten to just virtio-block.
>>>>>           
>>>> Hmm, I'd prefer something which is *not* used by the guest OS, so it is
>>>> a pure bootloader thing.  When using it to boot from scsi you don't want
>>>> to have the disk show up twice (as virtio and scsi) in the guest.
>>>>         
>>> You're assuming noone ever writes OS support for extboot...
>>>       
>> Which would be almost as silly as writing OS support for bios-int13 ...
>>     
>
> Not entirely. int13 is a software interface, extboot is a hardware interface.
> Look at it the other way round: If I already have my low performance boot 
> device exposed via extboot (on an otherwise diskless client), why should I 
> have to also expose it via virtio-blk just so that the guest can access it for 
> installing kernel upgrades.
>   

Because that's not what you'd use it for. That's what -kernel and
-initrd are there for.

IMHO having a BIOS backdoor is a good thing in general. If anyone wants
to destroy their user experience by writing a driver for that in their
OS, I'm good with that, but let's not expose things twice _to users_ as
the default case.


Alex

  reply	other threads:[~2009-11-17 14:23 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-16 18:04 [Qemu-devel] [PATCH 0/2] extboot reloaded Gerd Hoffmann
2009-11-16 18:04 ` [Qemu-devel] [PATCH 1/2] extboot: add option rom Gerd Hoffmann
2009-11-16 18:04 ` [Qemu-devel] [PATCH 2/2] extboot: qemu code Gerd Hoffmann
2009-11-16 19:24 ` [Qemu-devel] [PATCH 0/2] extboot reloaded Anthony Liguori
2009-11-16 20:20   ` Gerd Hoffmann
2009-11-16 21:14     ` Anthony Liguori
2009-11-17 11:36       ` Paul Brook
2009-11-17 12:26         ` Gerd Hoffmann
2009-11-17 12:36           ` Paul Brook
2009-11-17 13:01             ` Gerd Hoffmann
2009-11-17 13:35               ` Paul Brook
2009-11-17 14:23                 ` Alexander Graf [this message]
2009-11-17 14:53                   ` Anthony Liguori
2009-11-18  4:34       ` Kevin O'Connor
2009-11-18 14:42         ` Anthony Liguori
2009-11-19  1:27           ` Kevin O'Connor
2009-11-16 22:39     ` Jamie Lokier
2009-11-16 22:55       ` Anthony Liguori

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=4B02B1EA.5060000@suse.de \
    --to=agraf@suse.de \
    --cc=kevin@koconnor.net \
    --cc=kraxel@redhat.com \
    --cc=paul@codesourcery.com \
    --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).