qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Ryan Harper <ryanh@us.ibm.com>
To: linux-hotplug@vger.kernel.org
Cc: john cooper <john.cooper@redhat.com>,
	Rusty Russell <rusty@rustcorp.com.au>,
	qemu-devel@nongnu.org, Ryan Harper <ryanh@us.ibm.com>
Subject: [Qemu-devel] [PATCH v3 0/2] Add virtio-blk support to persistent-storage rules
Date: Fri, 25 Jun 2010 08:59:21 -0500	[thread overview]
Message-ID: <1277474363-6534-1-git-send-email-ryanh@us.ibm.com> (raw)

This patch series provides updates to udev to allow the creation symlinks for
virtio-blk devices, specifically disk/by-id and disk/by-path.  This is most
useful for virtio-blk devices that do not yet have any filesystem for which a
UUID can be extracted (disk/by-uuid).  These patches (save the path_id fix)
require an updated[1] qemu (on the host) and virtio-blk (in the guest)[2]  to
generate the by-id path; however if the guest or host qemu isn't capable
then no action is taken.

Changes since v2:
- Added 'serial' sysfs attribute to virtio-blk code upstream [2]
- Dropped VBID ioctl upstream [3]
- Switched rules to extract serial attributes directly

Changes since v1:
- Switch ID_VIRTIO_SERIAL to ID_SERIAL
- Switched IOCTL_CMD to use numeric value
- Add ID_SERIAL_SHORT
- Update persistent-storage rules to use ID_SERIAL for virtioblk_id


1. http://lists.gnu.org/archive/html/qemu-devel/2010-03/msg01869.html
2. https://lists.linux-foundation.org/pipermail/virtualization/2010-June/015326.html
3. https://lists.linux-foundation.org/pipermail/virtualization/2010-June/015325.html

             reply	other threads:[~2010-06-25 17:46 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-25 13:59 Ryan Harper [this message]
2010-06-25 13:59 ` [Qemu-devel] [PATCH 1/2] Add virtio-blk support to path_id Ryan Harper
2010-06-25 13:59 ` [Qemu-devel] [PATCH 2/2] Add virtio-blk by-id rules based on 'serial' attribute Ryan Harper
2010-06-29 15:29 ` [Qemu-devel] Re: [PATCH v3 0/2] Add virtio-blk support to persistent-storage rules Kay Sievers

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=1277474363-6534-1-git-send-email-ryanh@us.ibm.com \
    --to=ryanh@us.ibm.com \
    --cc=john.cooper@redhat.com \
    --cc=linux-hotplug@vger.kernel.org \
    --cc=qemu-devel@nongnu.org \
    --cc=rusty@rustcorp.com.au \
    /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).