Difference between revisions of "Virsh dumpxml"
Jump to navigation
Jump to search
↑ https://libvirt.org/sources/virshcmdref/html-single/#sect-dumpxml
↑ https://linux.die.net/man/1/virsh
↑ https://linux.die.net/man/1/virsh
↑ https://serverfault.com/questions/434064/correct-way-to-move-kvm-vm
↑ https://wiki.libvirt.org/page/Live-disk-backup-with-active-blockcommit
Line 20: | Line 20: | ||
*{{KVM}} | *{{KVM}} | ||
− | [[Category:Linux] | + | [[Category:Linux]] |
− | [[Category:KVM] | + | [[Category:KVM]] |
Revision as of 04:43, 7 January 2020
virsh dumpxml[1] {guest-id, VM_MACHINE_NAME or uuid}
[--inactive] [--security-info] [--update-cpu] [--migratable] [2]
--migratable
with --migratable one can request an XML that is suitable for migrations, i.e., compatible with older libvirt releases and possibly amended with internal run-time options. This option may automatically enable other options (--update-cpu, --security-info, ...) as necessary[3]
Activities
- Offline Migrate or move a virtual machine between two KVM servers without shared storage[4]:
virsh dumpxml
andvirsh define
- Create Live backups with active virsh blockcommit[5]
See also
See also
- 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
Advertising: