Settings and activity
31 results found
-
7 votes
An error occurred while saving the comment -
4 votes
Brandon shared this idea ·
-
8 votes
An error occurred while saving the comment Brandon commented
SolusVM provided a patch to this problem which seems to have fixed the Windows template provisioning boot error in our initial testing. We are told development is evaluating for permanent fix.
Brandon supported this idea ·
-
18 votes
Brandon supported this idea ·
-
2 votes
Brandon supported this idea ·
An error occurred while saving the comment Brandon commented
It was confirmed with support that the libvirtd team will not fix the issue where KVM VPS do not start up with a configure delay from /etc/sysconfig/libvirt-guests and supposedly for backward compatibility reasons. Support said they would be pursuing development of a custom startup method by node.
I would also like to request a option be developed to easily allow a individual node to be set prevent VPS from auto starting. This would be helpful for maintenance updates when we may have to do multiple reboots and do not wish VPS to start until we are complete.
Example:
sed -i "s/startup=yes/startup=no/" /usr/local/solusvm/data/vps-startup.iniBrandon shared this idea ·
-
31 votes
Brandon supported this idea ·
-
10 votes
Brandon supported this idea ·
-
19 votes
Brandon supported this idea ·
-
66 votes
Brandon supported this idea ·
-
26 votes
Brandon supported this idea ·
-
4 votes
Brandon supported this idea ·
An error occurred while saving the comment Brandon commented
I requested something similar in ticket WBC-658874 for KVM custom cpu model xml but, i'd like it per template. In particular interested because of Windows 2016 requiring additional CPU flags than the default on CentOS6. CentOS7 interestingly offers more CPU features in the default XML and doesn't have this problem i found later.
Make this optional if implemented please. More complex passwords would be more difficult in VNC session.