From: Paolo Bonzini <pbonzini@redhat.com>
To: Hannes Reinecke <hare@suse.de>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 0/2] scsi: enclosure support
Date: Fri, 4 Aug 2017 02:10:11 -0400 (EDT) [thread overview]
Message-ID: <637661261.1409588.1501827011350.JavaMail.zimbra@redhat.com> (raw)
In-Reply-To: <41045776-f4c2-20f5-1000-c826e314cfe2@suse.de>
> On 08/03/2017 05:10 PM, Paolo Bonzini wrote:
> > On 03/08/2017 15:26, Hannes Reinecke wrote:
> >> Hi all,
> >>
> >> due to a customer issue I've added simple subenclosure support
> >> to the SCSI emulation. The patch simply converts the current invisible
> >> LUN0 into an enclosure device; existing setups using LUN0 as disks or
> >> CD-ROMs will not be affected.
> >
> > What is the issue exactly? That is, for what is it necessary to have a
> > dummy enclosure?
> >
> Well, stock linux displays some very interesting error messages for
> these types of enclosures. Which was the prime mover for doing this.
--verbose?
> > I agree with Dan that this need machine type compatibility gunk. For
> > example, could the new device affect /dev/sgN numbering?
>
> Yes, indeed it would.
>
> What about a new option to the scsi driver?
If you do that, you've done 99% of the work to do compatibility so I
won't complain and do the 1% myself. :)
Paolo
next prev parent reply other threads:[~2017-08-04 6:10 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-03 13:26 [Qemu-devel] [PATCH 0/2] scsi: enclosure support Hannes Reinecke
2017-08-03 13:27 ` [Qemu-devel] [PATCH 1/2] scsi: Make LUN 0 a simple enclosure Hannes Reinecke
2017-08-03 13:32 ` Daniel P. Berrange
2017-08-03 13:37 ` Hannes Reinecke
2017-08-03 13:27 ` [Qemu-devel] [PATCH 2/2] scsi: use qemu_uuid to generate logical identifier for SES Hannes Reinecke
2017-08-03 15:10 ` [Qemu-devel] [PATCH 0/2] scsi: enclosure support Paolo Bonzini
2017-08-04 5:47 ` Hannes Reinecke
2017-08-04 6:10 ` Paolo Bonzini [this message]
2017-08-04 7:34 ` Hannes Reinecke
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=637661261.1409588.1501827011350.JavaMail.zimbra@redhat.com \
--to=pbonzini@redhat.com \
--cc=hare@suse.de \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.