Bug 709643 - Size of volume in cow type should display as virtual size in virt-manager
Summary: Size of volume in cow type should display as virtual size in virt-manager
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: libvirt
Version: 6.2
Hardware: x86_64
OS: Linux
low
low
Target Milestone: rc
: ---
Assignee: Osier Yang
QA Contact: Virtualization Bugs
URL:
Whiteboard:
Depends On: 704943
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-06-01 09:11 UTC by Min Zhan
Modified: 2011-11-23 03:14 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of: 704943
Environment:
Last Closed: 2011-11-23 03:14:03 UTC
Target Upstream Version:


Attachments (Terms of Use)

Description Min Zhan 2011-06-01 09:11:20 UTC
+++ This bug was initially created as a clone of Bug #704943 +++

Description of problem:
When create a volume in virt-manager, format as cow, allocate 10M, but after finish creating,  the size display as 0M in the vol list.

Version-Release number of selected component (if applicable):
# uname -r
2.6.32-131.0.1.el6.x86_64
libvirt-0.9.1-1.el6
virt-manager-0.8.6-4.el6.noarch

How reproducible:
Always

Steps to Reproduce:
1. In dir pool, Click New Volume, input the vol-name, and Format as Cow, Max capacity as 10M, Allocation as 10M, Then finish
2. Check the newly created vol in the volumes list
  
Actual results:
The size display as 0M

# qemu-img info /var/lib/libvirt/dir/a1.img
image: /var/lib/libvirt/dir/a1.img
file format: cow
virtual size: 10M (10485760 bytes)
disk size: 8.0K

# du -s -B1 /var/lib/libvirt/dir/a1.img 
8192	/var/lib/libvirt/dir/a1.img


Expected results:
The size should display as virtual size,which is 10M

Additional info:
For qcow2, qcow, raw type, they all display the virtual size as Size value, not the disk size. I think they should keep consistent.

Comment 1 Cole Robinson 2011-06-10 22:44:57 UTC
Sounds like a libvirt issue, since the code in virt-manager handles all these image formats the same.


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