This is a long-standing issue we are experiencing with Virtualizor KVM.
We already have an email thread opened with Softaculous support but we feel we are the only ones experiencing this issue hence opening this thread for the rest of community to post their feedback.
Since maybe May or June 2025, after updating our Virtualizors to one of the stable versions released back then, we started encountering problem with creating VPSs. The error was the "disk resize failed".
We tried HUNDREDS of suggestions that Softaculous mentioned to us - even switched all our virtualizors to the so-called "new vps provisioning method". The problem exists.
We have a person working full-time for this issue as the support from Softaculous team is quite slow and this is a critical matter to us.
What we believe is happening is:
On virtualizors where we have large storage added (e.g. 8 TB SSD), and we try to create VPS with large storage (e.g. more than 1 or 2 TB), the issue immediately comes up. The "addvs" process gets hang with "D" state. So we need to restart the Virtualizor for the process to be cleaned.
Once we restart the Virtualizor, a workaround we found is that we can create a VPS with 50 GB Storage and then we edit the VPS to add additional storage.
This is is however not a proper solution for production Virtualizors.
Please share your thoughts if anyone else experiences the same.