Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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.
Description
In "create a new virtual machine" dialog of virt-manager,unit of "Storage" is incorrect,it shows as Gb instead of GB.
Version
virt-manager-0.9.0-15.el6.x86_64
libvirt-0.10.2-6.el6.x86_64
How reproducible:
100%
Steps to Reproduce
1.Launch virt-manager.
2.Click "New" to create a virtual machine,input name,choose "Import existing disk image",click forward.
3.Input the existing storage path,eg:/var/lib/libvirt/images/qcow2.img,click forward.
4.Choose memory and cpu,click forward.
5.On the dialog,you can see the unit of "Storage" is Gb.
Actual results：
As step5 shows.
Expected results:
The unit of "Storage" shows as GB.
Additional info:
Comment 3Martin Kletzander
2013-03-14 14:15:24 UTC
Already fixed in RELEASE-0.9.0-1-104-gb7a533a:
commit b7a533a45116bea4d156f9cde6dd934a1d2e28ed
Author: Cole Robinson <crobinso>
Date: Sun Jan 29 21:51:07 2012 -0500
create: s/Gb/GB/ for storage units
I can reproduce this bug:
Version:
virt-manager-0.9.0-15.el6.x86_64
libvirt-0.10.2-7.el6.x86_64(libvirt-0.10.2-6.el6.x86_64 has been deleted)
Steps for Reproduce:
1.Launch #virt-manager.
2.Click "New" to create a virtual machine,input name,choose "Import existing disk image",click forward.
3.Input the existing storage path, click forward.
4.Choose memory and cpu,click forward.
5.On the step5 dialog, see the unit of "Storage".
Result:
Storage: Gb
Verify:
libvirt-0.10.2-21.el6.x86_64
virt-manager-0.9.0-19.el6.x86_64
Steps for Verify:
1.Launch #virt-manager.
2.Click "New" to create a virtual machine,input name,choose "Import existing disk image",click forward.
3.Input the existing storage path, click forward.
4.Choose memory and cpu,click forward.
5.On the step5 dialog, see the unit of "Storage".
Result:
Storage: GB
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
http://rhn.redhat.com/errata/RHBA-2013-1646.html