160 likes | 276 Views
Virtualization. A Discussion. Used Since1960’s starting with IBM System/360 Grown in acceptance and usage by non Mainframe or “Big Iron” Environments only in recent years Early adopters of Virtualization in smaller environments used primarily for testing and development purposes initially.
E N D
Virtualization A Discussion
Used Since1960’s starting with IBM System/360 • Grown in acceptance and usage by non Mainframe or “Big Iron” Environments only in recent years • Early adopters of Virtualization in smaller environments used primarily for testing and development purposes initially. • X86 Virtualization not available until 1999 When VMWare launched VMWareVirtual Platform History
Virtualization Actually Creates a underlying Hardware platform to run an Operating System on. • Emulation mimics another platform on a non-native platform • Virtualization uses emulation Virtualizationvs.Emulation
Better hardware efficiency • Security • Stability • Cost Effective* Why Virtualize?
Mainframe • Servers (X86, PowerPC, Sparc, etc…) • Workstations, Desktops, Laptops (X86) • Mobile (Smart phones, etc…) Platforms
Type I • Type II • Type 0? • Application Types of Virtualization
Hypervisor runs directly on underlying hardware and all Operating Systems run on top of it, including any “Control” Operating systems with special permissions. • Usually Micro Kernel based • Typically includes: ESX, Hyper-V, XEN, KVM(Macro Kernel) Type I
Hypervisor runs on top of an existing host Operating System as a standard application process. • Traditionally all Hardware Emulated • Typically includes: VMWare Workstation, GSX, VMWare Player, VirtualBox, Parralells Type II
An unmanaged Hypervisor • Really nothing more than a subset of Type I (Which doesn’t really exist) • The more you know, the more it looks like something from the marketing department Type 0
Really more like sandboxing an application than the other types of emulation listed • Less common, but becoming more so • Example Portable Apps Application
Faster • Designed to be more secure • Generally better centralized management tools for scaling • Headless Type I
Runs in user space • Slower due to hardware emulation • More likely to cause host system instability Type II