Bug 604929 - Add --uuid option to virsh vol-pool command
Add --uuid option to virsh vol-pool command
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: libvirt (Show other bugs)
All Linux
low Severity low
: rc
: 6.0
Assigned To: Eric Blake
Virtualization Bugs
Depends On:
  Show dependency treegraph
Reported: 2010-06-16 22:45 EDT by Justin Clift
Modified: 2010-11-11 09:50 EST (History)
6 users (show)

See Also:
Fixed In Version: libvirt-0_8_1-10_el6
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2010-11-11 09:50:04 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Justin Clift 2010-06-16 22:45:16 EDT
Description of problem:

The vol-pool command in virsh is only capable of returning a pool name, not a pool UUID.

It's not a killer, but it would be nice if vol-pool supported returning a pool UUID as well.

A patch has been submitted upstream that adds this support:


Version-Release number of selected component (if applicable):

Comment 2 RHEL Product and Program Management 2010-06-16 23:12:55 EDT
This request was evaluated by Red Hat Product Management for inclusion in a Red
Hat Enterprise Linux major release.  Product Management has requested further
review of this request by Red Hat Engineering, for potential inclusion in a Red
Hat Enterprise Linux Major release.  This request is not yet committed for
Comment 4 Dave Allan 2010-06-23 21:34:11 EDT
libvirt-0_8_1-10_el6 has been built in RHEL-6-candidate with the fix.

Comment 5 dyuan 2010-06-28 23:31:21 EDT
Verified PASSED with libvirt-0.8.1-10.el6.

# virsh vol-pool --uuid /mnt/vol/foo.img

# virsh vol-pool  /mnt/vol/foo.img
Comment 6 xhu 2010-09-08 01:34:39 EDT
Verified this bug with RHEL6 RC build and it passed:
Comment 7 releng-rhel@redhat.com 2010-11-11 09:50:04 EST
Red Hat Enterprise Linux 6.0 is now available and should resolve
the problem described in this bug report. This report is therefore being closed
with a resolution of CURRENTRELEASE. You may reopen this bug report if the
solution does not work for you.

Note You need to log in before you can comment on or make changes to this bug.