qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Gerhard Wiesinger <lists@wiesinger.com>
To: Gerd Hoffmann <kraxel@redhat.com>
Cc: Gerhard Wiesinger <lists@wiesinger.com>,
	Brian Jackson <iggy@theiggy.com>,
	Michael Tokarev <mjt@tls.msk.ru>,
	qemu-devel@nongnu.org, Paolo Bonzini <pbonzini@redhat.com>
Subject: Re: [Qemu-devel] XP install cores with SCSI LSI 53C895A disks
Date: Fri, 9 Mar 2012 08:46:49 +0100 (CET)	[thread overview]
Message-ID: <alpine.LFD.2.02.1203090843170.28069@bbs.intern> (raw)
In-Reply-To: <4F59AF52.7070206@redhat.com>

On Fri, 9 Mar 2012, Gerd Hoffmann wrote:

>  Hi,
>
>>>> #2 isn't an issue actually, at least for Debian users --
>>>
>>> Well, it is, to some degree.  Because vanilla upstream doesn't support
>>> booting from lsi it has alot less users and alot less regression testing
>>> (like autotest runs of lsi-scsi installs), which sums up to more bugs
>>> staying unnoticed like the one which triggered this thread.
>>
>> What's the holdup to integrate it into QEMU?
>
> Extboot is considered obsolete and thus several attempts to merge it
> into upstream qemu failed.  It started its life as hack to allow
> qemu-kvm boot from virtio-blk devices, which happened to work for lsi
> too.  virtio-blk is supported by seabios natively these days.
>
> Adding lsi support to seabios shouldn't be that hard.  Paolo paved the
> way by restructing the existing scsi disk/cdrom bits in seabios so they
> work for both usb-storage and virtio-scsi.  Adding support for yet
> another scsi hba should be easy, all the support bits for handling disks
> and booting from cdrom are there already.
>
> It just needs someone to sit down for a week or two and hack it up.

@Paolo: Would that be easily possible?

BTW: What do you think anout that:
Handling INT13h always directly through virtio-scsi regardless of selected 
SCSI adapter, or when OS driver is loaded through SCSI adapter, so just 
have 2 ways to the disks:
1.) Through INT13h to virtio-scsi and then to the disks
2.) Through SCSI adapter and then to the disks (OS driver loaded)

Ciao,
Gerhard

--
http://www.wiesinger.com/

  reply	other threads:[~2012-03-09  7:47 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-04 20:13 [Qemu-devel] XP install cores with SCSI LSI 53C895A disks Gerhard Wiesinger
2012-03-07  6:41 ` Gerhard Wiesinger
2012-03-07 14:51   ` Brian Jackson
2012-03-07 19:58     ` Gerhard Wiesinger
2012-03-08  7:44       ` Gerd Hoffmann
2012-03-08  8:54         ` Michael Tokarev
2012-03-08 10:07           ` Gerd Hoffmann
2012-03-09  6:28             ` Gerhard Wiesinger
2012-03-09  7:20               ` Gerd Hoffmann
2012-03-09  7:46                 ` Gerhard Wiesinger [this message]
2012-03-09  8:08                   ` Paolo Bonzini
2012-03-09  6:25           ` Gerhard Wiesinger
2012-03-09  6:18         ` Gerhard Wiesinger
2012-03-09  7:35           ` Gerd Hoffmann
2012-03-09  8:00             ` Paolo Bonzini
2012-03-09 11:50           ` Kevin O'Connor
2012-03-09 16:48       ` Brian Jackson

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=alpine.LFD.2.02.1203090843170.28069@bbs.intern \
    --to=lists@wiesinger.com \
    --cc=iggy@theiggy.com \
    --cc=kraxel@redhat.com \
    --cc=mjt@tls.msk.ru \
    --cc=pbonzini@redhat.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).