VDIs are persistent, on-disk objects that exist independently of Citrix Hypervisor servers. The on-disk representation of the data differs by SR type. Physical block devices represent the interface between a physical server and an attached SR. PBDs are connector objects that allow a given SR to be mapped to a host. PBDs store the device configuration fields that are used to connect to and interact with a given storage target.
VDIs are represented as volumes within the volume manager and stored in VHD format to allow thin provisioning of reference nodes on snapshot and clone. You can opt to use raw at the time you create the VDI. This option can only be specified by using the xe CLI.
We recommend that you consider your security requirements before using this option. The sr-param-list and vdi-param-list xe commands can be used respectively for this purpose. Attach the new virtual disk to a VM. Use the disk tools within the VM to partition and format, or otherwise use the new disk. It is not possible to do a direct conversion between the raw and VHD formats. Instead, you can create a VDI either raw, as described above, or VHD and then copy data into it from an existing volume.
You can do this by checking its virtual-size field, for example by using the vdi-param-list command. For example, standard disk management tools in Windows or the dd command in Linux. If the new volume is a VHD volume, use a tool that can avoid writing empty sectors to the disk.
This action can ensure that space is used optimally in the underlying storage repository. A file-based copy approach may be more suitable. This feature allows such VMs to be quickly cloned from templates, facilitating very fast provisioning and deployment of new VMs. This coalescing process runs asynchronously. The amount of disk space reclaimed and time taken to perform the process depends on the size of the VDI and amount of shared data. The image file is automatically extended in fine granular chunks as the VM writes data into the disk.
However unused space on the underlying copy-on-write instance disk is reclaimed when a snapshot or clone occurs.
The difference between the two behaviors can be described in the following way:. For LVM-based VHD images , the difference disk nodes within the chain consume only as much data as has been written to disk. However, the leaf nodes VDI clones remain fully inflated to the virtual size of the disk. Snapshot leaf nodes VDI snapshots remain deflated when not in use and can be attached Read-only to preserve the deflated allocation.
Snapshot nodes that are attached Read-Write are fully inflated on attach, and deflated on detach. The leaf node files grow to accommodate data as it is actively written. Old blocks are directly read from the parent template.
If the new VM was converted into a further template and more VMs cloned, then the resulting chain results in degraded performance. Citrix Hypervisor supports a maximum chain length of Do not approach this limit without good reason. Only one coalescing process is ever active for an SR. This process thread runs on the SR master host. For more information, see Virtual disk QoS settings. The development, release and timing of any features or functionality described in the Preview documentation remains at our sole discretion and are subject to change without notice or consultation.
The documentation is for informational purposes only and is not a commitment, promise or legal obligation to deliver any material, code or functionality and should not be relied upon in making Citrix product purchase decisions. Citrix Hypervisor. View PDF. This content has been machine translated dynamically.
Publish content. Server VDI. User personalization layer. Remove components. Upgrade and migrate. Upgrade a deployment. Security considerations and best practices. Delegated administration. Manage security keys. Smart cards. Smart card deployments. Pass-through authentication and single sign-on with smart cards. App protection. Virtual channel security. Federated Authentication Service. Generic USB devices. Mobile and touch screen devices.
Serial ports. Specialty keyboards. TWAIN devices. WIA devices. HDX 3D Pro. Text-based session watermark. Audio features. Browser content redirection. HDX video conferencing and webcam video compression. HTML5 multimedia redirection. Optimization for Microsoft Teams. Monitor, troubleshoot, and support Microsoft Teams. Windows Media redirection. General content redirection. Client folder redirection. Host to client redirection. Generic USB redirection and client drive considerations.
Printing configuration example. Best practices, security considerations, and default operations. Printing policies and preferences. Provision printers. Maintain the printing environment. Work with policies. Policy templates. Create policies. Compare, prioritize, model, and troubleshoot policies. Default policy settings. Policy settings reference.
ICA policy settings. HDX features managed through the registry. Load management policy settings. Profile management policy settings. User personalization policy settings. Virtual Delivery Agent policy settings. Virtual IP policy settings.
Connector for Configuration Manager policy settings. Multi-type licensing. In VDI sites that include a hypervisor, the Delivery Controller uses it to deploy desktops, manage access, perform connection brokering, and manage load balancing of user sessions. The database must have a fast connection to the Controller.
Installed on every machine or VM that runs virtualized desktops or applications. VDA allows you to register a system with the controller. This makes the computer host-hosted resources available to users. VDA also verifies licenses and policies. The enterprise application store gives users self-service. A client application that users install on their devices—available either as a downloadable application, or as an HTML5 app that can be accessed over a web browser.
Allows the user to view and interact with a virtualized desktop or application as if it were running on their local device. It provides wizard-based controls for setting up the environment, provisioning resources to host desktops, assigning them to users, and managing Citrix licenses for VDI components.
Another administrative tool that enables IT staff to monitor the VDI site, identify and troubleshoot issues, and support end users experiencing problems with their virtualized desktops. In many Citrix environments, virtualization is managed by the Citrix hypervisor. The hypervisor manages virtual machines that run user desktops and applications. A Citrix VDI site can also run on hypervisors from other vendors. Citrix lets you choose between two support models for its VDI infrastructure:. Citrix recommends that organizations use the CR-supported model as new features may be introduced.
As many applications and platforms move to an update-based subscription-based model, more Citrix customers are moving to the CR model. VDI is a mission critical system that holds a lot of sensitive data.
0コメント