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 893740 - Different Default Settings for New Storage Volumes (8GB vs 1GB)
Summary: Different Default Settings for New Storage Volumes (8GB vs 1GB)
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: virt-manager
Version: 7.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Martin Kletzander
QA Contact: Virtualization Bugs
URL:
Whiteboard:
Depends On: 852173
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-01-09 20:07 UTC by Dave Allan
Modified: 2016-04-26 15:20 UTC (History)
10 users (show)

Fixed In Version: virt-manager-0.10.0-1.el7
Doc Type: Bug Fix
Doc Text:
Clone Of: 852173
Environment:
Last Closed: 2014-06-13 13:04:49 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Dave Allan 2013-01-09 20:07:44 UTC
+++ This bug was initially created as a clone of Bug #852173 +++

Description of problem:
In Virtual Machine Manager 0.9.4 from Fedora 17, whenever I go to make a new vm, I put it in a custom path (my root partition is small, but I have a lot of space in my home directory) and have to click on the browse button. In that dialog, the default size for a vm differs from the default size suggested if I hadn't gone with a custom path. 

Why is the default size 1gb in one place, and 8gb in the standard flow? I feel like they should either be the same, since 1gb is not enough space to do anything useful with a standard distro, or it should remember my last entry and populate with that instead (I usually add a 0 and go with 10gb, after making the mistake of accepting the default once and having to recreate that vm).

Version-Release number of selected component (if applicable):
virt-manager-0.9.4-1.fc17.noarch

How reproducible:
Always

Steps to Reproduce:
1. Click create new vm
2. enter information until you get to step 4 of 5
3. Notice that default size of disk is 8GB
4. Select 2nd radio button, click Browse button
5. Click New Volume
6. Notice that Storage Volume Quota Max Capacity is 1000MB

  
Actual results:
Default option results in a disk size of 1GB

Expected results:
Default option results in a disk size that matches previous default, 8GB, or at least matches what I manually set it to last time I created a New Storage Volume

Additional info:

--- Additional comment from Matt Reid on 2012-08-27 14:31:50 EDT ---

Created attachment 607319 [details]
Default Size for Custom Path Volumes

Comment 2 Martin Kletzander 2013-02-06 16:24:35 UTC
Patch proposed upstream:

https://www.redhat.com/archives/virt-tools-list/2013-February/msg00054.html

Comment 3 Martin Kletzander 2013-02-07 09:08:21 UTC
Moving to POST:

commit 46c8ee58dcc1a057222212ebf09bbc0137f39f77
Author: Martin Kletzander <mkletzan>
Date:   Wed Feb 6 17:23:21 2013 +0100

    Match default storage size values

Comment 4 Cui Lei 2013-02-20 06:17:30 UTC
I can reproduce this issue in RHEL7 following comment1's steps.

Version-Release number of selected component:
virt-manager-0.9.4-4.el7.noarch
kernel: 3.7.0-0.34.el7.x86_64
libvirt-1.0.2-1.el7.x86_64

Comment 6 CongDong 2013-08-14 05:40:40 UTC
I can reproduce this bug:

# rpm -qa virt-manager libvirt
virt-manager-0.9.4-4.el7.noarch
libvirt-1.1.0-2.el7.x86_64

steps:
As the steps in description.

Result:
Default option results in a disk size of 1GB.


Verify:
# rpm -qa virt-manager libvirt
virt-manager-0.10.0-2.el7.noarch
libvirt-1.1.0-2.el7.x86_64

steps:
As the steps in description.

Result:
Default option results in a disk size of 8GB.

As the result, set VERIFIED.

Comment 7 Ludek Smid 2014-06-13 13:04:49 UTC
This request was resolved in Red Hat Enterprise Linux 7.0.

Contact your manager or support representative in case you have further questions about the request.


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