| Div | ||
|---|---|---|
| ||
|
Description
...
| Table of Contents |
|---|
After deleting VMs in the UNKNOWN state, more checks of the host machine may be required. Virtual machines VMs may be put in into the UNKNOWN state if there is an issue with a connection to the hypervisor. A virtual machine that is in the UNKNOWN state has a blue indicator with a question mark.
In Abiquo 2.4, any user can delete their machine in this state and These VMs are marked as UNKNOWN.
If a user deletes a VM in this state, then it could remain in the hypervisor . Therefore, the delete should only be performed by an authorized user who can check the hypervisor to ensure that the virtual machine has been fully destroyed. Otherwise the but it would not be registered on the platform. So the information in Abiquo may not be consistent with the state of the hypervisor and problems could occur. For example, if the user then redeploys their virtual appliance, this would create another virtual machine VM on the hypervisor. So there would be two different virtual machines with the same name using the same external disk.
Specifications
...
| class | privileg |
|---|
In Abiquo 2.6 the (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 improves platform stability by enabling greater control over situations such as minor communication failures between the hypervisor and Abiquo.
Limitations
No limitations to note for this feature.