Unterschiede

Hier werden die Unterschiede zwischen zwei Versionen angezeigt.

Link zu dieser Vergleichsansicht

Beide Seiten der vorigen RevisionVorhergehende Überarbeitung
Nächste Überarbeitung
Vorhergehende Überarbeitung
software:hypervisoren:start [2022-07-15 11:08] fabian.ditarantosoftware:hypervisoren:start [2022-07-15 12:01] (aktuell) Urs Graf
Zeile 1: Zeile 1:
 ====== Hypervisors ====== ====== Hypervisors ======
 ==== General information ==== ==== General information ====
-Working on a virtual environment, we suggest to choose one of the most common [[wp>Hypervisor]]s available, which are curently the following:+Working on a virtual environment, we suggest to choose one of the most common [[wp>Hypervisor]]s available, which are currently the following:
  
   * **VMware**   * **VMware**
Zeile 11: Zeile 11:
 Each of those hypervisors support the import of virtual machines (VMs) based on the file formats ''.ova'' and ''.ovf''. \\ Each of those hypervisors support the import of virtual machines (VMs) based on the file formats ''.ova'' and ''.ovf''. \\
 <box red 97% | Note> <box red 97% | Note>
-**Depending on how a VM is being configured via the underlying hypervisor, the export/import between different hypervisors could be compatible. However, in most cases, not without any manual preparation steps!**+**Depending on how a VM is being configured via the underlying hypervisor, the export/import between different hypervisors could be compatible. However, in most cases, not without any manual preparatory steps!**
 </box> </box>
 \\ \\
Zeile 22: Zeile 22:
 ==== Troubleshooting ==== ==== Troubleshooting ====
 === BIOS settings === === BIOS settings ===
-To operate with a type 2 hypervisor, a computer's CPU (processor) must support hardware virtualization in the first place, which is the case for most any of modern CPUs. That said, it may be required enable the according option within the computer's BIOS, mostly within the "Advanced BIOS Features" section or similiar. The according option to enable is typically called as one of the following:+To operate with a type 2 hypervisor, a computer's CPU (processor) must support hardware virtualization in the first place, which is the case for most of modern CPUs. That said, it may be required to enable the according option within the computer's BIOS, mostly within the "Advanced BIOS Features" section or similiar. The according option to enable is typically called one of the following:
   * Intel VT-x   * Intel VT-x
   * AMD VT   * AMD VT
Zeile 33: Zeile 33:
  
 === Incompatibility with Microsoft Hyper-V (VMware Workstation Version < 15.5 only) === === Incompatibility with Microsoft Hyper-V (VMware Workstation Version < 15.5 only) ===
-In case you are using a physical //Windows 10// computer and //VMware Workstation Player// version < 15.5 as a hypervisor, in some circumstances this combination can make you run into compatibility issues, caused by //Microsoft//'own virtualization platform //Hyper-V//. In such case, the following similiar error message will occur when trying to start the VM: \\ [{{:software:hypervisoren:hypervisoren01.png|Error message}}] \\+In case you are using a physical //Windows 10// computer and //VMware Workstation Player// version < 15.5 as a hypervisor, in some circumstances this combination can make you run into compatibility issues, caused by //Microsoft//'native virtualization platform //Hyper-V//. In such case, the following similiar error message will occur when trying to start the VM: \\ [{{:software:hypervisoren:hypervisoren01.png|Error message}}] \\
 To fix this issue, you could try one of the following solutions: To fix this issue, you could try one of the following solutions:
  
Zeile 41: Zeile 41:
   * Execute the following //CMD// command with administrative privileges: <code>bcdedit /set hypervisorlaunchtype off</code>   * Execute the following //CMD// command with administrative privileges: <code>bcdedit /set hypervisorlaunchtype off</code>
  
-After troubleshooting, if your computer meets any of the conditions above, **after a system reboot**, the error messages should not ocoour anymore.+If your computer meets any of the solutions above, **after a system reboot**, the error messages should not occur anymore.