this document to jump right in.
an XML change to make. actions are one of:
XML block –build-xml: Just build the requested XML block and print it (no domain or input XML are required here).
configuration, add the –update option (but not all options/devices support updating the running VM configuration).
XML option that is passed to virt-xml. So if –disk is passed, EDIT-OPTIONS select which <disk> block to edit.
cases, virt-xml will not complain if a corresponding XML block does not already exist, it will create it for you.
being edited before applying the requested changes. This allows completely rebuilding an XML block. See EXAMPLES for some usage.
applies for device XML.
only really applies for device XML.
the XML option.
block and add it to the XML.
format as –edit. Examples
DISK-OPTIONS’ will just print the new <disk> device.
actions’ will imply a default output action, described in detail above. These are only needed if you want to modify the default
operation. If combined with –add-device, this is a device hotplug. If combined with –remove-device, this is a device hotunplug.
specified, –define is required to force the change.
disabled and no persistent change is made.
persistent change is made.
used with ‘–option opt=,’, so to clear a disks cache setting you could use ‘–disk cache=,’
Virtualization hosts supported by libvirt may not permit all changes that might seem possible. Some edits made to a VM’s definition may be ignored. For instance, QEMU does not allow the removal of certain devices once they’ve been defined.
the project website http://virt-manager.org
- man 1 virt-xml, Version 11.5.1-1
- 08/22/2018 创建文章