Difference between revisions of "Virsh dumpxml"

From wikieduonline
Jump to navigation Jump to search
Line 15: Line 15:
  
 
== Related commands ==
 
== Related commands ==
* <code>[[virsh define]]</code>
+
* <code>[[virsh define]] YOU_VM_NAME.xml</code>
 
* <code>[[virsh dominfo]]</code>
 
* <code>[[virsh dominfo]]</code>
 
* <code>[[virsh domrename]]</code>
 
* <code>[[virsh domrename]]</code>

Revision as of 05:24, 2 February 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]


virsh dumpxml MACHINE_NAME > /path/to/savefile.xml

Activities

  1. Offline Migrate or move a virtual machine between two KVM servers without shared storage[4]: virsh dumpxml and virsh define
  1. Create Live backups with active virsh blockcommit[5]
  1. Dump config for all running machines: for NAME in `virsh list --name`; do virsh dumpxml $NAME > $NAME.xml; done

Related commands

See also

  • 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
  • Advertising: