When I run adb devices, both the Host and Guest show the physical device, and after attempting to run the debugger, running adb forward -list, the forward rules are as such: I assume if I could get the IDE to connect to 192.168.0.13:29301 (Host IP) instead, it would find the device, given that's where it is connected. You can see more details in Xamarin Diagnostic output and the full exception on logs.įrom what I have gathered, the debugger is trying to connect to localhost, and since the IDE is running within the Guest, the physical device will not be at localhost:29301. Unfortunately, even though I am able to deploy to my device, the debugger is unable to connect, and I receive Cannot start debugging: Cannot connect to 127.0.0.1:29300: No connection could be made because the target machine actively refused it 127.0.0.1:29301Ĭouldn't connect debugger. I believe this configuration is fine, according to the documentation. Guest machine runs the script, with remotehost set to the Host IP, with the same port. Host machine runs the script with IP 192.168.1.13 on port 6037 ( adb daemon runs on 5037, which is default). I used this to 'trick' adb running on the Guest to see the device (which is connected to my physical machine).

I was unable to see the device (within the IDE) initially, however, after some research and work, I've managed to get the device showing.

I have also tried to use workarounds, unfortunately, the device does not show up (even in Device Manager) in the Guest machine.

My physical device is unable to 'passthrough' due to decisions made by the Hyper-V designers, from what I've read. Using Visual Studio 2019 as my IDE with Xamarin (a monodroid project). I have a development environment set up in a Hyper-V virtual machine (Windows 10).

How to enable usb debugging windows 10