Editing Hypervisors
Jump to navigation
Jump to search
Warning: You are not logged in. Your IP address will be publicly visible if you make any edits. If you log in or create an account, your edits will be attributed to your username, along with other benefits.
The edit can be undone.
Please check the comparison below to verify that this is what you want to do, and then save the changes below to finish undoing the edit.
Latest revision | Your text | ||
Line 1: | Line 1: | ||
{{WIP}} | {{WIP}} | ||
− | A '''[[wikipedia:x86_virtualization|hypervisor]]''' is a program that takes advantage of an architectural quirk in | + | A '''[[wikipedia:x86_virtualization|hypervisor]]''' is a program that takes advantage of an architectural quirk in [[Intel CPUs]] to run emulated software at near-bare-metal speeds, running modern operating systems faster than emulators, but running video games slower than native hardware. This is possible because the processor is designed to execute code in a hierarchy that allows less-privileged software to run almost unmodified. For any instruction in a program that requests more privileges, such as those used by drivers, the hypervisor steps in to emulate the hardware response. There are two types of hypervisors; |
# A '''bare-metal hypervisor''', which is the operating system. | # A '''bare-metal hypervisor''', which is the operating system. | ||
# A '''software hypervisor''', the ones many are familiar with. They hook into the kernel of an existing operating system (such as Linux or Windows NT) and run alongside the rest of the software on the system. | # A '''software hypervisor''', the ones many are familiar with. They hook into the kernel of an existing operating system (such as Linux or Windows NT) and run alongside the rest of the software on the system. | ||
Hypervisors are the source of the "host" and "guest" terminology since they help clarify the specific "machine" one refers to; the host is the physical hardware and it manages the guests. Most hypervisors try and support the Open Virtualization Format (OVF) to facilitate virtual appliances which are built for a specific purpose (such as running common server software like WordPress or MediaWiki). | Hypervisors are the source of the "host" and "guest" terminology since they help clarify the specific "machine" one refers to; the host is the physical hardware and it manages the guests. Most hypervisors try and support the Open Virtualization Format (OVF) to facilitate virtual appliances which are built for a specific purpose (such as running common server software like WordPress or MediaWiki). | ||
− | |||
− | |||
==Type 2 hypervisors== | ==Type 2 hypervisors== | ||
Line 23: | Line 21: | ||
|align=left|{{Icon|Windows|Linux|macOS|FreeBSD}} | |align=left|{{Icon|Windows|Linux|macOS|FreeBSD}} | ||
|[https://www.qemu.org/download/ {{QEMUVer}}]<br/>[https://github.com/kjliew/qemu-3dfx qemu-3dfx ($)] | |[https://www.qemu.org/download/ {{QEMUVer}}]<br/>[https://github.com/kjliew/qemu-3dfx qemu-3dfx ($)] | ||
+ | |{{✓}} ||{{✓}} ||{{✓}} | ||
+ | |- | ||
+ | |[[VirtualBox]] | ||
+ | |align=left|{{Icon|Windows|Linux|macOS|FreeBSD|Solaris}} | ||
+ | |[https://www.virtualbox.org/wiki/Downloads {{VirtualBoxVer}}] | ||
|{{✓}} ||{{✓}} ||{{✓}} | |{{✓}} ||{{✓}} ||{{✓}} | ||
|- | |- | ||
|[[VMware Workstation]] | |[[VMware Workstation]] | ||
|align=left|{{Icon|Windows|Linux}} | |align=left|{{Icon|Windows|Linux}} | ||
− | | | + | |{{VMwareWorkstationVer}} |
|{{✗}} ||{{✓}} ||{{✓}} | |{{✗}} ||{{✓}} ||{{✓}} | ||
|- | |- | ||
Line 39: | Line 42: | ||
|18 | |18 | ||
|{{✗}} ||{{✓}} ||{{✓}} | |{{✗}} ||{{✓}} ||{{✓}} | ||
− | |||
− | |||
− | |||
− | |||
− | |||
|- | |- | ||
!colspan="6"|Mobile / ARM | !colspan="6"|Mobile / ARM | ||
|- | |- | ||
|UTM | |UTM | ||
− | |align=left|{{icon|macOS}} | + | |align=left|{{icon|macOS|iOS}} |
|[https://github.com/utmapp/UTM/releases {{UTMVer}}] | |[https://github.com/utmapp/UTM/releases {{UTMVer}}] | ||
− | |||
− | |||
− | |||
− | |||
− | |||
|{{✗}} ||{{✓}} ||{{?}} | |{{✗}} ||{{✓}} ||{{?}} | ||
|} | |} | ||
Line 71: | Line 64: | ||
;Virtual PC | ;Virtual PC | ||
:Microsoft's original offering for consumers, originally made by Connectix as commercial software until Microsoft made it a free download in 2006. Support ended with the introduction of Hyper-V but the last version can be downloaded [http://www.win3x.org/win3board/viewtopic.php?t=19227&language=en here]. Beware that it may cause issues on newer Windows so it's recommended that it's ran on older versions of Windows. As of modern updates of Windows 10 and Windows 11, it is completely impossible to use it. Hyper-V is the official successor, although it lacks support for guests before Windows XP or Windows Server 2003. | :Microsoft's original offering for consumers, originally made by Connectix as commercial software until Microsoft made it a free download in 2006. Support ended with the introduction of Hyper-V but the last version can be downloaded [http://www.win3x.org/win3board/viewtopic.php?t=19227&language=en here]. Beware that it may cause issues on newer Windows so it's recommended that it's ran on older versions of Windows. As of modern updates of Windows 10 and Windows 11, it is completely impossible to use it. Hyper-V is the official successor, although it lacks support for guests before Windows XP or Windows Server 2003. | ||
− | |||
− | |||
− | |||
==Type 1 hypervisors== | ==Type 1 hypervisors== | ||
Line 80: | Line 70: | ||
* ESXi (commercial hypervisor by VMware) | * ESXi (commercial hypervisor by VMware) | ||
* Xen (open-source hypervisor developed for the Linux kernel) | * Xen (open-source hypervisor developed for the Linux kernel) | ||
− | |||
* UnRAID (commercial NAS distribution with an integrated hypervisor) | * UnRAID (commercial NAS distribution with an integrated hypervisor) | ||
* Hyper-V (commercial hypervisor Microsoft developed for Windows. Requires a Pro, Enterprise, or Education version of Windows 8, 8.1, or 10) | * Hyper-V (commercial hypervisor Microsoft developed for Windows. Requires a Pro, Enterprise, or Education version of Windows 8, 8.1, or 10) | ||
Line 99: | Line 88: | ||
If you're using an NVIDIA card, you also need to configure how the graphics card appears to the VM so that NVIDIA's driver doesn't reject the card. | If you're using an NVIDIA card, you also need to configure how the graphics card appears to the VM so that NVIDIA's driver doesn't reject the card. | ||
− | + | ==Emulation issues== | |
− | |||
− | == | ||
− | |||
− | |||
− | |||
===Graphics=== | ===Graphics=== | ||
Hypervisors don't have direct access to the graphics hardware with few exceptions including Virgil/Virtio GPU available in QEMU (only works with Linux guests) and VMWare ESXi GPU passthrough, which means graphics card emulation is less than ideal for video games that use 3D APIs. However, 3D acceleration in hypervisors today is capable of running fairly demanding video games or other 3D applications with a few drawbacks such as limited DirectX API versions. Every hypervisor has a different approach to handling 3D graphics, and most of the time companion programs such as VMware Tools have to be installed in virtualized operating systems. Supports for OpenGL are slightly better than Direct3D since it doesn't have to be reverse engineered, but most Windows games (including ports) use Direct3D. | Hypervisors don't have direct access to the graphics hardware with few exceptions including Virgil/Virtio GPU available in QEMU (only works with Linux guests) and VMWare ESXi GPU passthrough, which means graphics card emulation is less than ideal for video games that use 3D APIs. However, 3D acceleration in hypervisors today is capable of running fairly demanding video games or other 3D applications with a few drawbacks such as limited DirectX API versions. Every hypervisor has a different approach to handling 3D graphics, and most of the time companion programs such as VMware Tools have to be installed in virtualized operating systems. Supports for OpenGL are slightly better than Direct3D since it doesn't have to be reverse engineered, but most Windows games (including ports) use Direct3D. | ||
− | ===[[macOS]]=== | + | ===[[Macintosh line#x86|macOS]]=== |
There's an ongoing effort to get macOS installations working on hypervisors that run on non-Apple hardware. Such support has historically been low or non-existent since Apple makes no effort to support standard PC hardware. Some people have gotten this to successfully work on KVM/QEMU, with an example/setup guide for Debian/Ubuntu hosts being available [https://github.com/kholia/OSX-KVM here]. | There's an ongoing effort to get macOS installations working on hypervisors that run on non-Apple hardware. Such support has historically been low or non-existent since Apple makes no effort to support standard PC hardware. Some people have gotten this to successfully work on KVM/QEMU, with an example/setup guide for Debian/Ubuntu hosts being available [https://github.com/kholia/OSX-KVM here]. | ||
Line 116: | Line 100: | ||
Despite many of the common operating systems including legacy ones such as MS-DOS, OS/2, Novell Netware, etc. are being supported by modern hypervisors, some obscure (e.g. [https://templeos.org/ TempleOS]), abandoned (e.g. [https://ja.wikipedia.org/wiki/%E8%B6%85%E6%BC%A2%E5%AD%97 Chokanji 1~4]), beta or experimental (e.g. [https://betawiki.net/wiki/Windows_95 Windows "Chicago" Beta]) operating systems may still fall out of the range and having issues, especially when relying on specific hardware configuration or old quirks that no longer presents in modern PC hardware. | Despite many of the common operating systems including legacy ones such as MS-DOS, OS/2, Novell Netware, etc. are being supported by modern hypervisors, some obscure (e.g. [https://templeos.org/ TempleOS]), abandoned (e.g. [https://ja.wikipedia.org/wiki/%E8%B6%85%E6%BC%A2%E5%AD%97 Chokanji 1~4]), beta or experimental (e.g. [https://betawiki.net/wiki/Windows_95 Windows "Chicago" Beta]) operating systems may still fall out of the range and having issues, especially when relying on specific hardware configuration or old quirks that no longer presents in modern PC hardware. | ||
− | Using a low-level [[ | + | Using a low-level [[Intel CPUs]] emulator to run these operating systems may ease out such problems compared to hypervisors. |
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
==See also== | ==See also== | ||
− | + | * [[Intel CPUs]] | |
− | * [[ | ||
− | |||
− | |||
− | |||
− | |||
− | |||
− | [[Category:Computers | + | [[Category:Computers]] |
[[Category:Not really emulators]] | [[Category:Not really emulators]] |