From: Stefan Hajnoczi <stefanha@gmail.com>
To: Hannes Reinecke <hare@suse.de>
Cc: Johannes Thumshirn <jthumshirn@suse.com>,
Paolo Bonzini <pbonzini@redhat.com>,
qemu-devel@nongnu.org, Alexander Graf <agraf@suse.de>
Subject: Re: [Qemu-devel] [PATCH RFC 0/8] scsi-disk: Active/passive ALUA support
Date: Thu, 10 Dec 2015 16:26:41 +0800 [thread overview]
Message-ID: <20151210082641.GA4222@stefanha-x1.localdomain> (raw)
In-Reply-To: <1448636346-24641-1-git-send-email-hare@suse.de>
[-- Attachment #1: Type: text/plain, Size: 1423 bytes --]
On Fri, Nov 27, 2015 at 03:58:58PM +0100, Hannes Reinecke wrote:
> here's now an updated version to enable ALUA and simplified
> active/passive multipath support for qemu.
>
> This patchset relies on having _two_ block devices configured,
> and two SCSI disks pointing to those block devices with the
> _same_ 'wwn' property and unique 'port_group' properties.
> I know, this is a bit of a nasty hack, but I hope to add
> proper multipath support (with several SCSI devices pointing /
> linking to the same block device) in the near future.
>
> It also implements a 'alua_policy', which allows for simulating
> an 'active/passive' multipath setup.
>
> And for testing I've implemented a 'block_disconnect' HMP command,
> which simulates a link failure for the attached devices.
>
> I wouldn't object if someone declares this a gross hack, but with
> it I can finally simulate real-life multipath failover and do
> some functional multipath-tools testing withouth having to recurse
> on using real hardware.
I'm not familiar with how ALUA works but have been thinking about a
multipath problem:
If the host has SCSI disks that are marked 'offline' then QEMU will
refuse to start up since it cannot open the block device (ENXIO).
Does it make sense to allow guests to start in this condition?
I think we'd need to notice when the disk comes back online and notify
the guest.
Stefan
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 473 bytes --]
next prev parent reply other threads:[~2015-12-10 8:26 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-27 14:58 [Qemu-devel] [PATCH RFC 0/8] scsi-disk: Active/passive ALUA support Hannes Reinecke
2015-11-27 14:58 ` [Qemu-devel] [PATCH 1/8] scsi-disk: Add 'port_group' property Hannes Reinecke
2015-11-27 14:59 ` [Qemu-devel] [PATCH 2/8] scsi-disk: Add 'alua_state' property Hannes Reinecke
2015-11-27 14:59 ` [Qemu-devel] [PATCH 3/8] scsi-disk: Implement 'REPORT TARGET PORT GROUPS' Hannes Reinecke
2015-11-27 14:59 ` [Qemu-devel] [PATCH 4/8] scsi-disk: Implement 'SET " Hannes Reinecke
2015-11-27 14:59 ` [Qemu-devel] [PATCH 5/8] scsi-disk: implement ALUA policy Hannes Reinecke
2015-11-27 14:59 ` [Qemu-devel] [PATCH 6/8] scsi-disk: Allow READ CAPACITY in standby Hannes Reinecke
2015-11-27 14:59 ` [Qemu-devel] [PATCH 7/8] scsi-disk: Implement 'alua_preferred' option Hannes Reinecke
2015-11-27 14:59 ` [Qemu-devel] [PATCH 8/8] block: Implement 'block_disconnect' HMP command Hannes Reinecke
2015-11-27 18:00 ` Eric Blake
2015-12-10 8:26 ` Stefan Hajnoczi [this message]
2015-12-10 9:13 ` [Qemu-devel] [PATCH RFC 0/8] scsi-disk: Active/passive ALUA support Hannes Reinecke
2015-12-14 7:24 ` Stefan Hajnoczi
2015-12-14 7:35 ` Hannes Reinecke
2015-12-15 3:02 ` Stefan Hajnoczi
2015-12-15 6:49 ` 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=20151210082641.GA4222@stefanha-x1.localdomain \
--to=stefanha@gmail.com \
--cc=agraf@suse.de \
--cc=hare@suse.de \
--cc=jthumshirn@suse.com \
--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).