Bug 1576862
| Summary: | Uploaded image: Virtual Size of qcow2 image is not reflected at guest OS level | |||
|---|---|---|---|---|
| Product: | Red Hat Enterprise Virtualization Manager | Reporter: | Ameya Charekar <achareka> | |
| Component: | ovirt-engine | Assignee: | Daniel Erez <derez> | |
| Status: | CLOSED ERRATA | QA Contact: | Yosi Ben Shimon <ybenshim> | |
| Severity: | low | Docs Contact: | ||
| Priority: | low | |||
| Version: | 4.1.11 | CC: | derez, ebenahar, lsurette, mtessun, Rhev-m-bugs, srevivo, tnisan | |
| Target Milestone: | ovirt-4.3.0 | Keywords: | ZStream | |
| Target Release: | 4.3.0 | Flags: | lsvaty:
testing_plan_complete-
|
|
| Hardware: | Unspecified | |||
| OS: | Unspecified | |||
| Whiteboard: | ||||
| Fixed In Version: | ovirt-engine-4.3.0_alpha | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | ||
| Clone Of: | ||||
| : | 1585454 (view as bug list) | Environment: | ||
| Last Closed: | 2019-05-08 12:37:35 UTC | Type: | Bug | |
| Regression: | --- | Mount Type: | --- | |
| Documentation: | --- | CRM: | ||
| Verified Versions: | Category: | --- | ||
| oVirt Team: | Storage | RHEL 7.3 requirements from Atomic Host: | ||
| Cloudforms Team: | --- | Target Upstream Version: | ||
| Embargoed: | ||||
| Bug Depends On: | ||||
| Bug Blocks: | 1585454 | |||
|
Description
Ameya Charekar
2018-05-10 15:04:30 UTC
So essentially, we are not extending the disk during upload? yet another reason why we should NOT ask for disk size during upload, IMHO. (In reply to Yaniv Kaul from comment #3) > So essentially, we are not extending the disk during upload? yet another > reason why we should NOT ask for disk size during upload, IMHO. The suggested fix is to set the disk size automatically (in upload disk dialog), using size information from the qcow header (or file size for raw images). WARN: Bug status wasn't changed from MODIFIED to ON_QA due to the following reason:
[Found non-acked flags: '{'rhevm-4.2.z': '?'}', ]
For more info please contact: rhv-devops: Bug status wasn't changed from MODIFIED to ON_QA due to the following reason:
[Found non-acked flags: '{'rhevm-4.2.z': '?'}', ]
For more info please contact: rhv-devops
Verify according to https://bugzilla.redhat.com/show_bug.cgi?id=1585454#c9 Tested using:
ovirt-engine-4.3.0-0.0.master.20180815091554.gitd5455ea.el7.noarch
ovirt-imageio-proxy-1.4.2-0.201808131405.gitec63551.el7.centos.p.noarch
Uploaded image (local):
$ qemu-img info temp_img.qcow2
image: temp_img.qcow2
file format: qcow2
virtual size: 10G (10737418240 bytes)
disk size: 50M
cluster_size: 65536
Format specific information:
compat: 0.10
refcount bits: 16
On storage after upload:
$ qemu-img info 213ac123-8f5a-46df-b4a6-16e39bf2f3a0
image: 213ac123-8f5a-46df-b4a6-16e39bf2f3a0
file format: qcow2
virtual size: 10G (10737418240 bytes)
disk size: 246M
cluster_size: 65536
Format specific information:
compat: 0.10
refcount bits: 16
From database before & after attaching to VM (and boot):
engine=# select image_guid,size from all_disks_including_snapshots where vm_names ='test_vm';
image_guid | size
--------------------------------------+-------------
213ac123-8f5a-46df-b4a6-16e39bf2f3a0 | 10737418240
Moving to VERIFIED
WARN: Bug status (VERIFIED) wasn't changed but the folowing should be fixed:
[Found non-acked flags: '{'rhevm-4.3-ga': '?'}', ]
For more info please contact: rhv-devops: Bug status (VERIFIED) wasn't changed but the folowing should be fixed:
[Found non-acked flags: '{'rhevm-4.3-ga': '?'}', ]
For more info please contact: rhv-devops
WARN: Bug status (VERIFIED) wasn't changed but the folowing should be fixed:
[Found non-acked flags: '{'rhevm-4.3-ga': '?'}', ]
For more info please contact: rhv-devops: Bug status (VERIFIED) wasn't changed but the folowing should be fixed:
[Found non-acked flags: '{'rhevm-4.3-ga': '?'}', ]
For more info please contact: rhv-devops
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. https://access.redhat.com/errata/RHEA-2019:1085 sync2jira sync2jira |