From: Gleb Natapov <gleb@redhat.com>
To: Alexander Graf <agraf@suse.de>
Cc: Paul Brook <paul@codesourcery.com>,
Hai Shan Bai <haishan.bai@gmail.com>,
qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH - V3] Port codes from qemu-kvm to support booting from SCSI disk image
Date: Wed, 18 Aug 2010 18:37:20 +0300 [thread overview]
Message-ID: <20100818153720.GG10499@redhat.com> (raw)
In-Reply-To: <632E0D52-7618-4184-990D-2918E51A61BC@suse.de>
On Wed, Aug 18, 2010 at 05:16:56PM +0200, Alexander Graf wrote:
>
> On 18.08.2010, at 17:08, Paul Brook wrote:
>
> >> The qemu-kvm could boot from SCSI disk image by utilizing seabios, this
> >> patch ported codes
> >> from qemu-kvm to let upstream qemu to support booting from SCSI disk image.
> >
> > No. This has nothing to do with SCSI.
> >
> > What it does is add a really cheap and nasty block storage device that aliases
> > one of the other block devices in the system. This is bad. The OS has no way
> > of knowing which devices are aliased, and we really don't want yet another
> > braindead guest visible interface (c.f. recent performance issues where -
> > kernel/fw_cfg were being abused)
> >
> > This has been discussed several times before. The proper solution is to teach
> > the bios how to boot off SCSI devices. IIRC support for virtio devices already
> > exists, implementing support for the SCSI controller shouldn't be that much
> > harder.
>
> Couldn't we just have an option rom for the SCSI controller? The same way the VGABIOS is a rewrite of a VGA BIOS for the Cirrus Logic...
>
>
Of course we could, but it should not be extboot, but proper scsi driver. gpxe has
src/drivers/block/scsi.c so may be it already supports qemu scsi device?
--
Gleb.
next prev parent reply other threads:[~2010-08-18 15:37 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-18 2:06 [Qemu-devel] [PATCH - V3] Port codes from qemu-kvm to support booting from SCSI disk image Hai Shan Bai
2010-08-18 2:20 ` haishan
2010-08-18 15:08 ` Paul Brook
2010-08-18 15:16 ` Alexander Graf
2010-08-18 15:31 ` Haishan Bai
2010-08-18 15:37 ` Gleb Natapov [this message]
2010-08-18 16:04 ` Paul Brook
2010-08-19 18:14 ` Blue Swirl
2010-08-18 15:54 ` Paul Brook
2010-08-20 7:44 ` Gerd Hoffmann
2010-08-20 13:42 ` Anthony Liguori
2010-08-20 14:09 ` Gerd Hoffmann
2010-08-20 14:39 ` Anthony Liguori
2010-08-21 14:20 ` Kevin O'Connor
2010-08-23 8:52 ` Gerd Hoffmann
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=20100818153720.GG10499@redhat.com \
--to=gleb@redhat.com \
--cc=agraf@suse.de \
--cc=haishan.bai@gmail.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).