Unterschiede

Hier werden die Unterschiede zwischen zwei Versionen angezeigt.

Link zu dieser Vergleichsansicht

Beide Seiten der vorigen RevisionVorhergehende Überarbeitung
Nächste Überarbeitung
Vorhergehende Überarbeitung
Nächste ÜberarbeitungBeide Seiten der Revision
software:hypervisoren:start [2022-07-15 11:09] fabian.ditarantosoftware:hypervisoren:start [2022-07-15 11:11] fabian.ditaranto
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 ocoour anymore.