6.0.1

Table Of Contents
VAIO Filter Framework
Virtual Machine
GuestOS
Filter 1
Filter 2
Filter N
I/O Path
vCenter Server
Virtual Disk
3rd Party
CIM Provider
3rd Party Web
Client Extension
Plugin
I/O Path
Each Virtual Machine Executable (VMX) component of a virtual machine contains a Filter Farmwork that
manages the I/O lter plug-ins aached to the virtual disk. The Filter Framework invokes lters when I/O
requests move between the guest operating system and the virtual disk. Also, any I/O access towards the
virtual disk that happens outside of a running VM is intercepted by the lter.
The lters execute sequentially in a specic order. For example, a replication lter executes before a cache
lter. More than one lter can lter the virtual disk, but only one for each category.
Once the I/O request has been ltered by all lters for the particular disk, the I/O request moves to its
destination, either the VM or the virtual disk.
Because the lters run in user space, any lter failures impact only the VM, but do not aect the ESXi host.
Storage Providers for VAIO Filters
After you install I/O lters and deploy them on ESXi hosts, the I/O lter framework congures and registers
a storage provider, also called a VASA provider, for each host in the cluster.
Storage providers for I/O ltering are software components that are oered by vSphere. They integrate with
I/O lters and report data service capabilities that I/O lters support to vCenter Server.
These data services become visible in the VM Storage Policies interface and can be referenced in a VM
policy. You then apply this policy to virtual disks, so that I/O for the disks can be processed by the lters.
Chapter 21 Filtering Virtual Machine I/O
VMware, Inc. 245