Hi,
I'm posting my genuine worries and concerns about Virtualizor.
I switched from SolusVM earlier on this year to Virtualizor. and since then the Product has been nothing but a pain in the ass. And I'm not saying it to cause drama it's true.
Try having a Product that is poorly documented. or a product that has features but with no clear indication that if you have it setup a specific way. Your VMS will loose their data upon them being migrated across another node again not enough documentation. Not straight away this happens but months later when a client reboots their VPS. this is caused by the fact that if you use file based storage. their code does not support file based migrations.
My second major concern is that they release code that is buggy. their Multivirt Feature is completely useless. Random shutdown(s) occur. and all Virtualizor can do is blame it on a Hardware Issue?
2015-08-05 09:39:25.051+0000: 14820: error : qemuRemoveCgroup:781 : internal error Unable to find cgroup for v1002
2015-08-05 09:39:25.051+0000: 14820: error : qemuAutostartDomain:294 : Failed to autostart VM 'v1002': Unable to create cgroup for v1002: No such file or directory
2015-08-05 09:39:25.066+0000: 14820: error : virFileReadAll:462 : Failed to open file '/vz/root/743/sys/fs/cgroup/memory/libvirt/qemu/v1003/memory.use_hierarchy': No such file or directory
I allowed Virtualizor tech access to this machine weeks after originally reporting the error to them. All I got from them is that the issue is fixed please check. So I did. Everytime I install a new KVM VPS on this 1 specific node. it will shutdown the VM. How ever Yesterday I contact ed virtualizor again because another server where a couple of the VPS have been put during the past several weeks. is now not coping with the Load.
qemu: terminating on signal 15 from pid 822047
This error above appears everytime the VPS is shutdown. how ever I have over 7 + Licenses with Virtualizor. any of the Nodes not running Multivirt keep having the same exact error above unable to start VPS due to a cgroup error.
Oh and I forgot to mention if you have VPS running from a ISO if you ever use the stop/start function it can screw up the disk partitioning. Something I have never had a problem with. All I got from them again is backup your critical VMs ?