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 6: | Line 6: | ||
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 27: | Line 25: | ||
|[[VMware Workstation]] | |[[VMware Workstation]] | ||
|align=left|{{Icon|Windows|Linux}} | |align=left|{{Icon|Windows|Linux}} | ||
− | | | + | |{{VMwareWorkstationVer}} |
|{{✗}} ||{{✓}} ||{{✓}} | |{{✗}} ||{{✓}} ||{{✓}} | ||
|- | |- | ||
|VMware Fusion | |VMware Fusion | ||
|align=left|{{Icon|macOS}} | |align=left|{{Icon|macOS}} | ||
− | | | + | |{{VMwareFusionVer}} |
|{{✗}} ||{{✓}} ||{{✓}} | |{{✗}} ||{{✓}} ||{{✓}} | ||
|- | |- | ||
Line 46: | Line 44: | ||
|- | |- | ||
!colspan="6"|Mobile / ARM | !colspan="6"|Mobile / ARM | ||
− | |||
− | |||
− | |||
− | |||
− | |||
|- | |- | ||
|UTM | |UTM | ||
− | |align=left|{{icon|macOS | + | |align=left|{{icon|macOS}} |
|[https://github.com/utmapp/UTM/releases {{UTMVer}}] | |[https://github.com/utmapp/UTM/releases {{UTMVer}}] | ||
− | |{{✗}} ||{{✓}} ||{{ | + | |{{✗}} ||{{✓}} ||{{?}} |
|- | |- | ||
|VMOS | |VMOS | ||
Line 67: | Line 60: | ||
;[[VirtualBox]] | ;[[VirtualBox]] | ||
− | :Is open source but it has an extension pack that adds features common on | + | :Is open source but it has an extension pack that adds features common on standard PCs like USB 2.0, 3.0, PXE boot, and hard drive encryption. It is generally the easiest to set up and get running. |
;[[VMware Workstation]] Pro | ;[[VMware Workstation]] Pro | ||
− | :Is also available for GNU/Linux, though the Windows version has better 3D support because of its native Direct3D implementation. | + | :Is also available for GNU/Linux, though the Windows version has better 3D support because of its native Direct3D implementation. |
:;[[VMware Workstation]] Player | :;[[VMware Workstation]] Player | ||
::Formerly VMware Player, it is VMware's free offering but lacks a few features like snapshots. | ::Formerly VMware Player, it is VMware's free offering but lacks a few features like snapshots. | ||
− | |||
− | |||
− | |||
;Virtual PC | ;Virtual PC | ||
Line 88: | Line 78: | ||
* 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) | ||
− | |||
==Integrations== | ==Integrations== | ||
Line 108: | Line 96: | ||
If you're using Windows 10/11 for host OS you can use Hyper-V and GPU-P just like Linux GPU passthrough. [https://github.com/jamesstringerparsec/Easy-GPU-PV#prerequisites jamesstringerparsec's "Easy-GPU-PV" batch script] for making GPU Paravirtualization on Windows Hyper-V easier. | If you're using Windows 10/11 for host OS you can use Hyper-V and GPU-P just like Linux GPU passthrough. [https://github.com/jamesstringerparsec/Easy-GPU-PV#prerequisites jamesstringerparsec's "Easy-GPU-PV" batch script] for making GPU Paravirtualization on Windows Hyper-V easier. | ||
− | |||
− | |||
− | |||
==Hypervisor issues== | ==Hypervisor issues== | ||
Line 138: | Line 123: | ||
[https://learn.microsoft.com/en-us/troubleshoot/windows-client/application-management/virtualization-apps-not-work-with-hyper-v Many third-party Type 2 virtualization applications don't work together with Hyper-V feature from 'Control Panel/Windows Features']. Affected applications include "VMware Workstation" and "VirtualBox". These applications might not start virtual machines, or they may fall back to a slower, emulated mode ('''no''' VT-x and nested paging etc.) | [https://learn.microsoft.com/en-us/troubleshoot/windows-client/application-management/virtualization-apps-not-work-with-hyper-v Many third-party Type 2 virtualization applications don't work together with Hyper-V feature from 'Control Panel/Windows Features']. Affected applications include "VMware Workstation" and "VirtualBox". These applications might not start virtual machines, or they may fall back to a slower, emulated mode ('''no''' VT-x and nested paging etc.) | ||
− | Even though some reports consider this issue fixed via [https://www.ubackup.com/enterprise-backup/vmware-workstation-and-hyper-v-are-not-compatible.html recent updates (with VMware 15.5.6 and Windows 10 20H1) and WHP windows feature], user reports shows that it's still there | + | Even though some reports consider this issue fixed via [https://www.ubackup.com/enterprise-backup/vmware-workstation-and-hyper-v-are-not-compatible.html recent updates (with VMware 15.5.6 and Windows 10 20H1) and WHP windows feature], user reports shows that it's still there. |
==See also== | ==See also== | ||
− | + | * [[POS_(Pong_Consoles)_CPUs_and_Other_Chips#x86_CPUs|x86 CPUs]] | |
− | |||
− | |||
− | |||
− | |||
− | |||
− | *[[POS_(Pong_Consoles)_CPUs_and_Other_Chips]] | ||
[[Category:Computers|*]] | [[Category:Computers|*]] | ||
[[Category:Not really emulators]] | [[Category:Not really emulators]] |