Filter
Top Products
163
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-allocated SR does become full, disk space must be made
available either on the SR target substrate or by deleting unused VDIs in the SR.
Note:
Some SR types might round up the virtual-size value to make it divisible by a configured
block size.
vdi-destroy
vdi-destroy uuid=<uuid_of_vdi>
Destroy the specified VDI.
Note:
In the case of Local VHD and NFS SR types, disk space is not immediately released on vdi-
destroy, but periodically during a storage repository scan operation. Users that need to force
deleted disk space to be made available should call sr-scan manually.
vdi-forget
vdi-forget uuid=<uuid_of_vdi>
Unconditionally removes a VDI record from the database without touching the storage backend. In normal
operation, you should be using vdi-destroy instead.
vdi-import
vdi-import uuid=<uuid_of_vdi> filename=<filename_of_raw_vdi>
Import a raw VDI.
vdi-introduce
vdi-introduce uuid=<uuid_of_vdi>
sr-uuid=<uuid_of_sr_to_import_into>
name-label=<name_of_the_new_vdi>
type=<system | user | suspend | crashdump>
location=<device_location_(varies_by_storage_type)>
[name-description=<description_of_vdi>]
[sharable=<yes | no>]
[read-only=<yes | no>]
[other-config=<map_to_store_misc_user_specific_data>]
[xenstore-data=<map_to_of_additional_xenstore_keys>]
[sm-config<storage_specific_configuration_data>]
Create a VDI object representing an existing storage device, without actually modifying or creating any storage.
This command is primarily used internally to automatically introduce hot-plugged storage devices.
vdi-resize
vdi-resize uuid=<vdi_uuid> disk-size=<new_size_for_disk>
Resize the VDI specified by UUID.