hyper-v 添加虚拟以太网交换机连接时失败
上传截图老是提示文件过大，传不上来，内容如下：在Hyper-v管理器中用虚拟交换机管理器新建虚拟网络交换机，选的是外部网络，点了应用之后弹出对话框提示：“应用 虚拟交换机属性 更改时出错” “修改虚拟以太网交换机设置时失败” “以太网端口{FC48AC1F-CA87-463D-A974-720E71000E61A}绑定失败：由于超时时间已过，该操作返回。(0x800705b4)”
解决方法安装网卡硬件厂商的最新驱动程序代替Windows自带微软网卡驱动程序
Fix: Can’t create Hyper-V Virtual Switch (Error 0x80070002)
ByJasmin KahrimanMay 24,
02 minutes read
RECOMMENDED:Click here to fix errors and optimize system performance
Every virtual machine that is hosted on Hyper-V probably requires a virtual network card in order to communicate with the rest of the network. In order to do so, we would need to create a virtual switch and assign it to the virtual machine. There are three different virtual switches on the Hyper-V including private, internal and external. The private network switch provides only communication between virtual machines that are hosted on a physical server. Next to that, the internal switch provides communication between virtual machines and Hyper-V host. The last, but not the least one is the external switch. An external switch is bound to the physical network card and provide communication with the entire network. After we create a virtual switch, the next step would be to assign a virtual switch to the virtual machine. Which switch will we assign? It depends on the virtual machine’s use case.
Some IT Admin is experiencing problems when creating virtual switches on the Hyper-V, regardless if they are trying to create it via GUI or Powershell. One of the error is known as “Error applying virtual switch properties changes. Failed while adding virtual ethernet switch connections.”The details show the GUID of the adapter, with the final text, “The system cannot find the file specified. (0x80070002). The same issue occurs not only on Hyper-V but also on Hyper-V and Hyper-V .
There are a few reasons why this problem occurs, but many of them are pointing to a problem with the network card. We will focus on two of them and walk you through solutions that have helped IT admins to solve a problem. It includes updating the network card, deleting NIC references and re-adding Hyper-V role. So, let’s start. If solution 1 doesn’t solve your problem, please try with solution 2.
Solution 1: Update network card drivers
In our case, we are using physical server HPE ProLiant ML350 Gen10 Server. In order to update the driver for the network card, we would need to access themanufacturer websiteand download an official driver for the network card. As this server uses Intel’s network card, we can also download it onIntel’s website.
