hypervisor.html
1 <!DOCTYPE html> 2 <html lang="de"> 3 <head> 4 <meta charset="UTF-8" /> 5 <meta name="viewport" content="width=device-width, initial-scale=1.0" /> 6 <meta http-equiv="onion-location" content="http://bopbopl6lohkl2rts3ltesjnag4hzs4jrx2h6k6etgq5xasbpqekzlqd.onion" /> 7 <title>BOP Wiki: Hypervisor</title> 8 <link rel="stylesheet" href="/assets/stylesheet.css" /> 9 <link rel="icon" type="image/x-icon" href="/assets/img/favicon.png"> 10 </head> 11 <body> 12 <header> 13 <!-- --------------------------------------------------------------------------------------------------------------------------------- --> 14 <script src="/assets/js/navbar-OpenClose.js"></script> 15 <script src="/assets/js/lightbox.js"></script> 16 <script src="/assets/js/copyCodeButton.js"></script> 17 <link rel="stylesheet" href="/resources/js-libraries/highlightJS/atom-one-dark.min.css"> 18 <script src="/resources/js-libraries/highlightJS/highlight.min.js"></script> 19 <script src="/resources/js-libraries/highlightJS/highlightjs-line-numbers.min.js"></script> 20 <script>hljs.highlightAll();</script> 21 <script>hljs.initLineNumbersOnLoad();</script> 22 <!-- --------------------------------------------------------------------------------------------------------------------------------- --> 23 <div class="branding"> 24 <button class="toggle-btn-navbar" id="navbarOpenButton">☰</button> 25 <a href="/"> 26 <img class="logo" src="/assets/img/logo.png"> 27 </a> 28 <div class="typing-animation">BytesOfProgress</div> 29 </div> 30 </header> 31 <div id="navbarContainer" class="navbar-container"> 32 <iframe class="navbar-iframe" src="/assets/navbar/navbar.html" frameBorder= "0"></iframe> 33 </div> 34 <main> 35 <article class="blog-post"> 36 <header class="post-header"> 37 <h1 class="post-title">Hypervisor</h1> 38 </header> 39 </article> 40 <nav class="breadcrumb"> 41 <a href="/">Home</a> 42 <span class="divider">›</span> 43 <a href="/wiki/">Wiki</a> 44 <span class="divider">›</span> 45 <span class="current">Hypervisor</span> 46 </nav> 47 <section class="post-content"> 48 <table> 49 <thead> 50 <tr> 51 <th>Title</th> 52 <th>Description & Link</th> 53 </tr> 54 </thead> 55 <tbody> 56 <tr> 57 <td>Proxmox</td> 58 <td>A Type 1 Hypervisor.<br><a href="/wiki/hypervisor/proxmox/proxmox.html">Read more</a></td> 59 </tr> 60 <tr> 61 <td>VirtualBox</td> 62 <td>A Type 2 Hypervisor.<br><a href="/wiki/hypervisor/virtualbox/virtualbox.html">Read more</a></td> 63 </tr> 64 </tbody> 65 </table> 66 <p> 67 Hypervisors are the core technology behind virtualization. 68 They enable the creation of virtual machines, which are 69 self-contained computing environments that run on a single 70 physical machine. Hypervisors are a fundamental element 71 of cloud computing, data centers, and virtualized IT 72 environments, allowing for greater flexibility, resource 73 utilization, and scalability. In essence, they transform 74 a single computer into a platform for multiple virtual 75 machines, each running its own operating system and 76 applications. This makes it possible to efficiently use 77 the power of modern hardware while maintaining isolation and 78 security between virtualized environments. 79 </p> 80 <p> 81 Virtual machines (VMs) can be moved to different computers 82 with ease because they operate independently of the physical hardware. 83 They use virtualized hardware, which is the same across different computers. 84 VMs are like software packages with their own settings and data, 85 making them portable. This means you can transfer a VM from one computer 86 to another and run it as long as the new computer 87 supports the same virtualization technology. 88 </p> 89 <p>There are two types of Hypervisors:</p> 90 <h2>Type 1 Hypervisors: Bare-Metal Virtualization</h2> 91 <p> 92 Type 1 hypervisors have direct access to the host system's hardware, 93 including CPU, memory, and storage. This direct connection translates 94 to superior performance, making them a preferred choice for demanding 95 enterprise environments. They efficiently allocate physical resources 96 available to multiple virtual machines (VMs). This ensures that CPU 97 cores, memory, and storage are utilized optimally. 98 </p> 99 <p> 100 VMs running on Type 1 hypervisors are isolated from one another. 101 This isolation not only enhances security but also means that issues 102 within one VM do not apply to others. 103 Notable Type 1 hypervisors include VMware vSphere/ESXi, Microsoft 104 Hyper-V (when installed directly on hardware), and Proxmox. 105 They are used in various environments, from data centers to cloud 106 settings, where many essential tasks are performed. 107 </p> 108 <p> 109 In essence, Type 1 hypervisors stand at the forefront of server 110 virtualization, offering a robust and efficient way to create 111 and oversee virtual machines directly on the physical hardware. 112 They are commonly used in data centers and cloud environments 113 to host virtual machines that run critical workloads. 114 </p> 115 <h2>Type 2 Hypervisors: Virtualization on Your Computer</h2> 116 <p> 117 Type 2 hypervisors are a form of virtualization technology that allows 118 you to run multiple operating systems on a single computer. Unlike Type 1 119 hypervisors that run directly on the computer's hardware, Type 2 hypervisors 120 work on top of your regular operating system, like GNU/Linux, macOS, or Windows. 121 Once installed, they create a virtual environment where you can run 122 other operating systems. These virtual machines (VMs) are like separate, 123 isolated computers running within your main computer. 124 </p> 125 <p> 126 Type 2 hypervisors are often used for tasks like development, testing, 127 or running specific software that might not be compatible with your main 128 operating system. For example, if you're using a Mac but need to run a Windows 129 program, a Type 2 hypervisor lets you do that in a virtual Windows environment. 130 </p> 131 <p> 132 Popular examples of Type 2 hypervisors include Oracle VirtualBox, 133 VMware Workstation, and Parallels Desktop (for macOS). They are generally 134 user-friendly and don't require special hardware or complex setup. 135 You can allocate CPU, memory, and storage to each VM, and these VMs 136 are isolated from your main operating system, so if something goes 137 wrong in one VM, it usually won't affect your computer. 138 </p> 139 <p> 140 While Type 2 hypervisors are convenient for certain tasks, they may 141 introduce some performance loss compared to Type 1 hypervisors. 142 </p> 143 </section> 144 <footer class="post-footer"> 145 <a href="/wiki/" class="cta-button">← Back</a> 146 </footer> 147 </main> 148 </body> 149 </html>