Red Hat Bugzilla – Bug 1459455
Creating a Clone vm from template with Format "QCOW2" and Target "block based storage" has a disk with same actual and virtual size
Last modified: 2017-11-15 10:38:12 EST
Created attachment 1285704 [details]
engine and vdsm logs
[reply] [−] Private Description Ameya Charekar 2017-02-04 01:13:42 EST
Description of problem:
Creating a Clone vm from template with Format "QCOW2" and Target "block based storage" created disks with actual and virtual size same.
Version-Release number of selected component (if applicable):
Red Hat Virtualization Manager Version: 220.127.116.11-0.1.el7ev
Steps to Reproduce:
1. Create a New VM from template.
2. Select Format "QCOW2".
3. Select any block based storage.
Actual size and Virtual size is same.
Virtual size should not be same as actual size.
File based storage do not have this issue.
Tal, didn't we solve something like this already?
(note the reported version).
Eyal - does this reproduce with modern 4.1.z engines?
This bug report has Keywords: Regression or TestBlocker.
Since no regressions or test blockers are allowed between releases, it is also being identified as a blocker for this release. Please resolve ASAP.
Sorry about the versions confusion, copy-paste error.
Engine - 4.2.0-0.0.master.20170602194647.gitaf23eb5.el7.centos
VDSM - 4.20.0-970.gitf0c24e5.el7.centos.x86_64
Engine - 18.104.22.168-0.1.el7
VDSM - 4.19.17-1.el7ev.x86_64
Continuing the conversation from https://bugzilla.redhat.com/show_bug.cgi?id=1419240.
(In reply to Eyal Shenitzky from comment #18)
> The relevant operation is create VM from a template as clone with disk QCOW.
> not copy disk.
> But let's move the conversation to the relevant bug -
Create VM will call copy operation from source Template to the VM.
As noted in https://bugzilla.redhat.com/show_bug.cgi?id=1419240#c17, I could not find any reference in the log which indicate that the destination storage domain is block storage domain.
Can you please share the destination block storage domain the copy was done to, and the log of the copy operation which was done to that block SD?
Create a VM to a block-based storage domain from Template with a disk on block-based storage domain using sdm_copy (data-center 4.2/4.1).
Created attachment 1286818 [details]
engine and vdsm logs new
I think that the problem is related to the Template's copy disks.
Can you please try to delete the Template disk's copies and try to create a new VM from Template, what is the actual size then?
You right, after removing the disk copies the actual size (6 GB) was smaller than the virtual size (10 GB)
(In reply to Eyal Shenitzky from comment #9)
> You right, after removing the disk copies the actual size (6 GB) was smaller
> than the virtual size (10 GB)
So is this a NOTABUG?
No, it is a bug.
Maor found the root cause and I verify that it occurs also in my environment.
The problem is that when the template disk has multiple copies, the scenario described above occur, but when the template has no copies it works as expected.
Just to make sure I understand - this is a *display* bug where the disk's size contains the size of the template too?
The actual image's size on the storage is OK?
The bug is not only a display bug, there is an issue with the images size.
Maor do you have more info?
*** Bug 1480133 has been marked as a duplicate of this bug. ***