Virsh destroy

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)

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 domblklist output 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

• virsh: Storage information, Connecting, Operations, Memory, Snapshots, Networking, CPU, release notes, virsh nodedev-list
• Changing VM running status operations: start, shutdown, destroy, reboot, reset, resume