Difference between revisions of "Virsh start"

From wikieduonline
Jump to navigation Jump to search
 
(10 intermediate revisions by the same user not shown)
Line 4: Line 4:
 
</pre>
 
</pre>
  
 +
virsh start VM_MACHINE_NAME --console
  
<pre>
+
virsh --connect qemu:///system start  VM_MACHINE_NAME
virsh start VM_MACHINE_NAME --console
 
</pre>
 
  
<code>virsh --connect qemu:///system start  VM_MACHINE_NAME</code>
 
  
 +
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 commands:
+
== Related terms ==
 
* <code>[[virsh --connect]]</code>
 
* <code>[[virsh --connect]]</code>
 
* <code>[[virt-install]]</code>
 
* <code>[[virt-install]]</code>
 
* <code>[[virsh console]]</code>
 
* <code>[[virsh console]]</code>
 +
* <code>[[virsh net-start]]</code> and <code>[[virsh pool-start]]</code>
 +
* <code>[[virsh autostart]]</code>
 +
* <code>[[virsh define]]</code>
 +
* Logs: <code>/var/log/libvirt/[[qemu]]</code>
 +
* [[Docker]]: [[Start configuration behavior and restart policy]]
  
 
== See also ==
 
== See also ==

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]

See also[edit]

Advertising: