From: Ryan Harper <ryanh@us.ibm.com>
To: Jule Slootbeek <jsslists@gmail.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] virtio_blk unique device ID
Date: Thu, 29 Jan 2009 16:47:56 -0600 [thread overview]
Message-ID: <20090129224756.GI13481@us.ibm.com> (raw)
In-Reply-To: <bf1361bc0901291400w25265104g3845702fc19bcc31@mail.gmail.com>
* Jule Slootbeek <jsslists@gmail.com> [2009-01-29 16:13]:
> All,
> I was recently testing the workings of virtio to provision SAN block devices
> to a domain, which worked great! However, i could not find a way to find the
> UID of a virto_blk device. The scenario I had created was the following. a
> LUN provisioned to my KVM (kvm-83) hypervisor over two paths, both paths
> mapped to my domain using virtio_blk. When configuring multipath-tools in
> the domain I could not find a way to find the UID of the LUN in order to
> create the multipath config. On a SCSI device, I would use the
> /lib/udev/scsi_id tools to discover this ID. I am using libvir/qemu 0.5.1 in
> Ubuntu Jaunty Alpha-3 as hypervisor and virtual machine.
> Does the virtio_blk driver provide a UID to its devices, and is there a way
> to get this ID in userspace?
use uuid? Some distros (Ubuntu for example) mount via UUID
% blkid
/dev/vda1: UUID="6331275f-f10d-4684-8aa8-e8aca1582b9d" TYPE="swap"
/dev/vda2: UUID="cf121062-fd27-4151-8a68-6cb940e449fe" TYPE="ext3"
# ls -al /dev/disk/by-uuid/
total 0
lrwxrwxrwx 1 root root 10 Jan 29 17:10 6331275f-f10d-4684-8aa8-e8aca1582b9d -> ../../vda1
lrwxrwxrwx 1 root root 10 Jan 29 17:10 cf121062-fd27-4151-8a68-6cb940e449fe -> ../../vda2
--
Ryan Harper
Software Engineer; Linux Technology Center
IBM Corp., Austin, Tx
ryanh@us.ibm.com
next prev parent reply other threads:[~2009-01-29 22:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-29 22:00 [Qemu-devel] virtio_blk unique device ID Jule Slootbeek
2009-01-29 22:47 ` Ryan Harper [this message]
2009-01-30 14:00 ` Jule Slootbeek
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=20090129224756.GI13481@us.ibm.com \
--to=ryanh@us.ibm.com \
--cc=jsslists@gmail.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).