Difference between revisions of "Virsh domblklist"
Jump to navigation
Jump to search
↑ https://linux.die.net/man/1/virsh
Line 35: | Line 35: | ||
== See also == | == See also == | ||
+ | * {{virsh}} | ||
* <code>[[virsh/virsh blockcommit|virsh blockcommit]]</code> | * <code>[[virsh/virsh blockcommit|virsh blockcommit]]</code> | ||
* <code>[[Virsh/virsh snapshot-list|virsh snapshot-list]] VM_MACHINE_NAME</code> | * <code>[[Virsh/virsh snapshot-list|virsh snapshot-list]] VM_MACHINE_NAME</code> |
Revision as of 10:10, 2 January 2020
virsh domblklist domain [--inactive] [--details]
[1]
Print a table showing the brief information of all block devices associated with domain. If --inactive is specified, query the block devices that will be used on the next boot, rather than those currently in use by a running domain. If --details is specified, disk type and device value will also be printed. Other contexts that require a block device name (such as domblkinfo or snapshot-create for disk snapshots) will accept either target or unique source names printed by this command.
$ virsh domblklist VM1_NAME Target Source ------------------------------------------------ vda /export/images/base.img
$ virsh domblklist VM2_NAME Target Source ------------------------------------------------ vda /export/images/base-root.qcow2 vdb /export/images/base-data.qcow2
$ virsh domblklist VM2_NAME --details Type Device Target Source ------------------------------------------------ file disk vda /export/images/base-root.qcow2 file cdrom vdb /export/images/base-data.qcow2
List for all VM Machines:
for VM in `virsh list --name`; do virsh domblklist $VM --details; done
See also
virsh
: Storage information, Connecting, Operations, Memory, Snapshots, Networking, CPU, release notes,virsh nodedev-list
virsh blockcommit
virsh snapshot-list VM_MACHINE_NAME
virsh destroy
,libvirtd
andvirsh console
- Virsh/Virsh Storage Information
- Virsh/Create Live backups
Advertising: