Difference between revisions of "Virsh start"
Jump to navigation
Jump to search
| (One intermediate revision by the same user not shown) | |||
| Line 7: | Line 7: | ||
virsh --connect qemu:///system start VM_MACHINE_NAME | virsh --connect qemu:///system start VM_MACHINE_NAME | ||
| + | |||
| + | |||
| + | error: internal error: process exited while connecting to monitor: 2020-09-24T09:20:37.260753Z qemu-system-x86_64: -blockdev {"node-name":"libvirt-1-format","read-only":false,"driver":"[[qcow2]]","file":"libvirt-1-storage","backing":null}: Failed to get "write" lock | ||
| + | Solution: use <code>[[lsof]]</code> or <code>[[fuser]]</code> and verify you do not have storage device duplicated in xml vm definition file. | ||
== Related terms == | == Related terms == | ||
Latest revision as of 09:37, 24 September 2020
virsh start VM_MACHINE_NAME Domain VM_MACHINE_NAME started
virsh start VM_MACHINE_NAME --console
virsh --connect qemu:///system start VM_MACHINE_NAME
error: internal error: process exited while connecting to monitor: 2020-09-24T09:20:37.260753Z qemu-system-x86_64: -blockdev {"node-name":"libvirt-1-format","read-only":false,"driver":"qcow2","file":"libvirt-1-storage","backing":null}: Failed to get "write" lock
Solution: use lsof or fuser and verify you do not have storage device duplicated in xml vm definition file.
Related terms[edit]
virsh --connectvirt-installvirsh consolevirsh net-startandvirsh pool-startvirsh autostartvirsh define- Logs:
/var/log/libvirt/qemu - Docker: Start configuration behavior and restart policy
See also[edit]
- KVM, Installation, QEMU,
virsh,virtinst,libguestfs-tools, libvirt, qemu, Red Hat Virtualization (RHV), MacVTap, Virtio, oVirt, KVM services, KVM networking, KVM graphics, CPU, KVM on ARM 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
Advertising:
