Originally posted by **JeffreyMik** April 25, 2024
Hello,
I have a server that is running Windows 10 with Hyper-V enabled. On this Hyper-V, I have GNS3 VM running with more then enough resources. The server is running in subnet 77.0/24 and I am in 78.0/24. When I start the GNS3 application on my laptop and connect to the server using the Edit>preferences>server tab it works fine. The connection gets up and I have no problems. When I start adding appliances it also works as expected, but when I start the appliances the connection gets down.
When I look at my server in the Hyper-V manager, I can see that the heartbeat to the GNS3 VM is changed to 'Lost Connectivity'. What does this mean and how can I fix this problem? Anyone got suggestions or solutions?
EDIT:
Found out that it has something to do with QEMU appliances. When I start an IOU cisco router it works fine. But when I start Ubuntu 20.04.4 and start a console, then the GNS3 VM becomes unreachable.
Discussed in https://github.com/GNS3/gns3-server/discussions/2370