
Hi everyone, please, can you limit the "Create VM" process somewhere so that setting up quota does not load the server so much, especially storage when duplicating the template disk?

On Wed, Apr 21, 2021 at 10:07 AM <ovirt.org@nevim.eu> wrote:
Hi everyone, please, can you limit the "Create VM" process somewhere so that setting up quota does not load the server so much, especially storage when duplicating the template disk?
I assume you refer to the process (qemu-img) that clones the disks, right? Did you consider changing the storage allocation to "thin" instead of "clone"?
_______________________________________________ Users mailing list -- users@ovirt.org To unsubscribe send an email to users-leave@ovirt.org Privacy Statement: https://www.ovirt.org/privacy-policy.html oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/2PO6CSPZN6N4E2...

Hi, no, we don't use bit cloning via "clone" function, but we use templates as a raw format template. When creating a VM through this template, the server load will increase a lot. We want to minimize this sharp increase during the establishment. We are willing to wait longer to set up the server.

On Mon, Apr 26, 2021 at 12:36 PM <ovirt.org@nevim.eu> wrote:
Hi, no, we don't use bit cloning via "clone" function, but we use templates as a raw format template.
When creating a VM through this template, the server load will increase a lot.
We want to minimize this sharp increase during the establishment. We are willing to wait longer to set up the server.
Try what Arik suggested: Open VM > Resource Allocation tab Set "Storage Allocation" to "Thin" This will create create an empty qcow2 image using the template disk as a backing file. No data will be copied when creating the VM. But note that this creates a dependency on the template. You will not be able to move the disk to another storage domain without copying the template to the other storage domain. This also creates a single point of failure - if the template become corrupted all the vm on top of it will break. Nir
participants (3)
-
Arik Hadas
-
Nir Soffer
-
ovirt.org@nevim.eu