Note that the files are left in the host to later boot the VM there. Same as suspended, but no checkpoint file is generated. Same as stopped, but the files are left in the host to later resume the VM there (i.e. VM state has been saved and it has been transferred back along with the disk images to the system datastore. If after a timeout period the VM does not disappear, OpenNebula will assume that the guest OS ignored the ACPI signal and the VM state will be changed to running, instead of done. OpenNebula has sent the VM the shutdown ACPI signal, and is waiting for it to complete the shutdown process. In this phase the system cleans up the Host used to virtualize the VM, and additionally disk images to be saved are copied back to the system datastore. The system is saving the VM files after a migration, stop or suspend operation. This can be a life migration or cold migration (the VM is saved, powered-off or powered-off hard and VM files are transferred to the new resource).Ī disk attach/detach, nic attach/detach operation is in process. The VM is migrating from one resource to another. In this state, the virtualization driver will periodically monitor it. The VM is running (note that this stage includes the internal virtualized machine booting and shutting down phases).
OpenNebula is waiting for the hypervisor to create the VM. The system is transferring the VM files (disk images and the recovery file) to the host in which the virtual machine will be running. The VM is waiting for one or more disk images to finish the initial copy to the repository (image state still in lock) The owner has held the VM and it will not be scheduled until it is released. It will stay in this state until the scheduler decides to deploy it, or the user deploys it using the onevm deploy command. If you are a developer you may want to take a look at the complete diagram referenced in the Virtual Machines States Reference guide):īy default a VM starts in the pending state, waiting for a resource to run on.
0 kommentar(er)
