Table of Contents |
---|
After deleting VMs in the UNKNOWN state, more checks of the host machine may be required. VMs may be put The platform may put VMs into the UNKNOWN state if there is an issue with a connection to the hypervisor. These VMs are marked as UNKNOWNIt marks these VMs with the gray UNKNOWN state label.
...
If the platform later recovers the connection to the hypervisor, it will restore the VMs to their corresponding state.
A user may see a VM in an UNKNOWN state and wish to delete it but this action is protected by a privilege because after you delete the VM, you may also need to check the host machine.
Panel |
---|
Privileges: Delete unknown virtual machine |
In addition, if the VM is in another enterprise, you will need the privilege to Allow user to switch enterprise or you will need to log in to the enterprise.
If you do not check the hypervisor after deleting the VM in the platform, the VM may remain in the hypervisor without being registered in the platform. If the information in the platform and in the hypervisor are not consistent, then this may lead to errors or problems.
For example, if the user then redeploys their virtual appliance, deletes a persistent VM in an unknown state, then the persistent template will be available to the user. If the user deploys the VM again, then this would create another VM on the hypervisor . So there would be two different virtual machines with the same name using the same external disk(s).
Therefore, the delete should only be performed by an authorized user who can check the hypervisor to ensure that the VM has been fully destroyed.
Panel |
---|
Privilege: Delete unknown virtual machine |
The "Delete unknown virtual machine" privilege controls whether users can delete virtual machines in an UNKNOWN state. This privilege is displayed in the virtual appliance privileges section. In addition, if the user is in a different enterprise, they will require the privilege to administer all enterprises.
This feature enables customers to ensure that information in Abiquo is consistent with the state of the hypervisor. It disks as the original VM.
This feature improves platform stability by enabling greater control over situations such as minor communication failures between the hypervisor and Abiquothe platform.