Difference between revisions of "Virsh destroy"
Jump to navigation
Jump to search
| Line 7: | Line 7: | ||
* Error while destroying VM_MACHINE: | * Error while destroying VM_MACHINE: | ||
| − | + | ||
| − | virsh destroy VM_MACHINE_NAME | + | virsh destroy VM_MACHINE_NAME |
| − | error: Failed to destroy domain VM_MACHINE_NAME | + | error: Failed to destroy domain VM_MACHINE_NAME |
| − | error: Timed out during operation: cannot acquire state change lock (held by [[remoteDispatchDomainBlockJobAbort]]) | + | error: Timed out during operation: cannot acquire state change lock (held by [[remoteDispatchDomainBlockJobAbort]]) |
| − | + | ||
virsh destroy VM_MACHINE_NAME-3 | virsh destroy VM_MACHINE_NAME-3 | ||
Revision as of 07:01, 9 August 2020
Ungraceful shutdown but do not destroy data or VM but you can corrupt guest file systems, --graceful flag attempts to flush the cache for the disk image file before powering off the virtual machine.
virsh destroy --graceful VM_MACHINE_NAME
virsh destroy VM_MACHINE_NAME Domain infrastructure destroyed
- Error while destroying VM_MACHINE:
virsh destroy VM_MACHINE_NAME error: Failed to destroy domain VM_MACHINE_NAME error: Timed out during operation: cannot acquire state change lock (held by remoteDispatchDomainBlockJobAbort)
virsh destroy VM_MACHINE_NAME-3 error: Disconnected from qemu:///system due to keepalive timeout error: Failed to destroy domain VM_MACHINE_NAME-3 error: internal error: connection closed due to keepalive timeout
- Review your log files:
/var/log/libvirt/qemu/,virsh domblklistoutput and try to restart libvirtd:systemctl restart libvirtd
- Logs:
/var/log/libvirt/qemu
VM_MACHINE.log:2019-04-18 07:53:30.584+0000: shutting down, reason=shutdown VM_MACHINE.log:2018-11-20 07:58:56.193+0000: shutting down, reason=crashed VM_MACHINE.log:2018-11-20 08:00:38.835+0000: shutting down, reason=destroyed
Related terms
virsh shutdown VM_NAMEvirsh undefine
See also
Advertising:
