Closed josephmhiggins closed 8 months ago
a gns3 "End Project" is highly desirable because gns3 users complain:
End project is a little tricky because of the "compute_id": = "local" bug in 2.2.39 (I have not tested it in 2.2.41 it is super simple to fix - takes 5 seconds with 7-Zip. A project can take 40 hours to complete - 5 seconds is nothing
End project idea works - but it requires skill from users/training from gns3 developers. Export project is scheduled to be rewritten so the "compute_id"/"local"/"vm" should go away eventual. I would not use the gns3 vm transfer data. I "do not use" Windows anymore in any serious capacity.
old GNS3 VM named GNS3 VM 2.2.39, new GNS3 VM named GNS3 VM old GNS3 VM has 1 project with 1 vm and 1 docker. tried the migration from the information menu. it failed with
rsync: write failed on "/home/gns3/gns3@192.168.161.143/gns3/images/QEMU/asav982.qcow2": No space left on device (28) rsync error: error in file IO (code 11) at receiver.c(374) [receiver=3.1.3]
This error occurred after I erroneously tried to rsync /opt/docker
"No space left on device" on a new GNS3 VM.
So, maybe rsync blew the new GNS3 VM up. I installed a new GNS3 VM.
But by that time, GNS3 VM 2.2.39 information screen got blowned up also. So I just used winscp to transfer the 2 files by downloading and then uploading because it is just 2 files and 1 project I installed a new GNS3 VM 2.2.39 to try reproduce the problem. The problem did not reproduce.
I will recommend windows users use winscp.
I only had 1 project because I have a "End Project" procedure which I will detail on the gns3 community board soon.