When we have multiple VLAN tagging interfaces, we suppose to create new bridge for each VLAN interfaces. So it would be better if SolusVM supports multiple bridges for KVM and Xen virtualization.1 vote
This would allow us to apply custom config to VPS on creation so we don't need to manually do it after the VPS is deployed.1 vote
Allow custom mac address assignment for IPv6 addresses. Some network providers require mac assignments for individual IPv6 addresses, and this currently requires manual work every time you want to assign an IPv6 to a KVM VM currently.
IPv6 and IPv4 should be allowed to be paired in this instance, since IPv4 and IPv6 mac address would need to be the same for the individual VM. If IPv6 have a custom mac address, and are assigned automatically, this could cause mix ups.1 vote
Hello. CDN support is very useful for svm user. It just needs few lines of code in config.php, and can show real ip in svm interface and nginx log instead of cdn's ip.2 votes
Would be useful having more hooks, for example on VM deletion and suspension/unsuspension3 votes
Please add console and serial to the autogenerated config so that admins can use
virsh console vpsname
Solus uses KVM as backend and should not limit its features.
Currently one gets greeted with
error: internal error: cannot find character device <null>
Placing full XML config that includes serial and console in every VPS via Solus web panel to overcome this limitation is awkward.2 votes
Add a configuration to the slaves configuration page that allows you to suspend VMs that exceed a certain level of load and leave the choice for the admin to choose the action (suspend or reboot or shut down the VM.4 votes
Currently the only way to enable quick backup for containers is to run the script in the solusvm DOCS occasionally however this really should be enabled at the point of container creation.
Please consider updating SolusVM to incorporate that.7 votes
The function has already been implemented and works great however for many of us with multiple PoP's the option to set this on/off on a per node basis would be a significant improvement, in Europe and the USA Bandwidth use is rarely a concern however in Asia Pacific regions this could get incredibly costly.
Currently it is global for all slaves/nodes regardless of location and it would allow us to give a much better and fitting service to customers if we could chose which nodes this applies too.5 votes
- Don't see your idea?