Difference between revisions of "Virsh destroy"
Jump to navigation
Jump to search
| Line 18: | Line 18: | ||
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) | ||
</pre> | </pre> | ||
| − | * Review your log files: <code>/var/log/libvirt/qemu/</code>, <code>[[ | + | * Review your log files: <code>/var/log/libvirt/qemu/</code>, <code>[[virsh domblklist]]</code> output and try to restart [[libvirtd]]: <code>systemctl restart [[libvirtd]]</code> |
Revision as of 04:25, 7 January 2020
Ungraceful Shutdown but do not destroy data or VM but you can corrupt guest file systems
virsh destroy VM_MACHINE_NAME Domain infrastructure destroyed
virsh destroy VM_MACHINE_NAME --graceful
- 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)
- 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
See also
Advertising:
