Symptom
When you perform Live Migration or Export/Import between Hyper-V Hosts, you may have a technical issue saying VM cannot find the network switch. (Figure 1)
The following configuration errors were found for virtual machine “Name”.
Could not find Ethernet switch “Name”.
![]()
Figure 1
Solution
To avoid this error, we can enable Ethernet Resource Pool on two Hyper-V hosts (test005, test010) and we can follow the steps below to configure it.
Step 1: Configure VM and vSwitch
In this demo, we create an internal virtual switch named “Pool-Internal” on host test005, and connect the “Pool-Test” VM to “Pool-Internal”. (Figure 2 and Figure 3)
![]()
Figure 2
![]()
Figure 3
Step 2: Create Resource Pool
We use PowerShell command “New-VMResourcePool“ to create an Ethernet pool.
New-VMResourcePool -Name TestEthPool -ResourcePoolType Ethernet
To add the Virtual switch to resource pool, we use “Add-VMSwitch”. (Figure 4)
Add-VMSwitch -Name pool-internal -ResourcePoolName testethpool
![]()
Figure 4
Step 3: Configure Resource Pool
We can see Resource pool is available in the settings of the VM Pool-Test on Test005. (Figure 5 and Figure 6)
![]()
Figure 5
![]()
Figure 6
Step 4: Create Resource Pool on another Host
Use the same commands in steps 2. (Figure 7)
![]()
Figure 7
Step 5: Perform Live Migration or Export/Import
We are able to export the VM “Pool-Test” and import it into Hyper-V Host test010 successfully. (Figure 8 and Figure 9)
In the procedure of importing, it will not prompt the option of selecting network connection, and it still connect to same pool.
![]()
Figure 8
![]()
Figure 9
Please click to vote if the post helps you. This can be beneficial to other community members reading the thread.