zl程序教程

您现在的位置是:首页 >  工具

当前栏目

Resolve the conflict between docker and VMWare-ITworkman

VMwareDocker The and between resolve conflict
2023-09-11 14:14:16 时间

How to Disable VBS and Speed Up Windows 11 or 10

下面的bcdedit /set hypervisorlaunchtype off执行了没啥用

HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\DeviceGuard.

Open EnableVirtualizationBasedSecurity and set it to 0.

然后重启电脑

(7 条消息) hyper-v 和 vmware 不兼容,是技术的原因?还是商业原因? - 知乎 (zhihu.com)

作者:谷月老师讲Office
链接:https://www.zhihu.com/question/21260608/answer/1346983318
来源:知乎
著作权归作者所有。商业转载请联系作者获得授权,非商业转载请注明出处。

2. 传统的解决方法

传统的解决方法是在选择多系统的启动菜单中新增一个选项,让 Windows 在启动时不加载 Hyper-V [4]

主要步骤如下:

解决办法: 以管理员身份打开命令提示符,运行如下两条命令: bcdedit /copy {default} /d "name" bcdedit /set {ID-Number} HyperVisorLaunchType OFF 命令详解: 第一条命令中 name 参数支持自定义。 如果第一条命令成功的话,就会有一串很长的 ID 出现,复制它,第二条命令中需要用到,即 ID-Number 参数,要把它复制到“{}”这个符号中间。 比如我执行的命令: bcdedit /copy {default} /d "Windows Server 2012 Without Hyper-V" bcdedit /set {ce54aea7-ad33-11e9-9022-f8edf66e1542} HyperVisorLaunchType OFF 执行成功后可以用 msconfig 验证是否成功创建启动项,并将引导菜单超时时间修改大一些。 然后重启系统,在选择启动项界面选择"Windows Server 2012 Without Hyper-V"就能运行 VMWare 了。 这样比装双系统方便些,而且这两个引导进去的系统是一样的,只是,有一>个只能运行 VMWare,另一个只能运行 Hyper-V。

3. 遇到了新困难

Windows 引入的一些新功能,例如 WSL 2、 基于虚拟化的安全功能(Virtualization Based Security, VBS,包括Windows Sandbox、Credential Guard、 Application Guard 等)依赖 Hyper-V 环境[5],如果 Windows 系统不加载 Hyper-V, 这些功能也无法使用。

古人有诗云,世间安得双全法,不负如来不负卿。有没有什么双全法可以兼得鱼与熊掌,让 VMWare Workstation/Player 与 Hyper-V 真正共存呢?

4. VMWare 和微软合作

从 VMWare Workstation/Player 15.5.5 版本开始,VMWare 公司重构了 VMM机制,将 VMM 机制调整为在用户级别运行[6],不再直接访问硬件,而是通过利用微软的 Windows Hypervisor Platform (WHP) 的 API 来运行。从而彻底解决了 VMWare Workstation/Player 与 Hyper-V 的冲突问题。

5. 如何让 VMWare 和 Hyper-V 共存?

  1. 将 Windows 版本升级到 Windows 10 20H1 或更高版本。
  2. 将 VMWare Workstation/Player 升级到 15.5.5 或更高版本,本文以 VMWare Player 为例。注意,在安装时,需要在如图所示的这一步勾选“自动安装 Windows Hypervisor Platform (WHP)”。
  1. 运行 VMWare Workstation/Player,新建或导入虚拟机。
  2. 打开虚拟机的设置选项,找到“处理器”,去掉如图所示的三个选项前面的钩,点击“确定”。

否则,在运行虚拟机时,VMWare Workstation/Player 会提示“开机时出错: VMWarePlayer 在此主机上不支持嵌套虚拟化。模块 MonitorMode 启动失败。未能启动虚拟机。”(VMware Workstation does not support nested virtualization on this host. Module ‘MonitorMode’ power on failed. Failed to start the virtual machine.)


"VMware Workstation and Device/Credential Guard are not compatible" error in VMware Workstation on Windows 10 host (2146361)

Steps to Disable Hyper-V:

Note:
It is recommended to take back up of your data and have system restore points as a safety measure. The following features would not work anymore once the Hyper-V is disabled

  • Credential Guard/Device Guard
  • Windows Sandbox
  • Virtual machine platform
  • WSL2
  • Hyper-V

Verify Virtualization-based Security (VBS) is Enabled/Not Enabled:

  1. Open msinfo32/system information on Windows 10
  2. Under System Summary on the Right-hand page, scroll down to Virtualization-based Security and
    ensure the Value is set to Not enabled.
  3. If the value is set to enabled follow the steps given below according to disable Hyper-V.

To open msinfo32/system information on Windows 10, you can follow these steps:

  1. Press the Windows key + R to open the Run dialog box.
  2. Type "msinfo32" in the Run dialog box and press Enter.
  3. The System Information window should now open.

1. Turn Off Hyper-V

  1. Go to "Turn Windows features on or off"
  2. Make sure Hyper-v is not ticked.
  3. If it is Ticked, untick it and click "Ok".

2. Open command prompt window as an administrator   

  1. Run “bcdedit /enum {current}”
  2. Note down the hypervisorlaunchtype in case this needs to be reverted
  3. Run “bcdedit /set hypervisorlaunchtype off” to disable hypervisor Close the command prompt after   executing the commands and restart the system.

We should be able to power on the Virtual Machine in Workstation now.

第一个命令执行完,看到hypervisorlaunchtype    Off
 

 

Process to turn off virtualization-based Security:

Below steps can be followed to turn off virtualization-based Security for Windows 10 Home & Pro:

For Microsoft Windows 10 Pro & above:

  1. Edit group policy (gpedit)
  2. Go to Local Computer Policy > Computer Configuration > Administrative Templates > System
  3. Double Click on Device Guard on the right hand side to open.
  4. Double Click on "Turn On Virtualization Security" to open a new window
  5. It would be "Not Configured", Select "Disable" and click "Ok"
  6. Close the Group Policy Editor.
  7. Restart the system

 

Windows 10 下如何彻底关闭 Hyper-V 服务?

我不知道为什么用楼主的方法没有解决

我是这样解决的,和楼主的差不多,区别在于没有加引导:

  • 以管理员身份运行命令提示符
  • 执行命令 bcdedit /set hypervisorlaunchtype off
  • 重启,运行vm即可

如果想要恢复hyper启动, bcdedit / set hypervisorlaunchtype auto



作者:张林军
链接:https://www.zhihu.com/question/38841757/answer/179656416
来源:知乎
著作权归作者所有。商业转载请联系作者获得授权,非商业转载请注明出处。

 

 

 

2023-03-11 可以选择不使用Hyper-V

WSL 2 backend

  • Windows 11 64-bit: Home or Pro version 21H2 or higher, or Enterprise or Education version 21H2 or higher.
  • Windows 10 64-bit: Home or Pro 21H1 (build 19043) or higher, or Enterprise or Education 20H2 (build 19042) or higher.
  • Enable the WSL 2 feature on Windows. For detailed instructions, refer to the Microsoft documentation.
  • The following hardware prerequisites are required to successfully run WSL 2 on Windows 10 or Windows 11:

  • Download and install the Linux kernel update package.

Resolve the conflict between docker and VMWare-ITworkman

After docker and VMware are installed locally, they cannot be started at the same time. Because docker and VMware are equivalent to hypervisors, and based on the properties of virtual machines, it is necessary to obtain control over CPU and other hardware, because they cannot run on the same machine at the same time.

 

VMware error reporting

 

 

VMware Workstation and Device/Credential Guard are not compatible. VMware Workstation can be run after disabling Device/Credential Guard. Please visit http://www.vmware.com/go/turnoff_CG_DG for more details.

 

Virtualization Based Security

 

Win + R open operation

 

Enter gpedit MSc Open Group Policy Editor

 

Computer Configuration -> Administrative Templates -> System -> Device guard rear

 

Double click to open the configuration option turn on virtualization based security and select disable

PowerShell command

 

Start – Windows PowerShell (admin)

 

The start command is

 

 


bcdedit        /set hypervisorlaunchtype auto

 

 

The close command is

 

 


bcdedit        /set hypervisorlaunchtype off

 

 

The above is my personal experience. I hope I can give you a reference. I also hope you can support the script home. If there are mistakes or not fully considered, please don’t hesitate to comment.