Hello, I understand the system's logic, I know how it works, and I've tested it. VMs is shaping up to be an application that will drive many people to buy TerraMaster. In other words, and to avoid calling it a bug, let's say it's a missing feature. This functionality is vital for using a hypervisor stably and comfortably. Every hypervisor has it. When the logic detects this excess storage, it should generate an alert and continue with the import process. It shouldn't stop the process or cause an import failure. If this functionality isn't included and expanded, the advantages of VMs will disappear, and with them, thousands of potential customers. I support the brand, and this comment is intended to help improve it. Therefore, you must include it. This way, thousands of professionals will be satisfied using TerraMaster.TMEmily wrote: ↑28 May 2026, 18:12Hello,The design logic of the VMs application is as follows: the virtual disk size declared in the virtual machine configuration file is treated by the system as the space that needs to be pre-allocated on the target storage (i.e., pre-allocated space). Therefore, when the available space on the target device (3TB) is less than the virtual disk size specified in the VM configuration (25TB), the system determines that there is insufficient space and blocks the import. This is the normal design behavior of the current version of VMs, not a system error.Nitrokalel wrote: ↑28 May 2026, 02:17You're correct, but you're also wrong. This function is essential for migrating multiple machines. Indeed, it is oversized, but this should trigger an alert, not stop the process. There should be an alert about the oversizing, not a validation. Or, this validation should be used to indicate that the machine is oversized but should still be allowed to be installed for operational reasons. This is a test, but in reality, it's a very useful function that should be included.MikeZhang wrote: ↑27 May 2026, 15:08
While thin-provisioned virtual disks may initially consume much less physical storage space than their configured logical capacity, the VM application currently validates disk allocation against the configured virtual disk size to help avoid potential storage overcommit situations.
If a VM with a 25 TB virtual disk is imported into a storage pool with only 3 TB of available capacity, future guest writes could eventually exhaust the physical storage space. In such cases, this may lead to VM instability, write failures, or possible data integrity risks.
The recommended approach is:
1. Modify the virtual disk size to a reasonable value during import (e.g., reconfigure it to 2 TB).
2. Alternatively, expand the physical storage first before importing, instead of forcibly importing a 25 TB configuration into a 3 TB environment.
Hola, entiendo la lógica del sistema, sé cómo funciona y lo he probado. Las máquinas virtuales se perfilan como una aplicación que impulsará a muchos usuarios a comprar TerraMaster. En otras palabras, y para evitar llamarlo error, digamos que es una funcionalidad faltante. Esta funcionalidad es vital para usar un hipervisor de forma estable y cómoda. Todos los hipervisores la tienen. Cuando la lógica detecta este exceso de almacenamiento, debería generar una alerta y continuar con el proceso de importación. No debería detener el proceso ni provocar un fallo en la importación. Si esta funcionalidad no se incluye y se amplía, las ventajas de las máquinas virtuales desaparecerán, y con ellas, miles de clientes potenciales. Apoyo la marca y este comentario pretende ayudar a mejorarla. Por lo tanto, deben incluirla. De esta forma, miles de profesionales estarán satisfechos con TerraMaster.
