Citrix Systems 5.6 manual Vdi-clone, Vdi-copy, Vdi-create, Tree /local/domain/0/backend

Parameter Name	Description	Type
managed	true if the VDI is managed	read only
xenstore-data	data to be inserted into the xenstore	read only map parameter
	tree (/local/domain/0/backend/
	vbd/<domid>/<device-id>/sm-
	data) after the VDI is attached. This is
	generally set by the SM backends on
	vdi_attach.
sm-config	SM dependent data	read only map parameter
is-a-snapshot	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-cloneuuid=<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 vdi-copythat is capable of exposing high-speed image clone facilities where they exist.

The optional driver-paramsmap parameter can be used for passing extra vendor-specific configuration information to the back end storage driver that the VDI is based on. See the storage vendor driver documentation for details.

vdi-copy

vdi-copyuuid=<uuid_of_the_vdi> sr-uuid=<uuid_of_the_destination_sr>

Copy a VDI to a specified SR.

vdi-create

vdi-createsr-uuid=<uuid_of_the_sr_where_you_want_to_create_the_vdi>name-label=<name_for_the_vdi>

type=<system user suspend crashdump> virtual-size=<size_of_virtual_disk>sm-config-*=<storage_specific_configuration_data>

Create a VDI.

The virtual-sizeparameter can be specified in bytes or using the IEC standard suffixes KiB (210 bytes), MiB (220 bytes), GiB (230 bytes), and TiB (240 bytes).

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 over-allocating virtual disk space on an SR. If an over-

190