Bug 709643

Summary: Size of volume in cow type should display as virtual size in virt-manager
Product: Red Hat Enterprise Linux 6 Reporter: Min Zhan <mzhan>
Component: libvirtAssignee: Osier Yang <jyang>
Status: CLOSED WONTFIX QA Contact: Virtualization Bugs <virt-bugs>
Severity: low Docs Contact:
Priority: low    
Version: 6.2CC: dallan, dyuan, mzhan, nzhang, rwu, whuang
Target Milestone: rc   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: 704943 Environment:
Last Closed: 2011-11-23 03:14:03 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Bug Depends On: 704943    
Bug Blocks:    

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.