Difference between revisions of "Virsh destroy"
Jump to navigation
Jump to search
(Created page with "Ungraceful Shutdown but do not destroy data or VM but you can corrupt guest file systems <pre> virsh destroy VM_MACHINE_NAME Domain infrastructure destroyed </pre> <pre> v...") |
|||
Line 30: | Line 30: | ||
== See also == | == See also == | ||
* {{virsh}} | * {{virsh}} | ||
+ | * {{virsh operations one line}} | ||
[[Category:Linux]] | [[Category:Linux]] | ||
[[Category:KVM]] | [[Category:KVM]] |
Revision as of 14:13, 5 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 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
Advertising: