Device Pathway to Virtualization
To Virtualization

        2Virt is an open source initiative to guide new developers to using the hypervisors available on today's market.
This site is meant to be a tutorial on the few step required to virtualize your current desktop computer, as well as creating a source environment for building the virtualization solution from scratch.
Please check out the Xen Blog area to see my development experience using the Xen hypervisor.

        To leverage the full power of the virtualization platform services across unpriviledged guest virtual machines, 2Virt offers developers and system administrators alike a special class of emulated 2Virt devices.

        The common cloud infrastructure has a semnificant arhitectural design issue expecially when accessing protected services stored in priviledged domains from guest virtual machines, as well as handling the interconection policy of the guest virtual machines found at different security levels.
        The old interconnection setup relied on configuring virtual Ethernet network interfaces forwarded to a real interface, as well as dedicated network administration - private/public networks, firewall rules, NAT-ing and other. In order to configure a safe cloud infrastructure a lot of setup was required at different Ethernet layers in priviledged domains. A typical example was providing a web service platform for an unsecure Hardware Virtual Machine guest to enable accessing the virtualization platform services, such as creating a new virtual machine, migrating and much more.

        2Virt devices can be used to interconnect the guest machines on your virtualization platform, in a secure manner allowing few to none administration requirements. The setup is easier to maintain, offer a PnP USB design, and are oriented to offering dedicated services to a virtual machine, not just a communication pathway as in the classic Ethernet design. The USB architecture enables the virtualization platform to add/remove any service offered to a guest machine at any time.
        Although this project does not want to completly replace the Ethernet network between the virtual machines we believe that this architecture is much better suited for a specific class of services, many of them relating to accesing the virtualization platform capabilities from unsecure guests, such as is done in a cloud infrastructure.



To VirtualizationDevice 2VirtPersonal InformationBlog