Updated with SME suggestions from Jia

Author: LouisBerner

articles/databox-online/azure-stack-edge-gpu-troubleshoot-virtual-machine-provisioning.md

@@ -137,8 +137,12 @@ To check for some of the most common issues that prevent `cloud init` from runni
 
 **Error description:** The primary NIC attached to a single root I/O virtualization (SRIOV) interface-enabled vSwitch caused network traffic to bypass the hyper-v, so the host could not receive DHCP request from the VM, resulting in a provisioning timeout.
 
-**Suggested solution:** Do not create a VM where the primary NIC is on a network-accelerated vSwitch.
+**Suggested solutions:**
+
+- On an Azure Stack Edge Pro 1 device, vSwitches created on Port 1 to Port 4 do not enable accelerated networking. On Port 5 or Port 6, vSwitches will enable accelerated networking by default. 
 
+ - On an Azure Stack Edge Pro 2 device, vSwitches created on Port 1 or Port 2 do not enable accelerated networking. On Port 3 or Port 4, vSwitches will enable accelerated networking by default. 
+ 
 ##	Network interface creation issues
 
 This section provides guidance for issues that cause network interface creation to fail during a VM deployment.