We reverted the Kernel Update (just in case) but this did not help. The template id in the gns3 project file for any node is still valid and still points to a template with correct disk image assignements in gns3_nf.Įven manually fixing the disk path in the gns3 file does not help as it will be rearranged once a topology is (re)started. vmx20.4 could end up with vmx 18.4 hda disk files and/or completly different disk files (we have vmx, vsrx and other vendors images in there). Running 2.2.22 and starting any topology the disk images inside the gns3 project file in the project dir get randomly reasigned to $something that is listed in the nfĮ.g. Using vmx20.4 it installs the correct disk image path into the gns3 project file in the topologies project dir. in gns3_nf) and are listing the correct disk images. We have a couple of custom Templates (mostly stuff like juniper vMX in various versions and other VNFs) build and imported.

It seemed to work fine for some time.Īfter a recent server reboot (due to kernel updates) and therefore service restart we noticed that all projects started after the reboot/upgrade fail to start the nodes.Īfter further invetigation we found out that the projects started after the restart have broken disk path images for the nodes. We are running a couple of GNS3 servers on ubuntu 20.04. I suspect the problem is with gns3-server, so i open it here. We opend a discussion on the community support forum( ), but were pointed to open an issue here.

Juniper images for gns3