RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 613557 - Cannot create qcow2 format when create new volume from LVM Volume Group
Summary: Cannot create qcow2 format when create new volume from LVM Volume Group
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: libvirt
Version: 6.0
Hardware: All
OS: Linux
medium
medium
Target Milestone: rc
: ---
Assignee: Daniel Veillard
QA Contact: Virtualization Bugs
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-07-12 09:08 UTC by Golita Yue
Modified: 2011-06-20 20:59 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-06-20 20:59:53 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
screenshot (40.86 KB, image/png)
2010-07-12 09:08 UTC, Golita Yue
no flags Details

Description Golita Yue 2010-07-12 09:08:23 UTC
Created attachment 431116 [details]
screenshot

Description of problem:
When I create new volume from LVM Volume Group, I cannot select qcow2 format and the format item is grey, the default is 'raw'.

Version-Release number of selected component (if applicable):
Virtual Machine Manager 0.8.4


How reproducible:
100%

Steps to Reproduce:
1. Add LVM Volume Group in host
   go to Edit -> Host Details -> Storage -> Add Pool
   input 'Name' and 'Type' ->logical:LVM Volume Group; add 'Target path' then finished.
2. Create New volume
   go to Edit -> Host Details -> Storage -> LVM Volume Group, press New Volume button, 
  
Actual results:
the 'Format' item is grey, cannot select the qcow2 format from this item.

Expected results:
can select qcow2 format

Additional info:

Comment 2 RHEL Program Management 2010-07-15 15:11:31 UTC
This issue has been proposed when we are only considering blocker
issues in the current Red Hat Enterprise Linux release. It has
been denied for the current Red Hat Enterprise Linux release.

** If you would still like this issue considered for the current
release, ask your support representative to file as a blocker on
your behalf. Otherwise ask that it be considered for the next
Red Hat Enterprise Linux release. **

Comment 3 Cole Robinson 2010-11-22 17:15:33 UTC
This is actually a limitation at the libvirt level. Reassigning

Comment 4 Suzanne Logcher 2011-03-28 21:10:59 UTC
Since RHEL 6.1 External Beta has begun, and this bug remains 
unresolved, it has been rejected as it is not proposed as an 
exception or blocker.

Red Hat invites you to ask your support representative to 
propose this request, if appropriate and relevant, in the 
next release of Red Hat Enterprise Linux.


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