
Parameter Name | Description | Type | |
|
|
|
|
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 snapshot | read only | |
| 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 |
| |
|
|
| |
the uuid of the pool which created this | read only | ||
| metadata VDI |
| |
|
|
| |
flag indicating whether the VDI contains the | read only | ||
| latest known metadata for this pool |
| |
|
|
|
|
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:
162