Installing Visual Studio may cause conflicts with VirtualBox and VMware because the Windows Phone SDK is installed, and the conflicts are manifested as follows:
When opening VirtualBox and creating a 64-bit virtual machine with VMware, the following error message appears:
VT-x/AMD-V hardware acceleration has been enabled, but is not operational. Your 64-bit guest will fail to detect a 64-bit CPU and will not be able to boot.
Please ensure that you have enabled VT-x/AMD-V properly in the BIOS of your host computer.
This is caused by the Windows Phone SDK having Hyper-V turned on during installation.
The phone simulator in the Windows Phone SDK needs to be virtualized with Hyper-V. Hyper-V is Microsoft's virtualization software, similar to VirtualBox and VMware, which can be used to create virtual machines. They are called hypervisors or Virtual Machine Monitors. Since Hyper-V cannot coexist with VirtualBox and VMware, VirtualBox and VMware will not work properly when Hyper-V is turned on. The "VT-x/AMD-V" mentioned in the error above is the hardware virtualization support of the processor, which is already turned on in the BIOS; Hyper-V used it, so VirtualBox and VMware complained that it was not operational.
The solution is to disable Hyper-V. There are several pathways:
The first method: Run the command with admin privileges: bcdedit /set hypervisorlaunchtype off.
The corresponding command to open Hyper-V is: bcdedit /set hypervisorlaunchtype auto.
The second method: use the "Add or remove Windows components" graphical interface program and uncheck Hyper-V in it.
All of the above methods require restarting the computer. And after disabling Hyper-V, you can't use the phone emulator in the Windows Phone SDK.
I haven't found a way to run VirtualBox VMs and Hyper-V at the same time, unless the VMs in VirtualBox are 32-bit (I tried 32-bit Windows XP VMs and they still work fine with Hyper-V enabled).
To choose whether to turn on Hyper-V when you start your computer, follow these steps:
1. Run with administrator privilegesbcdedit /copy {current} /d "Windows 10 (Hyper-V on)"command, and then prompt that another startup menu item has been created, note a string of code in { }.
2. Runbcdedit /set {XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX} hypervisorlaunchtype autocommand, replace the red XXX code here.
3. Right-click on the "This PC" property, Advanced System Settings, Startup and Failover, and set the "Time to display the operating system list".
|
Posted on 4/14/2018 9:20:17 PM
|
|
|
