
Parameter Name | Description | Type |
|
|
|
managed | true if the VDI is managed | read only |
|
|
|
data to be inserted into the xenstore | read only map parameter | |
| tree (/local/domain/0/backend/ |
|
|
| |
| data) after the VDI is attached. This is |
|
| generally set by the SM backends on |
|
| vdi_attach. |
|
|
|
|
SM dependent data | read only map parameter | |
|
|
|
true if this VDI is a VM storage snapshot | read only | |
|
|
|
snapshot_of | the UUID of the storage this VDI is a | read only |
| snapshot of |
|
|
|
|
snapshots | the UUID(s) of all snapshots of this VDI | read only |
|
|
|
snapshot_time | the timestamp of the snapshot operation | read only |
| that created this VDI |
|
|
|
|
vdi-clone
vdi-clone uuid=<uuid_of_the_vdi> [driver-params:<key=value>]
Create a new, writable copy of the specified VDI that can be used directly. It is a variant of
The optional
vdi-copy
Copy a VDI to a specified SR.
vdi-create
type=<system user suspend crashdump>
Create a VDI.
The
Note:
SR types that support sparse allocation of disks (such as Local VHD and NFS) do not enforce virtual allocation of disks. Users should therefore take great care when