Thank you Alex, I think it just clicked in my head what the core difference is. Reading again on the Internet, I got confused by the fact that ESX used a readhat kernel, but ESX doesn't actually run on it, but run under it after some "magic".
But you're right, the most important is that it feels bare-metal, and I am yet to see perf differences. Virtualbox just rocks :) And I totally agree with your P.S. on this one! Thanks a bunch for clearing this up for me. On 22 March 2013 09:22, Alexey Eromenko <[email protected]> wrote: > Hmm... > Type 1 means that the virtualization layer aka hypervisor sits below the > OS kernel. (VMware ESX/i, Xen, Hyper-V) > > Type 2 means that the virtualization layer aka hypervisor sits above the > OS kernel. (example KVM, VirtualBox) > There is no way in the world to change type. *but* there is a way to > optimize the O. S to bare-metal and server needs, so type 2 gives you > type1-like performance, features and user experience. RHEV (Red Hat > Enterprise Virtualization) does just that - it is a bare-metal minimal > Linux distro, but it is targeted at remote usage, like ESX with vSphere. > (it runs KVM, so it's type 2, but users think it is type 1) and it's > commercial. > > It is likely, that Oracle has bare metal commercial solution based on > minimal Linux and VirtualBox, known as Oracle VDI, but I haven't tried it. > > In short it does not matter if it works above or below the kernel, and > there is no proof, that type 1 is any faster than type 2. Making the > solution that "feels" bare-metal is important, and can be done with either > type. > > Example : the Open Stack cloud is absolutely server-targetted, and guess > what? It supports both Xen (type 1) and KVM (type 2) hypervisors. (adding > VirtualBox to OpenStack is possible, if anyone volunteers to maintain the > Open Stack-vbox driver) > > P. S: Hell, we must beat the "hype" part from the hypervisor. > > -Alexey Eromenko "Technologov" > Sent from Galaxy S III > > _______________________________________________ > vbox-dev mailing list > [email protected] > https://www.virtualbox.org/mailman/listinfo/vbox-dev > >
_______________________________________________ vbox-dev mailing list [email protected] https://www.virtualbox.org/mailman/listinfo/vbox-dev
