Solusvm Module Kvm

[Virtovo]

Hi all,

 

It seems the Blesta SolusVM module on our installation does not set a root password initially (or if it does it is incorrect).  When trying to perform the password action with Blesta for the module it says the data was submitted successfully but performs no reset. 

 

The Blesta module displays RAM/Disk usage for KVM services, despite these metrics not being exposed.

 

Is this normal behaviour?  If so is there a way to fix any of these issues?  Are there any other KVM limitations I should be aware of?

[Virtovo]

I didn't receive a PM regarding a testing environment so have looked to a solution elsewhere.

[Tyson]

Do your Module Logs show any input/output related to the password reset request? A successful response indicates that the reset was performed on the server.

 

Stats are always displayed, whether specific values exist for them or not.

 

You can take a look at the SolusVM documentation for more specifics on the module, such as welcome email tags and the use of the VNC console.

[Michael]

Be careful that no symbols are added in the password, if there is SolusVM will reject it whether successful or not, I hate SolusVM for that reason and use passwd command on SSH.

[Virtovo]

The error reported on the password reset is:

 

<status>error</status><statusmsg>Not supported for this virtualization type</statusmsg>

 

This is not true any longer and SolusVM does indeed offer password resets from the admin side and has most recently included them also from the client side in the latest beta.

 

Regardless if the password reset is not supported for KVM via the API/Module then this should not be exposed to the client and definitely should report success as it is very confusing to clients and causes undue frustration.  The same issues pertains to RAM/CPU metrics.  It would be far better to not show these metrics when the virtualisation type is KVM as reporting nothing leads people to believe that functionality is broken.

 

Is it possible to add checks to the module for the virtualisation type and enable/disable those features that do not work with that type? 

[Tyson]

Yes, we would like to improve the module to have better support for KVM/HVM, but we currently lack a testing environment for those virtualization types.

[Virtovo]

Yes, we would like to improve the module to have better support for KVM/HVM, but we currently lack a testing environment for those virtualization types.

 

If you wish to send a PM of your requirements I'm happy to oblige.