Difference between revisions of "Virsh reboot"
Tags: Mobile web edit, Mobile edit |
|||
| (3 intermediate revisions by the same user not shown) | |||
| Line 16: | Line 16: | ||
The order in which drivers will try each mode is undefined, and not related to the order specified to virsh. For strict control over ordering, use a single mode at a time and repeat the command. | The order in which drivers will try each mode is undefined, and not related to the order specified to virsh. For strict control over ordering, use a single mode at a time and repeat the command. | ||
| − | |||
| − | |||
| − | |||
| − | + | virsh reboot VM_NAME | |
| − | Domain VM_NAME is being rebooted | + | Domain VM_NAME is being rebooted |
| − | + | virsh reboot VM_NAME --mode [[acpi]] | |
| − | + | Domain VM_NAME is being rebooted | |
| − | |||
| − | |||
| + | virsh reboot VM_NAME --mode signal # signal reboot doesn't work for me | ||
| + | error: Failed to reboot domain fedora-27 | ||
| + | error: unsupported flags (0x8) in function qemuDomainReboot | ||
| + | |||
| + | virsh reboot VM_NAME | ||
| + | error: Failed to reboot domain VM_NAME | ||
| + | error: Timed out during operation: cannot acquire state change lock (held by [[remoteDispatchDomainBlockJobAbort]]) | ||
| + | |||
| + | |||
| + | == Related commands == | ||
| + | * <code>[[virsh destroy]]</code> | ||
| + | * <code>[[virsh shutdown]]</code> | ||
== See also == | == See also == | ||
Latest revision as of 07:23, 9 August 2020
virsh reboot VM [--mode MODE-LIST] [1]
Reboot a domain. This acts just as if the domain had the reboot command run from the console. The command returns as soon as it has executed the reboot action, which may be significantly before the domain actually reboots.
The exact behavior of a domain when it reboots is set by the on_reboot parameter in the domain's XML definition.
By default the hypervisor will try to pick a suitable shutdown method. To specify an alternative method, the --mode parameter can specify a comma separated list which includes:
--mode
acpiagentinitctlsignalparavirt
The order in which drivers will try each mode is undefined, and not related to the order specified to virsh. For strict control over ordering, use a single mode at a time and repeat the command.
virsh reboot VM_NAME Domain VM_NAME is being rebooted
virsh reboot VM_NAME --mode acpi Domain VM_NAME is being rebooted
virsh reboot VM_NAME --mode signal # signal reboot doesn't work for me error: Failed to reboot domain fedora-27 error: unsupported flags (0x8) in function qemuDomainReboot
virsh reboot VM_NAME error: Failed to reboot domain VM_NAME error: Timed out during operation: cannot acquire state change lock (held by remoteDispatchDomainBlockJobAbort)
Related commands[edit]
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
See also[edit]
Advertising:
