FVM

An OS level virtualization technique
Download

FVM Ranking & Summary

Advertisement

  • Rating:
  • License:
  • GPL
  • Publisher Name:
  • Rether Networks Inc
  • Operating Systems:
  • Windows 2K / XP
  • File Size:
  • 1.8 MB

FVM Tags


FVM Description

The name FVM stands for Featherweight Virtual Machine. FVM is an OS level virtualization technique akin to Solaris zones/Linux vserver on Windows Most current day virtualization technologies support virtualization at an abstraction level close to hardware and are heavyweight in that each Virtual Machine (VM) is created as a full-fledged operating environment. Initializing such a VM incurs too much overhead in terms of both disk space and invocation latency. Featherweight Virtual Machine (FVM) is an OS-level virtual machine technology that creates one or multiple execution environments on a single physical machine. Different from hardware-level virtual machine technologies, OS-level virtual machine technologies like FVM have the virtualization layer between the operating system and application programs. The virtualization layer can be designed in a way that allows processes in VMs to access as many resources of the host machine as possible through a special copy on write scheme, but never to tamper with them. In other words, every VM shares the same execution environment as the host machine, and only keeps any diverges from the host environment in the VM's local state. Therefore, such a VM can have very small resource requirement and thus can achieve large scalability. Each VM represents a distinct instance of the underlying physical machine, and does not interfere with one another or with the underlying machine. This isolation property makes FVM a possible building block for security and fault-tolerant applications. For example, running unsafe mobile code in a VM can protect the underlying physical machine from being compromised. To prevent denial-of-service attacks and also support performance isolation, a set of policies regarding resource quota and network access can be specified when a VM is created. The FVM layer limits the total system resource allocated to the VM according to these policies. This is achieved by assigning a Windows job object to the VM, initializing the job object with the policy settings for things like CPU scheduling priority, physical memory limit, working set size, process execution time, etc. Moreover, under this architecture, it is also possible for the VM and the host machine to synchronize state changes conveniently when necessary. For example, the legitimate state change in a VM can be committed to the host machine, while patches or reconfiguration of the host machine can be synchronized immediately in a VM.


FVM Related Software